3 Lessons from #MoDevTablet
Does your startup have a mobile application component? You’re certainly not alone, and that app should be more than just a mobile-aware website. That’s one thing that I heard repeated at the #MoDevTablet conference last Friday just outside Washington DC.
Here are 3 other lessons you should consider for your mobile project:
1. Measure and fix. Repeat.
Manuel Mattke from Hydra Insight gave a talk on product management skills that every entrepreneur should know, and his fifth one was “Measure and fix. Repeat.” That type of advice is solid and should not be a surprise to anyone following the lean startup movement. But how do you measure things in a mobile app? It’s not the same as web development. Manuel recommended using Mixpanel or Kissmetrics for tracking user patterns in the mobile app and learning from them. I also met the app47 team at the conference – their developer edition also provides built in analytics to your app.
2. Tablets and Smartphones are not the same
Is your app intended for smartphone use or tablet use? Or both? Consider this distinction carefully. There were a lot of mobile frameworks on display at the conference (such as Appcelerator, PhoneGap, Enyo, and more). Any of these frameworks will help you produce apps that run well on both iOS and Android devices, including different screen sizes. But producing an app that works well on both smartphone and tablets is not just about code that ports easily, it’s also about design and UX. You have a lot more real estate to play with on a tablet, and I heard one speaker admit that they sometimes had a hard time filling that space up. Consider how your app can provide a richer experience when run on a tablet.
3. Want to be profitable? Give your app away for free!
It sounds a little bit backwards, but free apps were definitely the consensus of multiple speakers at MoDevTablet, including Todd Moore, author of “Tap, Move, Shake: Turning your game ideas into iPhone & iPad apps”.
Many of the speakers recommended you will make more profitable apps with one of these options:
- advertisements in the free apps
- “in house” ads in your free apps that cross promote your other free or paid apps
- in-app purchases
- a paid subscription back end to your mobile app
Todd talked about still having paid versions of apps too, but those should probably not have in-app purchases. Pick one model or the other, but trying both doesn’t work well in his experience.
A few other tidbits
There were a lot of other tidbits that I heard from various speakers, and I’ll just regurgitate a few more here. Not all context is provided, so take these with a grain of salt:
- HTML5 based mobile apps have been a bust. Just ask Facebook.
- Some say “go native or go home”, others say “our framework removes the need for Objective C or Java.” I’m not going to choose sides on this religious war, but I will say research your development platform carefully before committing to it.
- Ask customers to send you feedback directly in your app, it’s more meaningful than what is written in app store reviews.
- Don’t ask users to review your app until a few days after they use it for the first time. If they are still using the app after a few days, that probably means you will get a more favorable review.
- Business people are attracted to apps with the word “Pro” in them. Others are attracted to apps with the word “Free” in them. Know your audience.
- Png’s are usually the best image type to use in your app, since iOS optimizes around it. The exception is “content” images like photos. Those should be jpg’s. Use a quality of about 60% on jpg’s, that is plenty on a mobile device.
- Your idea has probably been done before. Don’t give up on it just because of that. Learn from your competitors.
Are you ready for the real-time web?
RealTimeWeekly subscribers get a free copy of our e-book!