Skip to main content Scroll Top

App Design Wireframes: One Booking Flow From Pencil Sketch to Prototype

Updated November 2026 · Written and maintained by the Progression Agency strategy team

A wireframe is the cheapest argument an app team will ever have. App design wireframes reduce every screen of a flow to gray boxes and plain labels, so the owner, the designer and the developer can disagree about content, order and actions while a change still costs minutes. This page follows one hypothetical booking flow from a pencil sketch to a clickable prototype and shows what each pass settles: the level of detail, what every screen holds, how screens connect, which notes travel with them and which tools suit each stage. Progression’s designers and developers are based in New York and wireframe apps for businesses across the US.

On this page · 13 sections
  1. One gray box, two readings
  2. What app design wireframes settle before anyone picks a color
  3. Three levels of detail, one screen
  4. What each mobile app wireframe screen holds
  5. Wiring screens into a task
  6. Annotation: the notes that keep two people reading one box the same way
  7. Wireframe in software development: who reads it, and for what
  8. From wireframe to prototype
  9. Tools for app design wireframes
  10. A wireframe for app design reviews: ten questions
  11. Four habits that make wireframes expensive
  12. What app wireframing costs
  13. Inputs that make the first sketches useful

Wireframes already approved? When the wireframes are signed off and the work turns to finished screens, store graphics and the developer file, our mobile app design company page picks up from there.

Examples marked “Illustrative example.” describe a hypothetical bike repair shop and its booking app, not a real business.

One gray box, two readings

A hypothetical bike repair shop wants customers to book a tune up from their phones. The drop off screen in its first wireframe holds a gray box with one word in it: Map.

Two drawn boxes describing one wireframe box labeled Map. The first box gives the owner's reading, a live courier map. The second gives the developer's reading, a still image that opens the phone's maps app.Two drawn boxes describing one wireframe box labeled Map. The first box gives the owner's reading, a live courier map. The second gives the developer's reading, a still image that opens the phone's maps app.
Illustrative example. One unlabeled box on a hypothetical booking app, read two ways.

The owner read the box as a live map with courier tracking. The developer read it as a still picture of the street that opens the phone’s maps app. Both readings were reasonable, and nobody noticed the gap until the screen was built. One sentence of annotation beside the box would have settled it in a minute: still image of the shop’s location, tap opens the phone’s maps app.

That is the whole case for wireframing carefully. The drawing is cheap; the misunderstanding is expensive. The rest of this page follows the same hypothetical booking flow through every pass that prevents a gap like that one.

What app design wireframes settle before anyone picks a color

The W3C’s Accessibility Roles and Responsibilities Mapping describes wireframes as low fidelity screen mockups and lists them, beside user journeys, prototypes and information architecture, as core deliverables of user experience design. In practice app design wireframes settle six things: order, actions, paths, states, words and notes.

1: Order. What people see first, second and last on each screen.
2: Actions. One main action per screen, named for its result.
3: Paths. Where every tap leads, including back.
4: States. What the screen shows when things go wrong.
5: Words. Real labels, so length and tone are tested early.
6: Notes. Behavior, data and access written beside the box.

Everything else waits. Color, type, imagery and motion belong to visual design, and whether people can actually finish the task belongs to the prototype. The table splits each question across the three stages.

What the wireframe settles and what it leaves for later
QuestionSettled in the wireframeLeft for visual designLeft for the prototype
What is on the screen?Every element, in priority orderImagery and illustrationNothing new
How big is each part?Rough proportions and the main action’s prominenceExact spacing, type sizes and colorHow it feels to tap
What does the screen say?Labels, button wording and messagesTypography and tone of voice polishWhether people read it
Where does a tap lead?Every path, including back and cancelTransitions and motionWhether the path works end to end
What if it goes wrong?Each state the screen must showHow those states lookWhether people recover
Who can use it?Focus order, labels and gesture alternativesContrast and colorKeyboard and screen reader trials

Is an app wireframe the same as a mockup?

They are close relatives with different jobs. An app wireframe fixes structure and behavior in gray; an app design mockup shows how a finished screen will look, with color, type and imagery, and usually comes after the structure is agreed. Showing a polished mockup first invites comments on the color of a button before anyone has asked whether the button should exist.

