The biggest mistakes mobile app developers make

What are the most common mistakes that are being made by mobile application developers?

Well, many of them to be honest hardly care what they produce and focus on how financially rewarding the night after it’s being released is, but what they don’t know is that it’s not about how much of a hit it was the night it was released, it’s how much people tend to use it, and the more something is used, the more it is needed, these guys need to make their made apps into needs, not wants, since wants end, needs don’t. One of the main mistakes they make is giving up too early. If you look at the apps that made it big, they’ve often been growing for a year or more, or they’re only the most recent of several apps that have been made by the developer. ‘Overnight success’ can take a long time. The most common mistake is to neglect marketing. A developer cannot merely build and ship a product. He/she also must have a plan to market the apps. Most apps stores are filled, and to succeed you must get noticed. The biggest mistake developers make is focusing on downloads versus usage. Some of them chase trends too much and then app stores end up clogged with similar apps.

The key to designing and building good software is to have a comprehensive understanding of how and where it fits into today’s world. I know it’s a lot to ask developers to also be aware of the business and world requirements. But everybody involved in the chain needs to be able to put themselves into the shoes of the end customers (whatever the target market has been identified to be). Do this objectively and then decide what part of that end users life this app will actually impact (good and bad). Every mobile app needs a story. There is a villain and a hero. The hero must win in the end. Otherwise, who cares?


Lina Deveikyte

Marketing Manager


2 thoughts on “The biggest mistakes mobile app developers make”

  1. I think the biggest problem is one that affects all software developers and that is that the app/software is often designed with a mindset of ‘How would I do this task’ rather than ‘How would the end user do this task’. Often this is down to gaps in the customer research. Its better to delay development to get more research/End user testing completed than to simply rush it and get it out early.

  2. infact it is not only “How would an end user do this task” .. if we can go one step further and see ” How can this help end user optimize his/her task and can be used for many years” then it would be great and you will find applications not only relevant to the “wants” of the user, but also will help him/her on doing their task better and can be used for long time.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s