Hacker News new | ask | show | jobs
by eytanlevit 4946 days ago
A very interesting read indeed.

The question that keeps bugging me is that maybe this guy is blaming the platform, but the real problem was that they built something people didn't really need.

Look at http://any.do, these guys launched mobile first and hit millions of users in an extremely crowded market(todo lists) because they've created a great product a lot of people want and use daily.

In the end, it sounds like(and I don't know their story from close, only judging from things written in this post) they raised too much money early on because they are a YC company(raising a lot of money actually makes you much slower), launched a product with a shitty signup funnel and took a lot of time to fix that.

Apple taking their time to approve new versions isn't new, anyone(especially a YC company surrounded with top mentors) knows that a/b testing in a mobile app is a problem that should be tackled upfront.

Personally, I'm tackling that problem by testing everything I can BEFORE I even start to write code.

I'm running ads on FB/Google, testing CTRs for different value propositions/positioning, driving users to a landing page where I'm testing different mockup ideas I have for each value proposition, testing the icon, testing price, testing feature list.

I'm talking with as many customers in my customer segment I can not only to understand their needs and problems, but also to create an initial user base that likes me enough to agree to install my app BEFORE I launch it in the appstore using TestFlight.

This will enable me to discover a lot of UX problems upfront and to test a very very very important question - Is what I've built a painkiller or a vitamin, which is the most important question (I think) mobile app devs should ask since it's clear that most apps are downloaded and then forgotten in the abyss of unused apps.

If someone has read this long reply and has more ideas on how to test this question before launching, I'd love to collect more ideas.

2 comments

>The question that keeps bugging me is that maybe this guy is blaming the platform, but the real problem was that they built something people didn't really need.

A thousand times yes. The market is way past saturation. It doesn't need yet another social network that will never ever be as successful as facebook.

Have you considered qualitative surveys and relative importance testing? I've found that useful for validation in the past