Built a prototype for an idea I had. Really confused on what to do next . Help!!

by og_realslimshady. Posted on Sep 15, 2020    4    9

Two weeks ago i had a unique app idea. I learnt Figma and built the prototype for the app in like two weeks. I showed the app prototype to some of my friends and they really seemed to like it. Now tbh i don't know what to do next. Should i go on and build an mvp (which might take 2-3 months) or should i do more market research, survey and pitch the prototype to more people. Feeling really lost any help would be appreciated. :)


heypeter-io 1

What you have right now is a bunch of hypothesis that you need to test in order to be sure that your unique value proposition, is real. So I would recommend:

  • Do some interviews not talking about the App (this is crucial) only talking about the problem you are solving.
  • Once you have that info, make the changes you think are necessary after the interaction with potential users.
  • Do an Usability Testing with the same users that you interviewed talking about the solution you have built. What's that? You will test your prototype with final users, only telling them that is a simulation.
  • Define your user persona and start shaping more and more your value proposition.
Mister_Story 1

There's some good advice from all the responses here.

Key first task is to determine if your product or service is something people are willing to pay for.

A combination of a landing page along with market research will help you determine if you have something worth investing in.

Paid surveys can be useful, they are a bit pricey but help you reach your target demographics. I don't recommend the bog standard paid surveys as those responding are more than likely only in there for the few dollars they are paid for responding to surveys.

DancinWithWolves 1

My thoughts:

Landing page clearly explaining the value of your app.

Get into online groups full of your target user, and discuss the problem solution (don't spam these groups). Offer a link and ask them for their feedback.

Get sign ups and speak more with those who do sign up.

Start doing the maths on the TAM and work out what those signups would want to pay.

That should take 2 - 4 more weeks.

Then, create the most basic version of it, and get them to actually start a subscription.

You now need to spend a bit of time talking with your potential users, asking them questions, seeing what the problem really is. It's one of the most effort intensive parts of the journey, but it's really critical.

You'll know after a few weeks of the above wether or not it's worth doing, and you can make a call then.

AdamKyleWilson 1

Do the research.
Paul Graham, the founder of Y-Combinator once stated that every startup fails for the same reason: making something nobody wants. A great idea is only part of the battle. Finding people willing to pay for it is another. Once those two things come together and you have validation in the market you should move on to attracting technical Co-founders, funding, and beyond. Good luck!

P.S. the fall / winter cohort of our idea-stage startup accelerator is starting soon if you want to really get this thing off the ground quickly. startupblueprint.io for more information. DM if you have any questions. Would love to teach you what we’ve learned after 100+ App Store product launches.

MaxPast 2

Ask your friends if they want to buy the product if it exists or if it's just "nice"?
If they refuse to pay, it just means that you are asking wrong people.

Your goal is to test your product on those who will potentially be willing to pay, not just get some feedback from strangers. And, when you are getting the feedback, your goal is to read between the lines, trying to guess what do your first users really need from it. It's not the product that matters, it's the purpose of it for your customers.

I don't recommend to start with building it right away, better spend yet another day or two looking for those who will actually pay for it when it's done. I'm sure that the final version of your prototype will be much different from the initial one after that.

ILoveHK2020 2

Might be a difficult thought process to fathom - go ahead and build it. Like end to end finished product. Invest 2-3 months.

It fails or not does not matter. But the real world experience of converting an idea to a finished product does. Once you find a hammer everything else becomes a nail.

weCo389 3

Seems like you are quite motivated and excited and that’s the most important thing. Don’t get bogged down into market research that will just confuse you and create doubt. Since it sounds like you’re building this yourself if you invest 2-3 months to take it to the next level what’s the worst that can happen? You learned a bunch of stuff and had a great experience at the expense of your Netflix binging time? Just keep running with it and the next steps will become apparent along the way. Don’t overthink it.

xAvi_r 5

What I would do if I was in your shoes:

  • create a nice landing page with some videos of your prototype (or even a signup to your app if it's working enough to be shown)

  • drive traffic to that page (ads, reddit, indiehacker, social media... Wherever your potential customers hang out) Try to get 1000 visitors

  • On that page put a "buy early access". Get the email of.people that actually click on that button (or even sell it)

    That should give you a good idea of the potential. If you plenty emails then you can start to code.

    Don't start with a 3months MVP if you don't know if there is a market!
Wahoopokie 7

Market research right away - is the outcome or output of your app already delivered by something else? How is profit achieved? Is there actually an existing audience for this - or will it create a new audience? Answers may become the input you need for the next round of work, investment, update, etc. - which is critical - i.e. the business plan. The tech is easy - so, so easy these days to actually create...but the brand, value, usefulness, uniqueness is not. So many spend so much time and money on building something based on an idea that may exist only within their own echo chamber - without looking around and getting insight, feedback.