Where wireframes sit in the app design process

Wireframes come after the problem and the one task are agreed and before visual design. In the app design process they are the first point where a written requirement becomes something people can point at, which is why owners often see gaps in their own requirements for the first time here. The wider steps from idea to launch are on our how to build an app page. Once the flow holds up, the same screens are judged against finished work in our look at the best app design.

Three levels of detail, one screen

The same Pick a time screen from the hypothetical booking app can be drawn three ways. Each level answers a different question, and each costs a little more to change.

Three drawn phone screens. The first is a dashed pencil sketch with a box for the repair, five day boxes, six time boxes and a Book button. The second shows the same layout as solid gray blocks with placeholder labels. The third adds real words, Tune up 45 min, dates 13 to 17, times from 9:00 to 4:30, a Book 9:30 button and four numbered note pins.Three drawn phone screens. The first is a dashed pencil sketch with a box for the repair, five day boxes, six time boxes and a Book button. The second shows the same layout as solid gray blocks with placeholder labels. The third adds real words, Tune up 45 min, dates 13 to 17, times from 9:00 to 4:30, a Book 9:30 button and four numbered note pins.
Illustrative example. One hypothetical screen drawn as a sketch, in gray boxes and with notes.
Three levels of wireframe detail, compared
LevelMade withAnswersCannot answerMove on when
SketchPencil, paper or a whiteboardWhat belongs on the screen and roughly whereProportions, wording, behaviorEveryone agrees on the list of screens
Gray boxesA design tool with simple shapesOrder, size and the main actionHow it looks and feelsEach screen’s purpose fits in one line
AnnotatedThe same file with real words and notesWhat every part does, says and needsWhether people can finish the taskDevelopers have no open questions on the notes

Balsamiq’s guide to wireframes describes the low detail end as simple black and white or grayscale boxes and lines, and the high detail end as closer to the finished product, with placeholder text, images and some interaction. Most app projects pass through all three levels for the main flow and stop at gray boxes for screens that copy an existing pattern, such as a settings list.

How a wireframe paper prototyping session runs

A wireframe paper prototyping session uses printed or hand drawn screens as a working app. One person plays the computer, swapping sheets as a participant taps with a finger; another takes notes. The usability firm NN/g, in its article on paper prototyping, cites the common software engineering estimate that a change made before any code is written is about 100 times cheaper than the same change after implementation. The GOV.UK Service Manual’s guidance on making prototypes makes a similar point from another side: sketches are useful for exploring and discussing basic ideas with colleagues, while realistic code prototypes suit user research better.

  • Print each screen at the size of a real phone.
  • Cut the main buttons out so they can be moved between sessions.
  • Give the participant one task, in their own words.
  • Note every hesitation, not only every wrong tap.
  • Redraw between sessions rather than arguing about what was meant.

When does a high detail wireframe pay off?

When the words carry the risk. A booking confirmation, a price breakdown or a consent screen fails on wording more often than on layout, so those screens earn real copy and notes early, while a list of shop opening hours can stay in gray.

What each mobile app wireframe screen holds

A mobile app wireframe is a small canvas with a lot of decisions on it. The drawing below splits the hypothetical Pick a time screen into six zones, and the table extends the list to everything a finished wireframe should carry.

A drawn phone screen split into six numbered zones, from the screen's single purpose at the top to the notes at the bottom, with a numbered legend explaining each zone.A drawn phone screen split into six numbered zones, from the screen's single purpose at the top to the notes at the bottom, with a numbered legend explaining each zone.
Illustrative example. Six zones on one hypothetical mobile screen.
Parts of one wireframe screen
Part of the screenWhat it holdsThe question it settles
Purpose lineOne sentence above the frameDoes this screen earn its place?
Carried choicesWhat the person picked on earlier screensIs anything asked twice?
Content in orderEach element, most important firstWhat do people see before scrolling?
Main actionOne button, named for its resultWhat happens next?
Ways outBack, cancel, helpCan people leave without losing work?
InputsEach field, its keyboard and whether it is optionalWhat is the least we can ask?
StatesLoading, nothing found, error, successWhat does this screen show when things change?
NotesNumbered pins with plain sentencesWhat would a developer otherwise ask?

