Companies from Fortune 500-size to startups use mobile applications to target customers, streamline their processes, provide a service or, increasingly, as the backbone of their own business. While there is currently a strong push for mobile-first (or even mobile-only) within the business ecosystem, there are a few things to consider before hiring the developer or writing the check.
Here are five things to consider before kicking off a mobile app project:
Identify your users: Is this app internally-facing or external (meaning customers will see it)? Who are the people using the app and what are the demographics? Who will serve as the admin who can add / delete users and data? Without drilling closely into this question, you might waste money building for what you think is your user and not who your real target audience is. Do not fall victim to this – early in the brainstorm process, get all key holders in a room for a discovery workshop to has out requirements and agree on direction.
Research your competition: If you are moving into a crowded space, building a matrix of your competitors can be very helpful in building an app of your own. Identify what you like and do not like about their applications – and why. Read their customer reviews and find out how users feel about the apps and what they are lacking. Then, see if that is something you can capitalize on.
What problem does my app solve? Maybe you are building an extension of your e-commerce website onto a mobile platform. Perhaps you want to take advantage of the features a phone provides like location, push notifications, and onsite photos in a new way. But beware – if your app is not going to enhance your existing business or present a unique interaction with users, really take some time to consider the money and time you are about to spend.
Native or Hybrid? For fast proof-of-concepts or simple data entry applications, a hybrid platform like Phonegap or Ionic might be the right choice. This option lets a development team save time by writing only one codebase that works for both iOS and Android. However, if you’re envisioning a more complex app, considering spending the extra time for native development, meaning a different build for the different operating systems of iOS and Android. This allows the app to utilize the latest features of a native-only experience, such as Apple Pay, rich push notifications, Android Pay and TouchID. These all let the developer and client utilize the innovation happening in our pockets and purses. Furthermore, in general, native apps see better mobile behavior and research shows are more accepted by users. However, the cost and time to market difference may be worth a discussion.
Plan for post launch: Okay, you have a great idea and the plan is in place. What happens after you launch? How will you gather and respond user feedback? Who will make changes for incremental releases – the original build team or someone in-house? And realize that mobile phones change often, with new functionality added every few months. An app is different in that, unlike a website, you can not make changes on the fly. Setting a plan with a release schedule to add features, make changes and continuously provide a reason for users to open the app will help you be successful once you release your new mobile baby to the wild.