A few weeks ago, I spoke on the iPhreaks podcast, which I thoroughly recommend if you’re an iOS developer. While the podcast mostly focuses on the technical aspects of the iOS ecosystem, we took a little break this episode to talk about how to validate an app idea before writing code, something I write quite a bit about on this blog and my six-part email course.
I had an awesome experience being a guest on the podcast because it gave me an opportunity to aggregate all my writings into a coherent story–something an audience can digest in under 60 minutes.
Here is a rough outline of what we talked about:
- Identifying a customer segment
- Finding a painful or itchy problem
- Validating that the pain or itch is real
- How are they currently scratching it?
- What do they like/dislike about existing solutions?
- Prototype solutions & get feedback
- Marketing validation - how will you get people through the door?
- Build an early access list, use it as beta list AND interview candidates
- Build an MVP, Beta testing the app
I love this outline because it’s also a step-by-step roadmap of how to validate an app idea. The beauty of it is that anyone with the capability to build an app can do this.
Why is this important?
- Writing code is expensive;
- designing is expensive;
- marketing is expensive;
- shipping an app that doesn’t solve a real problem is expensive.
The goal is to maximize your chance of building an app users are happy to pay for. Validating an app idea gives you the best chance at creating something that can eventually turn into a business. To hear me elaborate on each of these points, take a listen here.
If this is the first time you are seeing about these concepts, I’d recommend you subscribe to my free six-part email course below, which walks you through each step in detail.