Two habits keep screens honest. Write the purpose line first; if it needs the word and, the screen is probably two screens. Then carry earlier choices forward visibly, so the person booking a tune up never wonders whether the app remembered which repair they picked.

Real words or placeholder text?

Real words, as early as the gray box stage. A button labeled Button tells nobody anything, and a label that reads well in a meeting can be too long for a narrow phone. Placeholder text hides both problems until the visual design stage, when fixing them costs more.

How many screens does a first app wireframe need?

Enough to finish the main task from start to end, plus the screens people reach when something goes wrong. For the hypothetical repair shop that is four screens for booking and three more for a full day, a taken slot and a failed payment, before any account or settings screens are drawn.

  • List the task’s steps in plain words before drawing anything.
  • Give each step one screen, then merge any two that share a purpose.
  • Add a screen for every way the task can stop.
  • Leave accounts, settings and profiles for the second pass.

Wiring screens into a task

Screens on their own say little about the trip between them. NN/g’s article on wireflows defines a wireflow as wireframe style page layouts combined with a simplified flowchart for interactions, and notes the format grew up among teams designing mobile apps, where each step can show a full phone screen.

Four small drawn phones joined by arrows: Service, Time, Drop off and Booked. Each arrow starts at the outlined hotspot, Tune up, Book 9:30 and Confirm, and points to the next screen.Four small drawn phones joined by arrows: Service, Time, Drop off and Booked. Each arrow starts at the outlined hotspot, Tune up, Book 9:30 and Confirm, and points to the next screen.
Illustrative example. A four screen booking task drawn as a wireflow.

The rule that makes a wireflow useful is the starting point of each arrow. An arrow should leave from the exact part people tap, not from the edge of the screen, so nobody has to guess which of three buttons leads where. In Figma’s prototyping guide, the same parts have names: the hotspot is where the interaction takes place, a connection joins it to the destination, a flow is the network of connected frames on one page, and each flow has its own starting point.

Flows for the hypothetical booking app
FlowStarts onStepsEnds on
Book a repairServiceChoose a service, pick a time, confirm drop offBooked
Change a bookingBookedOpen the booking, pick a new time, confirmBooked, with the new time
Cancel a bookingBookedOpen the booking, confirm the cancellationHome, with a message
No times leftTimeSee the next day with open slotsTime, on that day
Slot taken while choosingTimeSee a message and the nearest open timeTime, with that slot marked

Wireflow or flowchart?

Use a wireflow when a few screens change with what people do, which describes most apps; use a flowchart when the logic behind the screens has many branches, such as eligibility rules. Many teams draw both and keep the flowchart for developers.

An app idea that lives in a notes file?Send the notes and the one task customers should finish. You get a free proposal for app design wireframes that turn the idea into screens your team can argue over.

Get a free proposalTell us about a project you’d like help with.

Annotation: the notes that keep two people reading one box the same way

Annotations turn a picture into a specification. Figma’s annotation feature lets designers attach notes and live properties to a layer, and its design files come with four preset categories: Development, Interaction, Accessibility and Content.

A drawn card with four rows: Development, Interaction, Accessibility and Content, each holding one example note for a booking screen, and a closing line that each note answers a question before a developer asks it.A drawn card with four rows: Development, Interaction, Accessibility and Content, each holding one example note for a booking screen, and a closing line that each note answers a question before a developer asks it.
Illustrative example. Figma’s four preset annotation categories, each with a note for a hypothetical booking screen.
Annotation categories, with an example each
CategoryWhat the note coversExample on the Pick a time screen
DevelopmentData, rules and limitsTimes come from the shop calendar; past times never show
InteractionWhat a tap, swipe or hold doesA taken slot shows the next open time
AccessibilityFocus order, labels and alternativesDay strip scrolls with buttons as well as a swipe
ContentWords, lengths and toneButton text is Book plus the time, up to 14 characters

Figma says annotation properties stay accurate when the design later changes, and developers see annotations update in real time in Dev Mode. Adding annotations needs a Professional, Education, Organization, Government or Enterprise plan and a Full seat; reading them needs a Full or Dev seat and at least view access to the file. The same notes work just as well as numbered pins on a paper sketch; the tool only keeps them attached as the screen moves.

