What do discovery weeks establish?
Discovery weeks establish the foundation every later phase builds on, and firms hold this stage to two or three weeks for a typical app. Designers interview stakeholders, study analytics, map existing flows, and watch real users where the product already exists. Teams researching partners through a UI UX Design Firms list directory often ask why firms refuse to skip straight to screens, and the answer sits in this stage’s output.
- An agreed problem definition signed by both sides.
- A user picture grounded in observed behaviour,
- A prioritised flow list shapes the whole schedule.
Apps skipping discovery reach design faster and revision slower, since every wrong assumption caught later costs a full round. Firms treat these opening weeks as schedule insurance, and clients who supply analytics, past research, and quick stakeholder access routinely compress the stage from three weeks to two. The compression depends entirely on client readiness rather than firm speed, which makes discovery the one phase whose length the client largely controls before the contract even starts.
Wireframe the month in sequence
The month after discovery belongs to wireframes, because structure must settle before appearance gets any attention. Firms draw every core flow in low fidelity, test the drafts with a handful of users, and adjust while changes still cost hours.
A typical wireframe month runs in sequence.
- Core flows drafted across the first week.
- Internal review and structural corrections in the second.
- User testing on clickable drafts through the third.
- The revised structure was locked by the fourth.
Complex apps stretch the stage while simple ones compress it.
- Heavy data screens push toward six weeks,
- Role-based views add a week per role type,
- Single-purpose apps finish in three.
Locked wireframes then anchor everything after, and firms guard this lock firmly, since reopening the structure mid-visual doubles the remaining schedule. Clients feeling tempted to revisit locked flows should weigh the true cost, because one reopened structure ripples through every screen already styled on top of it.
Final visual and handoff weeks
Visual design and handoff close the engagement across the final month, splitting roughly into three weeks of screens and one of transfer. Designers apply the visual language across locked wireframes, build the component set, and polish the states a real app needs, empty screens, errors, and loading moments that separate finished products from demos. Handoff week then packages the work for engineering.
- Organised files with layers named for building,
- Interaction notes covering every state change,
- A walkthrough call where developers question each screen.
Firms adding a support window of a few weeks after handoff prevent the small misreadings that otherwise surface in the built product. Counting every stage, a standard app runs three to four months from kickoff to handoff, and quoted schedules far shorter usually signal a stage quietly removed. Teams comparing proposals should ask which stage absorbed the cut, since the missing weeks reappear later as revision rounds nobody budgeted.
Discovery sets the base, wireframes settle the structure, visuals complete the surface, and handoff moves it all to engineering. Teams reading a firm’s proposed timeline against these stages spot missing weeks before signing, rather than during delivery.