12 questions to ask before you build an app
Ian Lurie Mar 8 2012
Rick Santorum throws up at JFK speeches. I throw up when someone says “We want to build an i[whatever] app!”
I have one question.
Have you really, really considered why you’re building your app? Here’s 10 questions to help you decide:
- Can I afford it? I’m sorry, but you can’t build a quality mobile app for $750. Billy-Bob’s House of Apps isn’t going to give you something that’s worth showing the public. Between wireframing, concept, design and development, you’re going to spend a nice chunk of change.
- Does my existing audience use any apps? Huh. Might be worth thinking that one through for a second. If 75% of your customers have never touched an iPad, much less played Angry Birds, you may not get much from a shiny new app.
- Is there a new audience I can reach with an app? No new audience + no old audience = zilch. Zero. Zip. Nada. Nicht.
- Does anyone come to my web site using a mobile device? Only 1% of visitors to your site are using an iPad, iPhone or smartphone. That might not mean an app is a bad bet. Yeah. The same way SuperPACs might not mean more crappy campaign ads.
- Can I get the same result by making my site mobile-friendly? Ah. This one gets to the heart of things. If all you’re going to do with your app is deliver a list of headlines from your web site (don’t laugh, I’ve seen plenty of those), maybe you can tweak your site so it behaves itself on a little screen. Even if you end up building an app later, this is a great interim step. It lets you test the waters a little.
- Can I get the same result with an HTML 5, mobile-dedicated site? If so, it’ll likely be a hell of a lot easier than building an app from scratch.
- Is there already an app like mine? Hey! I know! Let’s build an app called ‘angry Portents,’ where you use a slingshot to shoot angry Portent logos at little pigs! It’ll be great! Wait.
- Can I support it? Yeah. For every 1,000 people who download your app with zero issues, someone’s going to have something go wrong. You’re going to have to help them fix it, or pay someone else to fix it.
- Can I handle the haters? People love to release their angst on app review pages. The happy app users rarely write anything. It’s the miserable ones, living in their house with 32 cats while they plan for the coming zombie infestation, who tend to review your software. If you’re going to panic the first time you get one star, consider a pause.
- Do I have a goal for this software? If you’re building an app because a competitor has one, you’re liable to end up roadkill.
- Can I offer something as a premium? If you can use your app to deliver premium content, or a better shopping experience, or just a warm tingly feeling because I don’t have get up off my couch any more, it might be worth it. People like to feel special. If your app can do that, you should build it.
- Can I reduce costs? Maybe switching a print manual or journal will result in huge cost savings. OK then. Go build that sucker.
I love apps—don’t get me wrong. They’re fantastic, and I’m an iPad addict. But those little mobile programs are a lot more complicated than they look. Building one is a big investment, not just up front but in long-term support. Make sure there’s a reason, and that you’re ready.
Ian Lurie is CEO and founder of Portent Inc. He's recorded training for Lynda.com, writes regularly for the Portent Blog and has been published on AllThingsD, Forbes.com and TechCrunch. Ian speaks at conferences around the world, including SearchLove, MozCon, SIC and ad:Tech. Follow him on Twitter at portentint. He also just published a book about strategy for services businesses: One Trick Ponies Get Shot, available on Kindle. Read More