Which accessibility notes belong on a wireframe?

The W3C’s mapping assigns a set of tasks to user experience designers, and several of them are wireframe decisions rather than visual ones. The list below paraphrases the ones that matter most for an app; W3C states that the mapping does not set WCAG requirements and is not a complete list.

  • Plan keyboard focus states for every active element.
  • Include hover and focus behavior with the design files.
  • Give gesture based actions a single pointer alternative.
  • Give anything that needs dragging a single pointer alternative too.
  • Keep information relevant to a form above its submit button.
  • Show error messages and alerts the same way across the app.
  • Avoid moving focus automatically from one form field to the next.

The W3C’s designing for accessibility tips add points that start in the wireframe too: clear and consistent navigation, form fields with clearly associated labels, and designs for different viewport sizes.

Wireframe in software development: who reads it, and for what

A wireframe in software development is read by more people than the ones who drew it. Each reader looks for something different, and a wireframe that answers only the designer’s questions leaves the rest to guess.

Who reads a wireframe, and what they look for
ReaderReads the wireframe forWants answered before work starts
Business ownerWhether the flow matches how the business runsIs every rule and exception covered?
Product leadScope of the first releaseWhich screens wait for version two?
DeveloperData, states and behaviorWhere does each value come from, and what if it is missing?
TesterPaths and edge casesWhat should happen at every dead end?
Content writerLabels, messages and lengthsHow much room does each line have?

The developer row matters most for cost. Every value on a screen comes from somewhere: a calendar, a price list, the person’s account. A note that names where each value comes from, and what the screen shows if it is missing, removes most of the questions that otherwise arrive halfway through a sprint. Our MVP development company page explains how a first release is scoped once the flow is agreed.

Should developers see wireframes before they are finished?

Yes, at the gray box stage. A developer who sees the flow early can flag a value the system cannot supply or a step that needs a slow outside service, while moving a box still costs nothing.

From wireframe to prototype

A prototype is a wireframe you can tap. Figma’s prototyping guide lists what a prototype is for: previewing interactions and user flows, sharing and iterating on ideas, getting feedback, testing interactions with users and presenting to stakeholders.

A six step flow: sketch, gray boxes, notes, wireflow, prototype and test, each with the question it answers.A six step flow: sketch, gray boxes, notes, wireflow, prototype and test, each with the question it answers.
Six passes from a pencil sketch to a tested prototype.

In Figma the step is small: the annotated frames gain connections from their hotspots, each connection gets a trigger such as a tap, and an animation sets how one frame moves to the next, with a duration between 1 millisecond and 10 seconds. Overlays handle menus, alerts and confirmations without new full screens. The GOV.UK Service Manual adds a warning for prototypes built in code: they need not meet production standards, so their code should not be copied straight into the live service, and a published prototype should sit behind a password so the public does not mistake it for the real thing.

  1. Freeze the annotated wireframes for the flow being tested.
  2. Connect every hotspot on the flow, including back and cancel.
  3. Add the failure states as overlays or extra frames.
  4. Set the prototype to the phone size most customers use.
  5. Test with people who match the customers, one task each.

How those sessions are run and recorded is covered on our usability testing services page.

What changes between the last wireframe and the first prototype?

Very little on the screen and a lot in the file: the frames gain connections, triggers and overlays, and the failure states become reachable. Visual polish can stay out; a gray prototype tests the flow just as well.

Tools for app design wireframes

The right tool is the one that keeps the current question cheap to answer. Pencils win at the start; a shared design file wins once notes and connections matter.

Wireframing tools and what each suits
ToolSuitsWorth knowing
Paper and pencilFirst sketches and wireframe sessions with the ownerNothing to install; cheapest to throw away
Whiteboard or FigJam boardMapping a whole flow with several people at onceGood for the list of screens, weak for detail
BalsamiqLow detail wireframes in a deliberately sketchy styleIts own guide pitches it to non-designers as well as designers
Figma DesignGray boxes, notes, wireflows and the prototype in one fileAnnotations need a paid plan and a Full seat
Figma First DraftA fast starting point from a written promptBuilds from Figma’s own libraries, not your design system

Many teams pick the wireframe software development teams already open every day, so notes and status live where the build happens. For the hypothetical repair shop that means paper for the first session, then one Figma file that carries the gray boxes, the notes, the wireflow and the prototype.

