App design

An app design agency that tests your screens on real phones before developers build them

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 on
Trusted by the world's fastest-growing brands

What app design is

Screens drawn for two platforms and one customer

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.

iPhoneAndroidPlanSkip or pauseNext week’s boxDelivers Oct 15Skip this weekPause planSkip or pauseNext week’s boxDelivers Oct 15Skip this weekPause plan

Flows before screens

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.

Two platforms, two sets of habits

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.

A file developers can build from

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

One layout on both phones or one system, two sets of patterns

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 phonesShared systemNative patterns where they matter
Navigation and backOne navigation model, identical on iPhone and AndroidEach platform’s tab bar, back gesture and sheets, wired to the same sections
Pickers and system controlsA custom picker drawn once and built twiceThe platform’s own date and time pickers, which people already know how to use
Drawing effortFewer screens to draw and one file to keep in stepMore screens to draw, because some differ by platform
Brand expressionCarried by the layout itself, which can look the same everywhereCarried by color, type, imagery and motion inside the platform’s frame
A good fit whenA small team wants one look and accepts that it will feel foreign on one platformCustomers use the app often and compare it with the apps around it
How we decide

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

Six things the platforms and a federal court have put in writing

The source and the date we read it are printed under each one.

  1. iPhoneApple

    Apple asks for a hit region of at least 44 by 44 points on a button.

    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.

  2. AndroidGoogle

    Google recommends touch targets at least 48dp wide and high.

    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.

  3. StandardsW3C

    WCAG 2.2 sets a 24 by 24 pixel target floor at Level AA.

    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.

  4. NavigationApple

    Apple says it is generally easier to navigate among fewer tabs.

    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.

  5. SubscriptionsApple

    App Review asks an app to describe what a subscriber gets before it asks for the subscription.

    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.

  6. CancellationFederal law

    The FTC’s 2024 click-to-cancel rule was vacated, and ROSCA still applies to online subscriptions.

    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

What each part of app design hands you

From the first audit to the last handoff note, each part names what lands in your Figma account.

Flow map · Cancel planRedrawAccountManage planCancel planReached through three screensCurrent app2 of 8 found it

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.

Task flowsScreen auditDrop-off points
Pattern list3 platform · 1 brandiPhoneNavigationTab bar, four tabsPlatformBackEdge swipe and back buttonPlatformDate pickerSystem pickerPlatformPrimary button44 pt high, brand colorYour brand

Platform-native patterns

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.

iOSAndroidBrand overrides
Task results8 people a roundSkip next week’s box3 → 7Change the delivery day4 → 7Swap one recipe5 → 8Find where to cancel2 → 8Current appPrototype

Clickable prototype and testing

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.

PrototypeReal phonesTask results
Variables · Kettle2 modesNameLightDarkcolor/primary#137C8B#56C1D6color/surface#FFFFFF#14181Fcolor/text#1A1F29#E7EAF1color/border#D5DAE1#2E3542Used byButtonCardInputSheet

A design system for both platforms

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.

ComponentsVariablesDark mode
Tap targetsSkip or pauseSkip this weekiPhone32 pt → 44 ptAndroid36 dp → 48 dpWCAG 2.2 AA24 × 24 px floor

Accessibility in the drawing

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.

ContrastTap targetsText size
Handoff · Skip or pause6 statesDefaultLoadingErrorOffline+2SkipNew componentSkip confirmation sheetQuestion for developersWhere does the cut-offtime come from?In your Figma account

Handoff to developers

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.

StatesSpecsDev notes

How it runs

Audit, test, system, handoff

You approve each stage before the next begins, and the Figma file sits in your team account from the first day.

screen-audit.csv

Screen audit

Sample · Sample Kettle app, ordering and subscription screens
ScreenFindingDecision
Plan pickerThree plans compared on one long scroll, with prices below the foldRedraw
Weekly menuSwapping a recipe sits behind a long pressRedraw
Skip or pauseSkip button is 32 pt high on iPhone and 36 dp on AndroidRedraw
Delivery dayA custom date wheel on both platformsUse each platform’s own picker
CheckoutThe total changes after the promo code fieldRedraw
Cancel planReached through three screensRedraw
Sizes are measured on a device, in points on iPhone and density-independent pixels on Android.

Our stack

The tools behind a designed app

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
Why Figma

Figma is a design tool for screens, components and clickable prototypes.

How we use it

The file lives in a team under your account, with components, variables and Dev Mode notes for the engineers.

Real-timeDev handoffTokens
FigmaYes
SketchSome
Static mockupsNo

Questions

App design, answered

Start here

Tell us which screens people give up on

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.