How to Design an App: Spaceberry’s Workflow from Discovery to MVP
By Bohdan Ostafiiv7 min readingNov 21, 2025

- 1. Discovery and strategy
- How we turn insights into a plan
- 2. UX and information architecture
- Practical steps for UX and IA
- 3. UI and the design system
- Building a practical design system
- 4. Prototyping, usability testing and iteration
- Iteration cycles
- 5. Engineering and cross-platform handoff
- 6. MVP, roadmap and ongoing optimization
- How long it takes: real timelines
- Checklist: what to do next
- Conclusion
- FAQ
- What are the main stages of app design?
- How long does it take to design an app?
- Do you need a design system for an MVP?
At Spaceberry Studio, we treat app design as a journey from a problem to a working product, not a sprint to a pretty mockup. Good app design starts by aligning user intent, business strategy and technical feasibility. Below is the workflow we use, phase by phase, with real examples from apps we have designed: what we do, what we deliver and how long it tends to take.
Whether you’re launching a fintech product, a health app or a consumer app, the core workflow stays the same: discover, define, design, test and iterate.
1. Discovery and strategy
Great apps begin with clarity. The discovery phase establishes the problem worth solving, the audience and the metrics that will define success. Without it, even the prettiest UI struggles to move the needle.
What discovery includes:
- Stakeholder interviews to align business goals with user needs
- A competitive audit to find opportunities and differentiators
- Target user personas and problem statements
- Contextual research and a heuristic review of existing solutions
- A priority roadmap and success metrics (north-star metric, activation, retention)
Discovery doesn’t have to be long to be useful. For Meter Scanner, a utility app for submitting meter readings, we interviewed 30 people: 28 of them were frustrated by logging in to a different web service for each meter, and 25 wanted to update everything in one session. Those two numbers shaped the whole product. For Crush, a dating app with a one-month timeline, discovery was a focused review of Tinder, Bumble, Hinge and Happn plus conversations with the founder about what had to change.
How we turn insights into a plan
- Convert findings into 2–3 core user journeys that matter most
- Draft a lightweight information architecture that supports those journeys
- Define success criteria for each journey (conversion, activation, retention)
- Set guardrails for scope and risk to avoid early feature creep
Tip: document decisions in a short design brief with a hypothesis for each major feature. It makes testing easier and helps explain decisions to non-design stakeholders.
2. UX and information architecture
UX design is where research turns into usable paths. We focus on information architecture (IA), user flows and task analysis, so every screen serves a purpose and every action moves the user forward.
- Task-first user flows that map end-to-end goals
- Low-fidelity wireframes to validate structure before visuals
- Card sorting and IA diagrams to optimize navigation
- Accessibility built into the IA and navigation from the start
For Farm.One, a New York vertical farm, we started with a mind map of the platform’s information architecture to rethink its structure and plan new functionality: subscriptions, order tracking, delivery information and a product catalog with filters. In usability testing of the redesign, setting up a recurring order took 60 seconds on average.
Practical steps for UX and IA
- Define the primary tasks for each persona and prioritize them
- Create end-to-end flows with error handling and success states
- Prototype the core flows in clickable form for early feedback
- Validate the IA with quick tree tests and card sorts
3. UI and the design system
With the UX foundation in place, UI design brings in the brand, personality and accessibility. Our UI work centers on a design system that scales across platforms and screen sizes.
- Consistent components: buttons, inputs, cards and navigation
- Typography, color and contrast that support readability
- Micro-interactions that communicate state changes without distraction
- Performance-conscious visuals and accessible patterns for keyboard and screen readers
On large products we often build the system before the screens. For Sandi+, a B2B wholesale platform, we started with color, accessibility, iconography, typography, grid and a complete UI kit, and only began designing pages once the system was approved: web app first, then mobile, then native apps. For IONA Pay, a token-based design system with light and dark modes held together 180+ screens and 20 flows for iOS and Android.
Building a practical design system
- Core tokens: color, typography, spacing and elevation
- A component library with variants for states and accessibility
- Documentation that engineers and product managers can follow
- Guidelines for motion and interaction cues
For an MVP, start with a small set of reusable components and grow the system as new features land. It keeps the project nimble and reduces rework.
4. Prototyping, usability testing and iteration
Prototyping bridges concept and reality. We build testable prototypes your team and your users can explore long before production code is written, and usability testing confirms the design solves real problems.
- Clickable prototypes that simulate key interactions
- Realistic onboarding flows and error states
- On-device tests to capture genuine behavior
- Metrics: task success rate, time on task and satisfaction
Testing with real users changes products. On Salud.ia, an AI health and longevity platform, alpha-user feedback led to a redesign of onboarding and the dashboard before the beta release: we found and fixed 18+ usability issues, cut the steps to first meaningful value by about 30% and made onboarding about 25% faster.
Iteration cycles
- Run a short design sprint for the core flows
- Test with 5–7 representative users and synthesize the learnings
- Prioritize changes that unlock the most value with the least risk
- Update the design system and documentation
Explore options early, while they’re cheap. On PickLang, an AI language-learning app, we designed three test screens and chose the strongest before the main work began; for Crush we did the same with three variations of the main screen. More on this in our guide to rapid prototyping.
5. Engineering and cross-platform handoff
Design without engineering feasibility is just art. We talk to product and engineering teams early so design decisions are implementable and maintainable, considering platform differences (iOS vs Android), performance budgets and cross-platform strategies (native, React Native, Flutter).
- Platform conventions and accessibility guidelines per OS
- Performance budgets for images, animations and network calls
- A handoff with precise specs and assets
- QA on real devices
The working rhythm adapts to the team. On PickLang, design and development first worked in weekly sprints and later moved to working on request, as the client’s CEO noted in their review. On Vera, a generative AI platform, we aligned the interface to a 4-pixel grid to simplify implementation and supported the client through development to make sure the build matched the design.
6. MVP, roadmap and ongoing optimization
Every app starts with an MVP that tests the critical assumptions while delivering real value. We map a roadmap that balances quick wins with longer-term investments, guided by data and user feedback.
- MVP success criteria tied to core user tasks
- A staged rollout (soft launch, metrics, feedback loops)
- An ongoing optimization cycle (A/B tests, usability tests, analytics reviews)
- Design-system discipline to support future growth
How long it takes: real timelines
Timelines depend on scope, but here is what this workflow looked like on recent projects:
- Crush - one month from concept to handoff, including a logo and illustrations; a clickable prototype within 30 days. The app is live with a 5.0★ App Store rating and 10K+ downloads.
- Farm.One - estimated at 320 hours (about two months), and the estimate matched the actual time: three iterations, with 160 hours of UI/UX design and 80 hours of finalizing.
- IONA Pay - a clickable prototype in 60 days and a live MVP in 16 weeks; core actions became about 40% faster (from 2 to 1.2 minutes).
- Aura Pura - an interactive prototype in 85 days and an MVP within 20 weeks; the app has passed 500K+ downloads on Google Play.
- PickLang - five months of design for iOS and Android; it launched during the client’s fundraising stage, holds a 5.0★ rating from 32 App Store reviews and has shipped updates for 4+ years.
Checklist: what to do next
- Start with a crisp problem statement and a north-star metric
- Map the core user journeys and sketch a lean IA
- Build a design system skeleton early and grow it with the product
- Prototype the core flows and test them with representative users
- Confirm feasibility and performance budgets with engineering
- Plan the MVP and a data-driven iteration cycle
Conclusion
Good app design is a disciplined, iterative process that starts with user insight and ends with a scalable system. Our workflow - discovery, UX and IA, UI and design system, prototyping, engineering handoff and continuous optimization - is what lets us ship a prototype in weeks and an MVP in a few months. If you’re building or redesigning an app, see our mobile app design services or browse our case studies.
Related reading: mobile app layout ideas and UI/UX design deliverables at every stage.
FAQ
What are the main stages of app design?
Discovery and strategy, UX and information architecture, UI and the design system, prototyping and usability testing, engineering handoff, and the MVP with ongoing optimization.
How long does it take to design an app?
It depends on scope. On our projects, a focused redesign took one month (Crush), a clickable prototype for a new fintech app took 60 days and its live MVP 16 weeks (IONA Pay), and a full AI app for iOS and Android took five months (PickLang).
Do you need a design system for an MVP?
A small one, yes: core tokens and a handful of reusable components. It keeps the MVP consistent and makes every next feature faster to design and build.
- 1. Discovery and strategy
- How we turn insights into a plan
- 2. UX and information architecture
- Practical steps for UX and IA
- 3. UI and the design system
- Building a practical design system
- 4. Prototyping, usability testing and iteration
- Iteration cycles
- 5. Engineering and cross-platform handoff
- 6. MVP, roadmap and ongoing optimization
- How long it takes: real timelines
- Checklist: what to do next
- Conclusion
- FAQ
- What are the main stages of app design?
- How long does it take to design an app?
- Do you need a design system for an MVP?
Feel we’re a perfect match?
If we’ve managed to impress you with our works and you have no doubt that you’re ready to collaborate with us, choose your preferred way to reach out.
Want to test our skills?
We offer a free 3-day trial to explore our expertise and see how we add value to your project. Assess our skills and workflow before committing to a partnership.