Can AI draft the first wireframe?

It can draft a starting point. Figma’s First Draft turns a written prompt into editable wireframes or designs in a couple of minutes, using wireframing and design libraries Figma built for the purpose. Figma notes it does best with common website and app patterns, and that it cannot yet generate from your own design system; from May 20, 2026 Figma’s agent is the new entry point for the feature. A draft still needs the purpose lines, states and notes a person writes.

A wireframe for app design reviews: ten questions

A review works best as a checklist read aloud with the owner, the designer and a developer in the room. The chart runs the hypothetical booking flow’s second pass through ten points; eight pass and two states are still undrawn.

A drawn checklist of ten rows. Eight ticks: stated purpose, labeled main action, choices carried over, arrows from tappable parts, real words, keyboard focus, tap alternatives to dragging and form help above the button. Two crosses: no slots left today and a slot taken while choosing are not yet drawn.A drawn checklist of ten rows. Eight ticks: stated purpose, labeled main action, choices carried over, arrows from tappable parts, real words, keyboard focus, tap alternatives to dragging and form help above the button. Two crosses: no slots left today and a slot taken while choosing are not yet drawn.
Illustrative example. A hypothetical booking flow passes eight of ten review points.
  1. Does every screen state its one purpose?
  2. Is the main action labeled with what happens?
  3. Do choices carry over between screens?
  4. Does every arrow start at something people can tap?
  5. Are placeholder labels gone?
  6. Is keyboard focus planned for every control?
  7. Does every drag have a single tap alternative?
  8. Is form help above the submit button?
  9. Is every way the task can stop drawn?
  10. Could a developer build each screen without asking a question?

Who should sign off a wireframe?

The person who owns the business rules, not only the person who likes the look. Sign off means the flow matches how the business runs, including the exceptions; the look is agreed later, at the visual design stage.

Four habits that make wireframes expensive

Wireframes fail quietly. Each habit below produces a tidy drawing that still leaves the expensive questions for the build.

  • Drawing only the happy path, so the first full day of bookings breaks the screen.
  • Using labels like Map or Button that each reader fills in differently.
  • Polishing color and type before the flow is agreed, which turns reviews into taste debates.
  • Handing over screens without notes, so developers measure and guess.

The cure for all four is the same: one purpose line per screen, real words, numbered notes and a wireflow that shows every exit. A related view of the whole product design discipline sits on our product design agency page.

What app wireframing costs

Wireframes are rarely bought on their own; they are the first part of an app design or prototype project. The bands below run from the typical low to the published high in the US market.

App wireframing and design work: published US price bands (market ranges only)
WorkTypical low to published high
Clickable prototype, wireframes through a tested flow$8,000 to $25,000
App UI and UX design, one platform$8,000 to $25,000
App UI and UX design, iOS, Android and web$20,000 to $40,000
Full product design project$10,000 to $100,000
Cross platform mobile MVP build that follows the design$40,000 to $90,000
Horizontal range bars for five kinds of work, from a clickable prototype to a cross platform mobile MVP build.Horizontal range bars for five kinds of work, from a clickable prototype to a cross platform mobile MVP build.
Published US price bands (market ranges only) for a clickable prototype, app design for one and three platforms, a full product design project and the cross platform build that follows, typical low to published high.

Progression sets its price in the written proposal, after scope, and it is subject to change. The full design service is described on our UI/UX design services page, and design and build costs together in our app development cost guide.

Why do two wireframe quotes differ?

Usually because they cover different amounts of the app. Count the flows, the failure states, the platforms and the review rounds in each quote; a cheaper quote often stops at the main screens and leaves the states and notes for later.

Wireframes that nobody can build from?Share the file. The free proposal covers the missing states, notes and flows before any code is written.

Get a free proposalTell us about a project you’d like help with.

Pricing depends on scope and is confirmed in a written proposal. Published prices are subject to change.

Inputs that make the first sketches useful

The first wireframing session moves fastest when the business rules are written down before anyone draws. The card lists six inputs.

