Most smartphones users I know ditch apps pretty quickly if they donâ€™t work or end up being clunky. So, if your company is considering offering mobile apps to your customers you should be aware of a few things.
Buy a Smartphone. If you donâ€™t already have a smartphone then you should go out and buy one. Then download a number of apps that interest you and try them out and see what you like and what you donâ€™t like. For example, if you do the shopping for your family you might consider trying out a bar code scanner app that lets you compare pricing. Some scanner apps may work faster than others. If you donâ€™t own a smartphone then you wonâ€™t be able to understand what a good app is.
Likes and Dislikes. Pay close attention to what you like and donâ€™t like about a particular app. Here are a few questions to take note of:
- Was it easy to use?
- Did it hang and/or crash?
- Did it perform its tasks gracefully?
- Did it do what you expected?
- Was it visually appealing?
Become Tech Savvy. Become a bit more tech savvy about things that the phone is doing behind the scene. There are apps that do this for both Android and iPhone that help you monitor whatâ€™s going one. Things to look out for:
- Apps that keep running even after you think you shut them off. These will run the battery down faster.
- Apps that consume more and more memory over time. Using more memory equals more battery usage and shorter time between charges.
- Apps that seem to slow your phone down when they run. These apps may be using more CPU than necessary resulting in greater battery usage.
- Apps that connect to the internet frequently costing you extra data charges. There are apps that let you monitor how much data your phone uses and some apps can help pinpoint which apps use the most data.
Which Phones to Support? Understand what devices to support. If you are building an application for internal use, then you have an easier decision since you hopefully have some control over which devices are being used and how often their software gets updated. If you work in retail, your users may have Androids, Blackberries, iPhones, iPads, Kindleâ€™s, Nookâ€™s and possibly other tablets that get updated whenever and however the customer dictates. My advice is do some research and pick one that is used the most and work on that first.
Release Early and Iterate Often. Technology changes so quickly these days that if your app takes more than 3 â€“ 6 months to build, then the technology will change underneath you. In other words, you might be releasing an application that doesnâ€™t work perfectly with the latest phone operating systems or browsers that your customers are using. When that happens, it will cost you even more time and money to fix the problem and the problem will repeat itself. Be sure to take into account the speed at which technology will change once you begin your software development process.
Go Native, Go Web Browser, or Both? Last, itâ€™s important to understand that there are two common types of mobile applications. Native apps are downloaded from an app store and installed directly on the phone, the other is a web app that runs in the phones web browser. My advice is to research and understand your target market. What do your competitors use? What do your customers prefer? What are the trends in your industry?
If you go with native apps, youâ€™ll need to understand which phones to support and how often you will be updating the app. If you choose web apps youâ€™ll need to know which browsers to support. Also take into consideration which skill sets your development team has and understand if they can tackle the project or if you need outside help.
Update, Update, Update. No matter what you decide, you canâ€™t just deploy an app and think youâ€™re done. If you want to keep your customers happy, youâ€™re going to have to keep updating the app until the product line is discontinued or replaced. And, you have to update it often enough to stay on top of the latest technologies. New smartphone models are being released all the time and they all may have different screen sizes and screen resolutions. An app that looks good at one screen size may look horrible on a tablet or iPad. These things have to be accounted for. And, the smartphones operating system software may be updatedÂ three or more times per year offering new functionality and fixing bugs. If your customers download a broken app, or if they see the appÂ that hasn’t been updated in a while and something stops workingÂ they may not be your customers for much longer. This is especially true for retail apps where customers make split second decisions whether to stay or walk away and try something else.
Conclusion. I hope you find this list useful and at least give you some ideas to think about before you dive head first into bringing a new mobile application into the world. It can be fun, be there is a lot of hard work involved. But, if you plan it right youâ€™ll be successful andÂ learn alotÂ in the process!