Flows and screen audit
We walk the current app on an iPhone and an Android phone, map each job a customer has to finish, and mark where people stall. You receive: the audit, the flow maps and a ranked list of screens to redraw.
App design
We design your iPhone and Android screens to each platform’s own guidance, try them with your customers, and hand your developers a Figma file they can build from.
Tell us which screens people give up onWhat app design is
An app design agency decides what each screen of a mobile app shows, how people move from one screen to the next, and how the result looks and behaves on an iPhone and on an Android phone, all before developers write code. The file it hands over is what the build is measured against.
The first drawing is the path a customer takes to finish one job, such as changing next week’s order. We map those paths with you and cut the steps that only exist for the screen’s sake.
iPhone and Android owners expect different back gestures, tab bars and pickers. We draw to Apple’s Human Interface Guidelines and Google’s Material Design, and mark where your brand overrides them.
Components, color and type variables, and the states of each screen are named in Figma, so a developer reading the file can look up an answer before asking you for one.
The platform decision
Both are sound ways to design an app. The choice changes the drawing effort, the build effort and how the app feels in the hand.
| Single layoutThe same screens on both phones | Shared systemNative patterns where they matter | |
|---|---|---|
| Navigation and back | One navigation model, identical on iPhone and Android | Each platform’s tab bar, back gesture and sheets, wired to the same sections |
| Pickers and system controls | A custom picker drawn once and built twice | The platform’s own date and time pickers, which people already know how to use |
| Drawing effort | Fewer screens to draw and one file to keep in step | More screens to draw, because some differ by platform |
| Brand expression | Carried by the layout itself, which can look the same everywhere | Carried by color, type, imagery and motion inside the platform’s frame |
| A good fit when | A small team wants one look and accepts that it will feel foreign on one platform | Customers use the app often and compare it with the apps around it |
The scope lists which screens follow each platform’s pattern and which carry your brand’s own. You approve that list before the first screen is drawn.
The published guidance
The source and the date we read it are printed under each one.
The Buttons page gives 44x44 pt as the general rule. The Accessibility page lists 44x44 pt as the default control size on iOS and iPadOS, with 28x28 pt as the minimum, and adds that spacing between controls matters as much as size.
Android Accessibility Help says anything a person can touch should be large enough for reliable use, and points to Material Design’s accessibility guidelines for the 48dp figure. It also shows how to keep an element’s look while enlarging the area that responds.
Success Criterion 2.5.8 allows exceptions for spacing and inline links; 2.5.5, at Level AAA, asks for 44 by 44. Criterion 1.4.3 asks for 4.5:1 contrast on text, and 3:1 on large text. WCAG is written for web content, so we treat it as a written baseline for app screens.
The Tab bars page asks designers to weigh each extra tab against how often people need that section. Where people choose their own tabs, it suggests a default of five or fewer, and it warns that a More tab makes hidden content harder to reach and notice.
Guideline 3.1.2(c) puts it as questions: how many issues a month, how much cloud storage, what kind of access. It also refers to Schedule 2 of the Apple Developer Program License Agreement for the terms to show. That text lands on the paywall screen.
The Eighth Circuit vacated the amended rule on July 8, 2025. ROSCA requires clear disclosure of material terms before billing details are taken, express informed consent, and simple mechanisms to stop recurring charges. State laws add their own cancellation rules.
The scope
From the first audit to the last handoff note, each part names what lands in your Figma account.
We walk the current app on an iPhone and an Android phone, map each job a customer has to finish, and mark where people stall. You receive: the audit, the flow maps and a ranked list of screens to redraw.
Navigation, back behavior, sheets and pickers follow Apple’s and Google’s guidance, with your brand carried by color, type and imagery. You receive: a pattern list that says which screens follow the platform and which carry your own design.
The flows become a prototype that people tap through on their own phones while we watch where they hesitate. You receive: the prototype, the session notes and the task results with the changes they led to.
Buttons, cards, inputs and sheets are built once in Figma with color, type and spacing variables, for light and dark appearance. You receive: the component library and a short guide to extending it without redrawing what exists.
Screens are drawn with target sizes, contrast and larger text in mind, then reviewed against the platform guides and WCAG 2.2. You receive: the accessibility notes, screen by screen, and the open items you decide on.
Each screen is marked up with its states, spacing, component names and the questions we expect developers to ask. You receive: the handoff sheet and a Figma file your developers can inspect, or ours can.
How it runs
You approve each stage before the next begins, and the Figma file sits in your team account from the first day.
Screen audit
| Screen | Finding | Decision |
|---|---|---|
| Plan picker | Three plans compared on one long scroll, with prices below the fold | Redraw |
| Weekly menu | Swapping a recipe sits behind a long press | Redraw |
| Skip or pause | Skip button is 32 pt high on iPhone and 36 dp on Android | Redraw |
| Delivery day | A custom date wheel on both platforms | Use each platform’s own picker |
| Checkout | The total changes after the promo code field | Redraw |
| Cancel plan | Reached through three screens | Redraw |
Our stack
What the screens are mapped, drawn, tried on phones and handed to developers with. Open a card to see where each one sits in the work.
Figma is a design tool for screens, components and clickable prototypes.
The file lives in a team under your account, with components, variables and Dev Mode notes for the engineers.
Questions
Keep exploring
Business software built around how you work, in your own repository.
Swift and SwiftUI iPhone apps, built in your own Apple Developer account.
Kotlin and Jetpack Compose apps, published from your own Google Play account.
Engineers on your product, working in your GitHub, Jira and Slack.
A remote team building in your repository, with the code in your name.
A first version at a fixed price, with a list of what to cut.
Portals, dashboards and SaaS-style tools that run in the browser.
Software for larger organizations, built around the systems already in place.
One TypeScript codebase for iPhone and Android, in your own store and Expo accounts.
Start here
Say where the app stands. We’ll send back the screens in scope, the platforms, the testing plan and a written price for the design.