You have an idea, but you do not know which screens you need
You know who the app should help, but it is hard to describe how it should work. Design puts the steps in order and shows how users get from opening the app to completing the task.
UX/UI design helps you decide how users will complete their task: which screens they will see, what they will need to enter and how they will read the result. At EP Digital Studio, we prepare user flows, wireframes and the interface before development starts. We can begin with an idea for a new app or with a specific problem in a live product.
We agree the price and schedule individually, once the scope is defined.

You know who the app should help, but it is hard to describe how it should work. Design puts the steps in order and shows how users get from opening the app to completing the task.
The difficulty may come from unclear labels, too many decisions or no feedback after a tap. We look at the whole task instead of starting by changing the colours of a single screen.
New modules need shared rules for buttons, forms and messages. Designing reusable components helps keep things consistent without drawing every similar situation from scratch.
A prototype lets you walk through the planned screens and discuss the solution. You can spot a missing step, an unclear label or information the app does not yet have a source for — early on.
We agree on specific deliverables: a map of the user’s steps, wireframes, designs of the key screens, a prototype and a description of the shared components. The scope depends on the problem. Improving a single form does not always require designing the whole app; for a new product, a single screen image usually does not describe enough of how it works.
A wireframe helps decide how information is laid out. The interface design defines the look and hierarchy of the elements, and a clickable prototype shows the transitions between selected screens. We keep these deliverables separate, so it is clear what you are reviewing and what the developer will receive.
We also describe situations that do not appear on the main screen: empty data, an invalid entry, waiting for a response and no connection. Users should know what has happened and what their next step is. These decisions are part of the design, not an extra left until the end.
We take into account text legibility, contrast, touch targets and element names for screen readers. Accessibility then needs to be checked in the finished app. A visual design alone does not confirm that the whole product is compliant.
We agree the price and schedule individually, once the scope and the required materials are defined.
We discuss the user’s task, the information needed and the constraints. In an existing app, we identify the part that needs improving and how it connects to the rest of the process. We also agree who approves decisions.
We show the order of the screens and the information needed at each step. We check that users can complete the task and that we are not asking them for data they do not have. We sign off how it works first.
We give the screens a consistent look, prepare the components and link selected views together. The prototype is used to assess the navigation. If testing with your audience is needed, we agree the scenarios, participants and how feedback will be collected separately.
We organise the approved screens, variants and behaviour rules, and flag decisions that depend on technical constraints. The materials can go to your team or become the basis for the studio’s further work on the app.

Procentownik has 33 modules in six categories. The interface has two themes, Calm and Bold, each for day and night. A set this large needs recognisable fields, buttons and results, despite the differences between an everyday converter and a school maths task.
In the School category — maths step by step — explanations and visual models matter. Tools that use external data need to show the source and how current the information is. The app uses data from NBP, GPW Benchmark, the Ministry of Finance, ZUS and Polish Treasury Bonds, and includes screen reader descriptions.
Calculations can work offline, but refreshing external data requires an internet connection. That is why a local result and the freshness of downloaded information are two different things, which the interface should communicate clearly. Have a look at Procentownik and the online calculators to see real forms and ways of presenting results.
Yes, we can agree a scope that covers UX/UI only. Before we start, we define the materials to be handed over and the needs of the team that will implement them. If you want to combine design with building the product, see Flutter apps.
No. Prepare a description of the person the app should help and their main task. Together, we can organise the features and dependencies. If the scope is still open, it is worth starting by defining the project’s boundaries rather than ordering every screen straight away.
A prototype shows selected transitions and interface behaviour. It does not replace real calculations, data storage or a connection to your company’s systems. Before reviewing the materials, we agree which elements are a demonstration and which need technical verification.
We agree the scope of testing separately. Walking through a prototype during a design meeting is not the same as research with your audience. If we need participants, we define how they will be recruited, the tasks and the expected outcome before this part of the work begins.
We can include them in the agreed scope. Each variant needs its text, contrast and component states checked. We define the number of themes and screens before quoting, rather than treating an additional look as an automatic copy of the first design.
The quote depends on the number and complexity of the flows, the variants needed and the scope of the prototype and handover. The number of screens alone does not describe all the work. We describe the factors and the materials you need for the conversation in our guide: how much a mobile app costs.
Tell us who the app should help and what stage you are at. If the product is already live, point to the task that causes difficulty and show us the current screens. For a new app, a description of the idea is enough; add anything that has not been decided yet.