We also did something that I forgot to mention in the article that helped us grow nationally before we had a lot of proprietary data. One of the nice things about starting a company in 2017 is that there are tons of great resources available to you. Free or cheap services that solve what used to be really hard problems are readily available. One such service is Foursquare. When we launched Winnie, if you opened the app in an area where we didn't have data, instead of showing you nothing we instead showed you results from Foursquare. This was admittedly not the best experience, but it gave people affordance to still find places and write reviews.
Refusing to go market-by-market also forced us to build a bunch of proprietary and very cool infrastructure that collects data at scale. One early system we built could actually figure out which restaurants had changing tables and highchairs, nationally and instantaneously, at a VERY low cost. I can't say how we did that but you'd be surprised at what's possible if you have the will and ambition :)
Users don't care. Most of them can't tell.
It's definitely not required, it just helps. Our app got featured in one of the App Store's daily stories despite it being written in React Native.
Name one.
Developer apathy becomes user apathy. If you make great apps, your customers will be enthusiastic about using them. If you make mediocre apps, you will attract mediocre users, or no users at all.
Mediocre apps are annoying, I agree, but that rarely has anything to do with the underlying technology.
What about for games? Unity is extremely tempting, especially when the alternative is to write the game twice in two different languages...
I'd honestly just lean in on PWAs if you're a content/SEO focussed business.
A company that does a respectable job of developing a nice-looking and performant native-application is going to stand very far apart from this crowd. The same company may have done just as well in terms of performance and UI conformity with React Native but will they stand out as well to tired and jaded reviewers? I think that is what the OP is getting at. No one can predict who will be featured, but true native is probably one thing that helps.
- Go true native, not hybrid
- Use ads for testing ideas
- Don't forget about email!
I'm also intrigued by your approach of not going market-by-market like a lot of local-focused marketplaces do. Your approach seems to make sense, and obviously worked for you. I particularly like that you had a different onboarding flow for users in new markets, that's smart.
But still, I'm not sure that this approach would make sense for a lot of local-focused apps? I think the fear would be that it would be relatively easy to get 100k users but they'd be spread out so thin that they'd find little utility in the app and stop using it. So you'd have 100k users in your database, but a tiny fraction of that in terms of actual active users. But maybe that doesn't even matter, since you wouldn't have had all those inactive users anyway?
Could you speak to that? I'd love to hear how many of those 100k users are DAU or MAU, but understand if you can't share that :)
Congrats!