A prototype is not an MVP.

Strategy · 5 min read

These two terms get thrown around like they mean the same thing. They don't. And confusing them can lead to some expensive misunderstandings about what you're getting, what you're paying for, and how far along you actually are.

Let me break it down simply.

What is a prototype?

A prototype is a clickable, interactive representation of your app. You can tap through it on your phone. You can show it to people. It looks and feels like a real app. But underneath, there's nothing. No backend, no database, no real data, no actual functionality. It's a simulation.

That's what comes out of the design phase. Every screen designed, every flow mapped, every interaction considered. It's built in a tool like Figma and it's detailed enough that you can put it in front of real users and watch how they navigate it. You can test whether people understand it, whether the flow makes sense, whether the layout feels right.

A prototype is also what your developer uses as the blueprint. It tells them exactly what to build, how it should look, and how every screen connects. The better the prototype, the cheaper and faster the development.

What is an MVP?

An MVP is the finished first product. It's coded. It works. It's on the App Store or Google Play. Real people can download it, sign up, and use it. Data goes in, things happen, results come out. It's a real, functioning application.

But it's the minimum version. It's not your full vision with every feature you've ever imagined. It's the simplest version of your app that still solves the core problem you set out to solve. You ship it, you watch what happens, and you learn from real usage.

The MVP is where you find out if your idea actually has legs. Not whether people say they'd use it, but whether they actually do.

Why the difference matters

The prototype proves the design works. The MVP proves the business works. They're different stages of the same journey, and each one answers a different question.

The prototype asks: does this make sense? Can people navigate it? Does the flow feel right? Is the experience intuitive? Does it look and feel the way it should?

The MVP asks: will people actually use this? Will they pay for it? Does it solve the problem well enough that they come back? Is there a real market here?

You need the first one before you build the second. If you skip the prototype and go straight to development, you're building on assumptions. And assumptions are the most expensive thing in app development. Every wrong assumption is a feature that gets rebuilt, a flow that gets redesigned, or a screen that gets thrown out entirely.

And here's the thing most people don't realise: a good designer understands that the MVP isn't just a design problem. It's a business problem. The MVP is about you, the person building the business. Your goals. Your market. Your budget. Your timeline.

A designer who isn't thinking about this side of things will hand over a pretty Figma file and wish you luck. But they won't have considered what it'll cost to develop, how to position it on the App Store, what your go-to-market strategy looks like, how to pitch it to investors, or how to communicate the value to potential partners. They're designing screens. They're not designing a product that succeeds.

The designer you want is the one who's thinking about all of this from day one. Someone who designs with the developer in mind, with your marketing strategy in mind, with your business model in mind. Because the prototype isn't just a set of screens. It's the foundation for everything that comes after. And if the foundation doesn't account for the business, the business will feel it.

If you're a subject matter expert, this is your advantage

If you've been working in your industry for ten, fifteen, twenty years, you already know the problem inside out. You know the workarounds. You know what frustrates people. You know what's been tried and why it didn't work.

That expertise means your prototype is already grounded in reality. It's not a guess. It's informed by years of watching the problem play out every day. And when that prototype becomes an MVP and lands in front of real users in your industry, you'll know immediately whether it's working. You'll recognise the feedback. You'll understand the edge cases. You'll know which complaints matter and which ones are noise.

That's a massive advantage over someone who's guessing from the outside.

The journey from idea to launched product

Here's how it actually works, step by step:

Idea. You've got a problem worth solving and an idea for how to solve it.

Research and design. We dig into your users, your competitors, and your market. We design every screen, every flow, every interaction. The output is a detailed prototype you can tap through on your phone.

Development. A developer takes the prototype and builds the real thing. Backend, database, infrastructure, the works. This is where the app goes from looking like it works to actually working.

Launch. Your MVP goes live. Real users download it and start using it.

Learn. You watch what happens. What do people actually use? Where do they drop off? What do they ask for? This is the gold.

Iterate. You improve the app based on real data, not assumptions. Add features people actually want. Remove the ones they don't. This is how successful apps are built.

What you're paying for with me

When you work with me, you're getting the design phase. That means the research, the strategy, the wireframes, the visual design, the branding, and a fully interactive prototype that's ready to hand to a developer. I'll also lightly code the front end of your app. That's the visual layer, the screens, the layout, the interactions, everything the user actually sees and touches. Your developer gets this code along with the design files, giving them a real frame and logic to build from rather than starting from scratch. With the AI tooling available now, a good developer can take that code and move significantly faster.

You're not getting a coded, fully working app. That's the development phase, and it's a separate step. But because the design is thorough, the prototype is detailed, and the developer handoff is clean, the build goes faster and costs less than if you'd skipped this step entirely.

The prototype gets you to a point where you can see your app, feel your app, test your app, and show it to investors, partners, or users. The MVP comes next, and I'll connect you with developers I trust to make it happen.

You can see exactly what's included at each pricing tier.

Related blog posts:

Why subject matter experts build the best apps →

What is an MVP and why should your first app be one? →