It can be frustrating when things don’t go our way, especially when it comes to mobile devices, like the recent 02 disaster many people had to endure.
You may have little sympathy for the companies who are to blame when things go wrong, so I thought it would be a good idea to show you Mashable’s top 10 reasons for why App’s fail.
This has be taken from Mashable’s website:
1.Demand Exceeds Supply
It’s a classic case of the dangers of success — the fact that millions of consumers can simultaneously discover your app at the same time.
2. Incorrect Memory and CPU Usage
Made more challenging by the vast array of different devices that can run apps. As Dave Murphy, SOASTA’s Senior VP of Delivery puts it, “You can’t just test on a 64-gig third generation iPad and expect that to work [like] an 8 gig first generation iPhone.”
3. Bandwidth Constraints
Whether it’s inadequate bandwidth, or overly large data payloads, the pipe matters. Especially since mobile users expect quick response times.
4. Network Changes
Switching from cellular networks to WiFi and back can cause lost connections, which affects app stability. Murphy notes, “It’s not necessarily a problem ‘solved’ by the OS, so it is something that the developers need to account for.”
5. Fatal Bugs in Production
This can often come into play when a new feature is introduced that may have an impact on another part of the application.
6. Poor Front-End Optimization
Even for local apps that don’t talk to a back-end server, using resources effectively is key. Image compression and other strategies can help, but devs need to be mindful of the relationship between what’s happening on-screen and what the devices are capable of handling.
7. Integration Dependencies
How all of the back-end systems come together to deliver content to the user can have a tremendous effect on app usability.
8. Database Contention
Bad queries and excessive sessions can quickly drag down performance. Murphy cautions, “If you haven’t properly optimized and indexed your database, the database is going to perform poorly. But from the user’s perspective, all they know is that the application isn’t responding.”
9. Browser Incompatibility
Browser problems aren’t just a desktop phenomenon. According to SOASTA, Apple’s done a good job of building a “walled garden” with the mobile version of Safari, but app interactions with Chrome and other third-party browsers often don’t get tested, particularly on iOS.
10. Device Incompatibility
It’s impossible to test on every Android device, and even iOS has a fair amount of fragmentation. As Murphy puts it “something that runs on an iPod touch all the way [up] to an iPad — you’ll start to see some differences [in performance].”
So now you are aware of just why apps can fail, will it make you less angry at the company who produces them?
Or do you still expect them to work consistently?