A drawn card with six rows: the one task, today's version, must ask, rules, words and decision makers, with a closing line that the rules row shapes every state.A drawn card with six rows: the one task, today's version, must ask, rules, words and decision makers, with a closing line that the rules row shapes every state.
A drawn card with six inputs to have ready before wireframing starts.
  • The one task customers should finish.
  • How they do it today.
  • Every piece of information the business needs from them.
  • Opening hours, limits, prices and exceptions.
  • The words customers already use.
  • Who signs off, and who builds.

Teams planning a build alongside the design can compare iOS app development, Android app development and cross platform app development.

What this page leaves out: the Progression Method, proprietary and reserved for clients. Reach out to learn more

Frequently asked questions

What are app design wireframes?
They are simple drawings of each screen in an app, in gray boxes and plain labels, that fix content, order, actions and paths before visual design or code begins.
How detailed should an app wireframe be?
Detailed enough to answer the question at hand. A sketch decides what belongs on a screen, gray boxes decide order and size, and an annotated wireframe decides what every part does and says.
Is a wireframe the same thing as a mockup?
They differ in purpose. A wireframe fixes structure and behavior; a mockup shows how the finished screen will look, with color, type and imagery.
Should wireframes use real words?
Yes, from the gray box stage onward. Real labels show early whether a line fits a narrow phone and whether people understand it.
What goes on every mobile app wireframe screen?
A one line purpose, the choices carried from earlier screens, content in priority order, one main action, ways out, any inputs, every state and numbered notes.
How many screens should the first wireframes cover?
Enough to finish the main task from start to end, plus a screen for every way the task can stop. Accounts and settings can wait for a second pass.
What is a wireflow?
It is a wireframe style screen layout combined with a simple flowchart of interactions, as the usability firm NN/g defines it, with arrows that start at the part people tap.
Which annotation categories does Figma provide?
Figma design files come with four preset categories: Development, Interaction, Accessibility and Content. Editors can rename them or add more for the file.
Which Figma plans can add annotations?
Professional, Education, Organization, Government and Enterprise plans, with a Full seat and edit access to the file.
Do developers need a paid seat to read annotations?
They need a Full or Dev seat and at least view access to the file to view annotations in Figma.
Which accessibility decisions belong in a wireframe?
Focus states for every active element, single pointer alternatives to gestures and dragging, form information above the submit button and consistent error messages, all of which the W3C maps to user experience designers.
Is paper prototyping still worth doing?
Yes, for first sketches. NN/g cites the common estimate that a change before code is written is about 100 times cheaper than the same change after implementation.
Can AI create an app wireframe?
It can create a first draft. Figma’s First Draft turns a prompt into editable wireframes in a couple of minutes from Figma’s own libraries, though it cannot yet use your design system.
When does a wireframe become a prototype?
When its screens are connected so people can tap through a task. In Figma that means adding connections, triggers and overlays to the annotated frames.
Can prototype code go straight into the finished app?
Rarely. The GOV.UK Service Manual advises against copying prototype code into production, because prototype code is not built to production standards.
How does a user flow relate to a single wireframe screen?
A user flow maps the steps of a task; a wireframe shows one screen in that task. A wireflow puts both on one page.
Where do wireframes sit in the app design process?
After the problem and the main task are agreed and before visual design, as the first point where requirements become screens people can point at.
Who should review app design wireframes?
The business owner, the designer, a developer and, ideally, a tester, each reading for rules, flow, data and dead ends.
What do app design wireframes cost?
They are usually priced as part of a larger project. Published US bands run from $8,000 to $25,000 for a clickable prototype and $8,000 to $25,000 for app design on one platform; Progression sets its price in the written proposal.
Which business details help the first wireframing session most?
The one task customers should finish, how they do it today, the information you need from them, your business rules, the words customers use and who signs off.
Does Progression’s team also build the app after the wireframes?
Yes. Progression’s designers and developers work as one team based in New York, wireframing, designing and building apps for businesses across the US, with on-site sessions on request.

An app idea that lives in a notes file?Send the notes and the one task customers should finish. You get a free proposal for app design wireframes that turn the idea into screens your team can argue over.

Get a free proposalTell us about a project you’d like help with.

Get a free marketing proposal

Tell us what you are trying to grow and we will come back with a plan, not a pitch deck. Same-day reply on weekdays.

Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.
Contact Us