Mobile app design covers two distinct layers: the structure of how a user moves through the app, and the visual layer built on top of it. Jar Agency handles both as part of one design process, separate from development, so a business can order design on its own or as part of a full project — with source files handed over and pricing tied to the actual number of screens involved.
What mobile app design covers: UX and UI
UX is the structural layer: how a user moves between screens, where they complete a key action, what happens when something goes wrong. It is largely invisible when done well — the app simply feels easy to use.
UI is the visual layer built on that structure: color, typography, icons, and the different states of buttons and fields. UI without solid UX underneath often looks polished but is awkward to actually use.
Getting this balance right matters more on mobile than on desktop: screen space is limited, so every design decision has to earn its place rather than simply adding visual interest.
Design as a separate stage from development
Design and development are distinct stages with separate deliverables. Design produces a set of screens at device resolution that a developer can build from directly, without needing further clarification at each step.
Ordering design separately from development makes sense if a business already has its own development team and only needs the interface work done. It can also be delivered as part of a full project, alongside development.
We typically test the interface flow with the client before moving into final visual polish, catching usability issues while they are still cheap to adjust.
Design system and screen count
Screen count is the clearest driver of design cost: each unique screen and interaction state takes time to design. Repeated elements — cards, buttons, input fields — are designed once and reused, which keeps cost down for apps with a consistent visual language.
A design system formalizes those reusable components. It adds cost upfront but pays off as new screens are added later, since each new screen draws from components that already exist rather than being built from scratch.
We also design for the states that are easy to forget in early mockups — empty screens with no data yet, loading states, and error messages — since these appear constantly in real use even though they're rarely the centerpiece of a pitch.
Pricing for design work
Design pricing depends on the number of screens, the complexity of interactions, and whether a full design system is built alongside the interface itself. It is quoted separately from development pricing.
We provide a breakdown after a brief so the client can see the design cost as a distinct line item, rather than a portion buried inside a single total figure.
Even without a formal design system, we group and label reusable elements clearly, so a future designer or developer can extend the interface without guessing at the original intent.
Timeline for design
A small app with a limited number of screens takes less time to design than a product with a client account, a catalog, and multiple interface states.
Design timelines are set separately from development timelines — the client reviews and approves the screens before development starts, avoiding rework later in the process.
We provide screens at the resolutions used by the target devices, along with notes on spacing and behavior, so nothing gets lost between the design file and the built interface.
Choosing a design agency — what to look for
Ask to see how a past project's structure was mapped before any visuals were made — an agency that jumps straight to screens without planning the logic tends to produce designs that need reworking once real use cases surface.
Ask whether the source files are handed over at the end of the project. Owning the design files means you're not locked into one agency for every future change.
It's also worth asking how revisions are handled — a design process that allows for feedback rounds tends to produce a more usable result than one that treats the first draft as final.
Our design process
We start with the structure — how the app should work — before any visual design begins. That structure is reviewed with the client before moving to interface design.
From there we design the visual layer, build reusable components where it makes sense, and hand over a complete set of screens ready for development, along with the source files.
We're transparent about timeline slippage risk from revision rounds — if a client expects several rounds of significant changes, we account for that in the schedule upfront rather than treating each round as an unplanned delay.
Как это выглядело у клиентов
Частые вопросы
Is mobile app design offered separately from development?+
Yes, design can be ordered on its own if you already have a development team, or as part of a full project that includes development.
What determines the cost of app design?+
The number of unique screens, the complexity of interactions, and whether a full design system is built alongside the interface. Reused elements reduce cost compared to fully unique screens.
Do we get the source design files?+
Yes, source files are handed over, so you are not dependent on one agency for future changes to the design.
Is a design system necessary for a small app?+
Not always. It pays off for apps expected to grow and add screens over time. For a small, one-off app it can be an unnecessary added cost.
How long does the design stage take?+
It depends on the number of screens and complexity of the app. Timelines are set separately from development, and screens are reviewed before development begins.
Обсудим вашу задачу
Оставьте телефон или мессенджер — вернёмся в течение рабочего дня и посчитаем, во сколько обойдётся заявка в вашей нише.
Подробно об услуге «Сайты и разработка»