---
title: "App modernisation"
url: "https://wzor.biz/en/services/app-modernisation/"
description: "App modernisation at Wzór UX agency: an interactive design of the new interface, split into releases and rolled out in batches on your existing backend."
lang: "en"
---
# App modernisation

At Wzór, a UX agency, you get an interactive app modernisation design, split into successive releases, which can then be implemented by our team or by your own developers. We have already modernised the [CWZN](https://wzor.biz/en/case-studies/cwzn-online-store-redesign/) online store, with ten years of history behind it, and redesigned the old [Bosfor Charter](https://wzor.biz/en/projects/bosfor-charter/) booking site. We often begin with a [technical audit](https://wzor.biz/en/services/technical-audit/), and the new screens in each release share a common [design system](https://wzor.biz/en/services/design-system/).

[Free consultation](https://wzor.biz/en/free-consultation/) [Projects](https://wzor.biz/en/projects/)

-   [105+ projects](https://wzor.biz/en/projects/)
-   [115+ clients](https://wzor.biz/en/clients/)
-   [27 testimonials](https://wzor.biz/en/testimonials/)

Challenges

## What challenges does **app modernisation** help you solve?

###  ![](https://wzor.biz/_astro/challenge-08.CpUOXUL6_Z1GH2pM.webp) “I know the interface has to change, but _we can't afford to rewrite the whole system…_”

Our approach

We start with what stays untouched: the logic, the data and the integrations remain where they are, and the new interface runs on the same backend. Any backend changes the new screen genuinely needs come to you as a separate list with the reasoning behind each, so you decide whether and when to fund them.

Scope of services

-   [Technical Audit](https://wzor.biz/en/services/technical-audit/)
-   [Product strategy](https://wzor.biz/en/services/product-strategy/)

###  ![](https://wzor.biz/_astro/challenge-03.DjiM6UVt_ZRFjnL.webp) “Our users know this system by heart, and I'm afraid _a new interface will infuriate them…_”

Our approach

We keep the habits that help people work and change what slows them down or leads to mistakes. Users get new screens in batches, so nobody has to relearn the whole system on a single Monday, and we check every batch first with the people who know the system best.

Scope of services

-   [UX Research](https://wzor.biz/en/services/user-research/)
-   [UX Audit](https://wzor.biz/en/services/ux-audit/)

###  ![](https://wzor.biz/_astro/challenge-04.DJ5e_wQQ_2aL6Xb.webp) “The system has to run every single day, and I'm afraid _rolling out a new interface will bring something to a halt…_”

Our approach

We plan every release so that a new screen first reaches a chosen group, such as your internal team, behind a switch that brings the old view back within minutes, with no emergency release. You move everyone else over only once the new version has survived that group's daily work.

Scope of services

-   [Web app development](https://wzor.biz/en/services/web-app-development/)
-   [Web app design](https://wzor.biz/en/services/web-app/)

Who it is for

## Which companies do we deliver **app modernisation** for?

Stores SaaS Internal systems Mobile apps Software houses

### Online stores and booking sites

We work on online stores and booking sites that are already selling and have their own customers. We modernised the [CWZN](https://wzor.biz/en/case-studies/cwzn-online-store-redesign/) store when, after ten years of changes, it had started to look like a blog, and at [Bosfor Charter](https://wzor.biz/en/projects/bosfor-charter/) we redesigned the old site, where choosing a yacht had relied on phone calls and emails. At [CWZN](https://wzor.biz/en/case-studies/cwzn-online-store-redesign/) we started with a UX audit that set the goals and the schedule, and the client's own developers implemented the store from files we prepared for them.

### SaaS products

With SaaS products, we make sure that a customer who has paid a subscription for years still recognises their product after logging in. The new view structure brings order to modules that were added wherever there happened to be room, and it arrives in batches, so new customers find their way around faster.

### Internal systems

We design for teams who spend the whole day in the system and know every one of its shortcuts. We change the screens where the department loses the most time, and the shortcuts daily work relies on stay where people look for them.

### Customer mobile apps

We replace the interface of apps customers use to pay, order or collect parcels, and we do it module by module rather than on one day for everyone. A customer paying or collecting a parcel in a hurry then gets to know the new look piece by piece, while doing what they came to do anyway.

### Software houses

We join software houses that maintain an application for their client and have been asked to deliver a new interface. We hand over the design in batches that follow the release plan, with components and every state described, so your developers can implement it without asking about each screen.

-   [E-commerce](https://wzor.biz/en/industries/e-commerce/)
-   [Software](https://wzor.biz/en/industries/saas/)
-   [Banking & Finance](https://wzor.biz/en/industries/fintech/)
-   [Healthcare](https://wzor.biz/en/industries/medtech/)
-   [Energy](https://wzor.biz/en/industries/energy/)
-   [Media](https://wzor.biz/en/industries/media/)
-   [Aerospace & Defense](https://wzor.biz/en/industries/aerospace-and-defense/)
-   [Automotive & Mobility](https://wzor.biz/en/industries/automotive-and-mobility/)
-   [Crypto & Blockchain](https://wzor.biz/en/industries/crypto-and-blockchain/)
-   [Education](https://wzor.biz/en/industries/education/)
-   [Entertainment](https://wzor.biz/en/industries/entertainment/)
-   [Fashion & Accessories](https://wzor.biz/en/industries/fashion-and-accessories/)
-   [Grocery Retail](https://wzor.biz/en/industries/grocery-retail/)
-   [Gaming](https://wzor.biz/en/industries/gaming/)
-   [Public Sector](https://wzor.biz/en/industries/public-sector/)
-   [Insurance](https://wzor.biz/en/industries/insurance/)
-   [Logistics & Fulfilment](https://wzor.biz/en/industries/logistics-and-fulfilment/)
-   [Industrial Manufacturing](https://wzor.biz/en/industries/industrial-manufacturing/)
-   [Pharma](https://wzor.biz/en/industries/pharma/)
-   [Real Estate](https://wzor.biz/en/industries/real-estate/)
-   [Retail & FMCG](https://wzor.biz/en/industries/retail-and-fmcg/)
-   [Cybersecurity](https://wzor.biz/en/industries/cybersecurity/)
-   [Services](https://wzor.biz/en/industries/services/)
-   [Sport](https://wzor.biz/en/industries/sport/)
-   [Telecommunications](https://wzor.biz/en/industries/telecommunications/)
-   [Transport & Travel](https://wzor.biz/en/industries/transport-and-travel/)

First conversation

## Free consultation

We ask what bothers your users most in the application and what must not stop, even for a moment. You leave with recommendations on where to start your app modernisation, or with the conclusion that a rewrite would cost less. Knowing your product is enough.

[Free consultation](https://wzor.biz/en/free-consultation/) [Projects](https://wzor.biz/en/projects/)

![](https://wzor.biz/_astro/portrait.Cn4p6oJS_Z1ryFk.webp)

Patryk Korycki CEO, Business Analyst

Why us?

## Why choose our **UX agency**?

-   ### An earlier return on investment
    
    You spread the budget across releases, and the first one covers the screens where the business loses the most today. You use the new interface before the modernisation is finished.
    
-   ### Faster onboarding for new people
    
    An interface that explains itself shortens training for new starters and takes the load off the people who currently walk them through the system at the next desk. Fewer questions reach your support team, too.
    
-   ### One interface instead of two
    
    Switching the old views off is part of the scope, and its date sits in the release plan from the start. You are not left with two versions of the application to maintain and train people on in parallel.
    
-   ### A senior team
    
    A team of senior UX designers that has been designing interfaces for nine years, today for large organisations, SaaS companies and software houses. The new interface fits the way your users work.
    
-   ### Proven client trust
    
    We have designed for [115 brands](https://wzor.biz/en/clients/), and most of them come back to us with another project.
    
-   ### Higher quality with AI
    
    A designer working with AI tools compares more variants of the new screen against the current one than they could draw by hand, and picks the one that removes the most obstacles with the least disruption to habits. What goes into user testing is the chosen version, not the first one.
    

Process

## How will we carry out your **app modernisation**, step by step?

1.  ### A conversation with your team
    
    We agree on the goal of the modernisation and its boundaries
    
    First the goal that has to justify the modernisation to the board: faster work in the department, fewer support tickets, or a product that shows better in sales meetings. Then the boundaries: maintenance windows, the approvals a release needs, the integrations we leave alone and who will implement the new screens.
    
    Key steps
    
    -   The goal of the modernisation and how we will measure it
    -   User roles and their most frequent tasks
    -   Release constraints: maintenance windows, approvals, integrations
    -   Choosing who implements: our team or yours
    
    Deliverables
    
    -   Agreed goal and scope
    -   List of user roles
    -   List of release constraints
    
2.  ### Screen inventory and release plan
    
    We go through the application view by view and set the order of change
    
    We list every screen together with who uses it, how often and how many support tickets it generates. On top of that come interviews with users and observation of their work, because some problems only show up when someone works around the interface in their own way. This produces a release plan in which every batch of screens has a reason.
    
    Key steps
    
    -   Screen list with roles and traffic from analytics
    -   Review of support tickets and user feedback
    -   User interviews and shadowing their working day
    -   Order of screen batches, with the reasoning
    
    Deliverables
    
    -   Screen map with traffic and roles
    -   List of user problems
    -   Release plan
    
3.  ### Interactive design of the first batch
    
    The new screens can be clicked through before anyone starts implementing them
    
    We design the first batch of screens together with the components the next batches will be built from, and we describe every state: empty, with an error, without permissions. Your users try the first batch on the prototype, and what we learn from those tests goes back into the design before anything reaches the developers.
    
    Key steps
    
    -   View architecture and navigation for every role
    -   Design of the first batch of screens with all states
    -   Components shared by the following batches
    -   Prototype tests using tasks from the old view
    
    Deliverables
    
    -   Interactive design of the first batch
    -   Component library
    -   User testing report
    -   Specification for developers
    
4.  ### Rollout in batches
    
    New screens enter daily work release by release
    
    Depending on how you work, our team implements the first batch or we hand it to your developers with the specification and components, and answer their questions while they build it. The following batches follow the rhythm of your sprints, without freezing the product roadmap.
    
    Key steps
    
    -   Implementing the first batch or handing it over to your developers
    -   Release to a chosen group of users, behind a switch
    -   A condition for returning to the old view, agreed before release
    -   Change announcement and materials for the support team
    
    Deliverables
    
    -   First batch in production or a package ready to implement
    -   Rollback conditions for every release
    -   Materials for the support team
    
5.  ### Next batches and switching the old interface off
    
    We check how the new view has landed and see the change through
    
    After each release we check how much of the work has already moved to the new interface, what users report and where they go back to the old view. Based on that, we refine the released batch and prepare the next one, until the final release removes the switches and the old screens.
    
    Key steps
    
    -   Measuring the share of work done in the new interface
    -   Collecting user feedback and fixing the released batch
    -   Designing and implementing the next batches
    -   Removing the switches and the old views
    
    Deliverables
    
    -   Report after every release
    -   Updated release plan
    -   An application with a single interface
    

Methods and technologies

## Methods we use in **app modernisation**

-   ### Strangler Fig
    
    We use the Strangler Fig approach so the new interface takes over the application screen by screen, while the old one keeps running until the last batch is through. There is no single big switchover day, and every release delivers value on its own.
    
-   ### Feature flags
    
    We write feature flags into the plan for every release: they decide which group of users sees the new screen and when the old one comes back. That stops a release from being an all-or-nothing decision.
    
-   ### Information architecture
    
    We rework the information architecture for every role before the first screen is designed. Each later batch then has a ready place in the navigation, so nobody has to rearrange the menu at the next release.
    
-   ### Interactive design
    
    We deliver an interactive design instead of flat mockups, so a new screen can be clicked through and set next to the old one while it is still at the design stage. We collect feedback at the point where acting on it costs least.
    
-   ### Usability testing
    
    We run usability tests on the tasks users perform in the old view today and check whether they go more smoothly in the new one. Comparing the same tasks reveals a gain that opinions alone don't show.
    
-   ### Change communication plan
    
    We prepare a change communication plan for every release: an announcement, a short explanation of what has changed and a channel for feedback. Users know what to expect, so their first day with a new screen doesn't start with a call to support.
    

Selected work

## Our work

-   [
    
    ![Bosfor Charter - a tablet showing the yacht charter platform: a photo of a couple on a yacht and a search widget (number of weeks, dates, yacht type, "Search"), against a sea backdrop.](https://wzor.biz/_astro/cover.DHPu_e5c_Zgsk30.webp)
    
    Transport & Travel
    
    Bosfor Charter
    
    View project
    
    The Bosfor Charter platform - yacht rental and charter. A home page with a search widget (number of weeks, dates, yacht type), search results with filters, a yacht page with specs, equipment and a booking form, and a redesign of the old service. A navy identity, desktop and mobile.
    
    
    
    ](https://wzor.biz/en/projects/bosfor-charter/)
-   [
    
    ![Tip Card - two phones: the client panel ("Hi Barbara", earnings 350 PLN, withdraw) and the "Boost your tips with Tip Card!" landing with personalised QR cards, on a colourful gradient background.](https://wzor.biz/_astro/cover.DTw-Pu6y_4lOMF.webp)
    
    Banking & Finance
    
    Tip Card
    
    View project
    
    Tip Card - a cashless tipping platform based on personalised QR-code cards. A "Boost your tips with Tip Card!" landing page, a card store, sign-up and a client panel with earnings, transactions and payouts. A dark, colourful layout, desktop and mobile.
    
    
    
    ](https://wzor.biz/en/projects/tip-card/)
-   [
    
    ![Fonia - two phones on a teal background: the cashback app home screen with a 325.53 PLN balance and a list of partner stores, next to a store search with suggestions for Empik, Booking, AliExpress and Play.](https://wzor.biz/_astro/cover.DdIowm6o_Z12riqx.webp)
    
    Fonia
    
    A cashback app for online shoppers
    
    
    
    ](https://wzor.biz/en/projects/fonia/)
-   [
    
    ![Wolumen - the "Offer" step of the energy price comparison: three tariff options with per-kWh rates, a contract-length picker and a discount-code field, beside an account statistics card showing 34,225 zł of savings and the electricity and gas prices; on a blue background.](https://wzor.biz/_astro/cover.CpuQAJvX_ZyCKhF.webp)
    
    Wolumen
    
    Energy and gas price comparison for businesses
    
    
    
    ](https://wzor.biz/en/projects/wolumen/)
-   [
    
    ![EzzyGuide - three phones on a dark background: a sign-up confirmation, guide Małgorzata Iwańska's profile with a star rating, and tour details for "In the Footsteps of the Wrocław Dwarves" with the price and contact details.](https://wzor.biz/_astro/cover.DW1rNgrl_ca7w6.webp)
    
    EzzyGuide
    
    A tours app connecting guides with travellers
    
    
    
    ](https://wzor.biz/en/projects/ezzyguide/)
-   [
    
    ![Jawny Lublin - a laptop showing the portal home page: the lead article, the city category menu and a column of popular stories.](https://wzor.biz/_astro/cover.DReNwwRw_1JC914.webp)
    
    Jawny Lublin
    
    A watchdog portal on city transparency
    
    
    
    ](https://wzor.biz/en/projects/jawny-lublin/)
-   [
    
    ![Flotino - a loan calculator and the "Who is our online loan for?" screen on phone mock-ups, against blurred colourful shapes.](https://wzor.biz/_astro/cover.BIgugYRo_ZeHyg7.webp)
    
    Flotino
    
    Online cash loan service
    
    
    
    ](https://wzor.biz/en/projects/flotino/)
-   [
    
    ![WygodnaDieta - a phone showing the app's home screen: an "Excellent" Trustpilot rating and a "Menu-Choice Diet" plan card priced from PLN 80.90/day, against a red gradient with vegetables.](https://wzor.biz/_astro/cover.BfmwIntu_1CFKMk.webp)
    
    WygodnaDieta
    
    App and online store for a meal-box diet service
    
    
    
    ](https://wzor.biz/en/projects/wygodna-dieta/)
-   [
    
    ![SPEC Food - two phones showing the Delikatesy SPEC store: the home page with promotions and a cart with products, on a navy background.](https://wzor.biz/_astro/cover.CbodJcEt_ZIHzVj.webp)
    
    SPEC Food
    
    Online store for a food delicatessen
    
    
    
    ](https://wzor.biz/en/projects/spec-food/)
-   [See what else we build Projects](https://wzor.biz/en/projects/)

## Start your **app modernisation**

A new interface design, a release plan and a rollout in batches, with no backend rewrite.

[Let us talk Write to us](https://wzor.biz/en/free-consultation/)

Client voices

## What our clients say

iLeopard Bosfor Group Sellace EMBIQ

 ![](https://wzor.biz/_astro/dawid-smiglarski.RgmAcSCC_Z1JjuzK.webp)Dawid Śmiglarski Area Manager, iLeopard

> “After migrating our store to PrestaShop and changing the template, we decided to have UX Agency Wzór run a UX audit. It surprised us to learn there were over 40 UX defects in our system, 5 of them critical. The Wzór team not only identified the problems but also set out practical recommendations and concrete examples of how to fix them. At the meeting where we went through the audit we also received valuable input and together chose a new module for the checkout process. We believe the changes will benefit both our customers and the growth of our brand. We thank UX Agency Wzór for their commitment and professionalism, and we will certainly use their services again.”

 ![](https://wzor.biz/_astro/opinia.BrbzyDCf_Z2rQFd5.webp)Maja Wieloch-Silecka Operations Director, Bosfor Group

> “Working with the Wzór team was a genuinely great experience! They always answered our questions quickly and were flexible about our comments. They have no shortage of creative ideas and are at the same time thoroughly reliable and on time. The end result fully met our expectations; we recommend them to anyone looking for professionals who care.”

 ![](https://wzor.biz/_astro/mateusz-swol.DkFG1xeC_ZygxNl.webp)Mateusz Swół Chief Operating Officer, Sellace

> “Our cooperation with UX Agency Wzór started with our own website. We really liked the way they work, so we decided to subcontract projects for our clients to them on a White Label basis. We loved their workflow, the way they hand projects over to our team, their documentation and their work on the design system. Now we can take on bigger risks.”

 ![](https://wzor.biz/_astro/kacper-maraszkiewicz.CZFKryrf_18OjlM.webp)Kacper Maraszkiewicz Project Manager, EMBIQ

> “UX Agency Wzór is a real treasure for us. From the very start, on every one of our UX/UI projects, we can count on their full commitment and professionalism. Their approach to design and to the way they work fits our needs perfectly - from thorough documentation to finished designs that are simply easy to implement. They have a great flow, so everything runs smoothly, and every project looks excellent and is thought through from the user’s side. We wholeheartedly recommend Wzór as a dependable partner for any software house!”

[Meet our clients (115)](https://wzor.biz/en/clients/)

The team

## Who will run your **app modernisation**?

-   ![Aleksandra Bondar](https://wzor.biz/_astro/portrait.D0iAts48_Z2ryhWH.webp)
    
    ### Aleksandra Bondar
    
    Senior UX/UI Designer
    
    [View profile](https://wzor.biz/en/team-and-partners/aleksandra-bondar/)
    
    How can I help you?
    
    > “I will design the new screens batch by batch and hand them to the developers complete, with every state, so no view is left to guesswork.”
    
-   ![Katarzyna Adamczuk](https://wzor.biz/_astro/portrait.BFsC1rhN_Z17TUuY.webp)
    
    ### Katarzyna Adamczuk
    
    Prezes, Analityk Biznesowy
    
    [View profile](https://wzor.biz/en/team-and-partners/katarzyna-adamczuk/)
    
    How can I help you?
    
    > “I will turn the board's goals into an order of change: which roles and tasks move to the new interface first, and how you will know it paid off.”
    
-   ![Patryk Korycki](https://wzor.biz/_astro/portrait.Cn4p6oJS_Z1ryFk.webp)
    
    ### Patryk Korycki
    
    CEO, Analityk Biznesowy
    
    [View profile](https://wzor.biz/en/team-and-partners/patryk-korycki/)
    
    How can I help you?
    
    > “I will build the release plan and the budget for each batch with you, and then make sure the old interface is switched off on the agreed date.”
    

FAQ

## Frequently asked questions about **app modernisation**

What is app modernisation?

App modernisation at Wzór UX agency means replacing the interface of a live application in batches, without rewriting the logic and data the application runs on. The old and new views run side by side for a while, and the final release switches the old screens off. The first step is a screen inventory and a release plan, not mockups of the whole system.

How long does app modernisation take?

App modernisation takes roughly 8-10 weeks. The timeline depends on the number of screens and user roles, the state of the API the new views rely on, and who implements the following batches: our team or your developers. We confirm the exact time once we know the scope.

Does app modernisation require rewriting the backend?

App modernisation does not require rewriting the backend, because the new interface uses the same API and the same data as the old one. Gaps between what a new view needs and what the backend returns today are covered by an intermediate layer on the interface side. Whatever cannot be worked around stays your decision: we describe it separately, with its cost.

Will app modernisation stop the company's work?

App modernisation does not stop the company's work, because new screens arrive in batches and the old interface keeps running until the migration ends. Each release goes first to a group you pick, and the point at which the old view comes back is set in advance.

Can app modernisation start with a single module?

App modernisation can start with a single module, or even a single screen, that goes all the way from design to users. It shows us how the new interface copes with real data, real permissions and the team's habits. The remaining modules then follow the release plan.

When is it better to rewrite an application from scratch?

It is better to rewrite an application from scratch when it is small and replacing it in one go takes less than replacing it in batches, when the technology it runs on is no longer supported, or when the old system has to go quickly. In those cases we say so plainly in the first conversation and propose designing a new application instead of a modernisation.

How do you prepare users for a new application interface?

Users are prepared for a new application interface with advance notice, a brief note on what is changing and why, and the option to return to the old view during a transition period. For releases that change ingrained habits, we prepare materials for your support team and a channel for users to send feedback. After the release, we tell them what we improved based on that feedback.

Who implements the new interface in an app modernisation?

In an app modernisation, the new interface is implemented either by our team or by your developers, and the choice is yours. When you implement it in-house, we pass on the design, the components and the specification for each batch, and stay on the release plan. Often we implement the first batch ourselves to set the pattern, and the following ones move to your team.

What if app modernisation stalls halfway?

An app modernisation that stalls halfway does not leave you empty-handed, because every release is self-contained and fixes specific screens on its own. The date for switching the old interface off is in the plan from the start, and after each release you get a report on how much work the new interface already handles. A decision to stop is then based on the numbers in those reports, not on an impression.

![](https://wzor.biz/_astro/portrait.Cn4p6oJS_Z1ryFk.webp)

Patryk Korycki CEO, Business Analyst

[Send us a message](https://wzor.biz/en/contact/)

Related services

## Services related to **app modernisation**

### You don't know yet _where the problem lies_.

We will examine the interface or the code before planning any change.

[UX Audit](https://wzor.biz/en/services/ux-audit/) [Technical Audit](https://wzor.biz/en/services/technical-audit/)

### You already know the old system _isn't worth developing any further_.

We will design a new application from the ground up, around the process you run today.

[Custom software](https://wzor.biz/en/services/custom-software-development/) [Web app design](https://wzor.biz/en/services/web-app/)

### You already have new screens and want them to _stay consistent_.

We will turn the components into a system or advise you on the next changes.

[Design system](https://wzor.biz/en/services/design-system/) [UX consulting](https://wzor.biz/en/services/ux-consulting/)

Next step

## Free consultation

We talk about where your application slows people down and which parts of it must run without a break. You leave with recommendations for your app modernisation and suggested next steps. There is nothing to prepare.

[Free consultation](https://wzor.biz/en/free-consultation/) [Projects](https://wzor.biz/en/projects/)

![](https://wzor.biz/_astro/portrait.Cn4p6oJS_Z1ryFk.webp)

Patryk Korycki CEO, Business Analyst
