How to build a successful mobile app.
Or how we got to 50,000 downloads with no marketing.
Disclaimer: 50,000 downloads might sound like a measly number to those who regularly follow the tech space, but to a pair of college students who built an unstable, utility app (with no UI to speak of), for fun in their spare time, and left it to rot on Google Play for 18 months, that number was mind-boggling. The following post is as much for ourselves as it is for everyone else — about the lessons we learnt and the things we need to keep in mind when we get down to building a real product in the future.
During the summer of 2012, a friend and I were doing our technical internships in different companies, just like the rest of our class- it was a part of coursework. It was pretty boring, and we decided to build an app in our spare time. Suhas came up with the idea for an app that notified you when your friend came online on Facebook. This was when not everyone had a smartphone yet, and Whatsapp wasn’t being used as much. So the only way that people strewn all over the world would communicate was when they logged on to Facebook on their laptops. More often than not, you’d login and stick around waiting for someone relevant to chat with. So the idea was to have this little app to keep checking when your closest friends came online. Simple as that. So Suhas dug around a little into Facebook’s APIs and we came up with an app called Onliner. We uploaded it on Google play, told all our friends about it on Facebook, and that’s about it. Nothing after that for ages.
When we logged into our developer account a year later, there was this sudden spike. People were actually using this thing! And it kept adding users slowly but steadily.
Two weeks ago, we crossed 50,000 downloads.
All this with no support, no marketing and most importantly the fact that it actually didn’t work too well( it was buggy and used to crash a lot). So what did the whole episode teach us?
1. Solve a problem, solve your own problem- The important thing is to build a solution to a problem and not the other way around. And when it’s a problem that you face personally, you’ll know exactly what you’re working to solve. It’s ok if the only customer you know is you — you’ll soon find other people with the same problem once you build the solution.
Get Chaitanya Krishna’s stories in your inbox
Join Medium for free to get updates from this writer.
2. Functionality matters a lot more than the UI- For the record, our app looked atrocious. Till about a month ago, it still used default gingerbread elements and was an eyesore on beautiful holo themed jellybean phones. But apparently, people didn’t care. No other app had this functionality at the time (AFAIK), and people didn’t care as long as it did the job. Sure, the UI is important and can be a huge differentiator in a crowded space, but make sure the app does what it’s supposed to do first, and that it does it well.
3. Just do it — Suhas works for an android startup now, and when he looked at the app’s code a month ago, he didn’t know whether to laugh or to cry. Horrendous would be an understatement! The code was so unbelievably amateurish that it was laughable that we put it out for other people to download. Oh and wait till you hear about our choice of version control.
The point is that there’s only so much you can learn by reading and thinking. Getting down and dirty is the only way you’ll make significant progress with any skill that you’re trying to master. So hankering over how little you know and how you aren’t ready yet really doesn’t cut it — start doing things, and you’ll figure it out along the way.
4. Perfection is iterative, don’t chase it the first time — There’s a good chance that what you build isn’t going to be great the first time round. It’ll go through multiple iterations before it resembles anything awesome. So even if you think you have a Jobs-esque eye for design, stop fussing over the small stuff, at least early on. Facebook, with it’s 1.3 billion users, needs to worry about which shade of blue it uses in each app version. As a startup or indie app maker, that’s the last thing that matters to you. As Eric Ries would say, get an MVP out and see if people actually use the damn thing.
So there you go. We got really, really lucky and this was an attempt to look at why. To be honest, we didn’t follow everything that I’ve said above, but this article is a reminder to ourselves about the things that we should focus on, when we work on actual products in the future. Hope this helps.
PS: You can check out the app we made( Onliner-Notifier for Facebook ) right here:
https://play.google.com/store/apps/details?id=flashbang.apps.fbtrack
If you have any questions about how the app was coded or need any help with Android app coding and the like, do not hesitate to contact Suhas (Facebook/Quora) or me!
Do hit the Recommend button below if you liked the article.








