I read a recent CNET article by Don Reisinger, "98 Billion Apps to be Downloaded in 2015, Study Says." It made me question, how many companies are creating apps just because their client wants one or just because they can?

Wanting one and needing one are two different things. Wanting one because everyone has one, especially their competitors, isn't a sound enough reason to make one, because:

1. You'll lose money on it.
2. You won't get the downloads you hoped for.
3. You're not creating something your audience wants or needs.
4. If your web site isn't getting big hits, an app won't find the audience for you.

Some apps are no-brainers. I use my bank app all the time. Some apps I download just to see what it's like and then I move on. I don't need it taking up space on my phone.
If you're developing an app for a client or class project, here are things to keep in mind:

1. Make it sure it functions.  Really? Yes. Think about all of the buggy apps you've downloaded. Test and test again. Does it work with or without WIFI? Does it eat up a lot of data? What happens if phone service is interrupted? API? There's lots to consider.
2. Is it useful? Your app should add ease to the service the brand provides. Don't link me to your website. That's what bookmarks are for. Don't recreate the web site. This should be a simplified version of your service. Also, it should offer some service that can only be provided by the app.
3. Has your app been done before? If you're creating an app because your competitor has one, explore and push for ways yours can be better. Find the advantage.
   
4. Ads. If you must promote or sell space on the app, don't clutter or hurt the function. It sounds like another no-brainer, but then why do we see it all the time?

An app for app sake is not an ideal assignment, but you can rise above it by digging deep and creating valuable function and content.