Lessons Learned From An App Graveyard

The article uses the author’s “app graveyard” to show why many mobile apps get downloaded but rarely stay in use. The main point is that an app should solve a real need, work reliably, respect device resources and user data, and make a strong first impression.

Reading notes

#

• Many downloaded apps are abandoned, deleted, or ignored, so the author keeps neglected apps on the device as reminders of what caused them to fail.
• An app is not always necessary if a responsive website or web app can serve the content and functionality well enough.
• Apps should work as expected, especially after updates or OS releases, and testing on real devices plus analytics can help find failures.
• Apps should avoid draining memory, bandwidth, battery, or location services, and should disable location updates as soon as possible.
• Mobile design should follow platform conventions and give users guidance when an interaction model is unfamiliar.
• Apps that handle sensitive data need to explain why they ask for information and how they use it, and they should avoid unnecessary registration or sign-in.
• Apps that create or store user data should let people save, back up, or archive it so the data is not lost if the app is discontinued or updated.
• App descriptions should clearly state what is included and what requires in-app purchase, and users should not be forced to rate or share the app to unlock paid features.
• Apps should load quickly and let users start using them immediately, without splash screens or loud launch effects.
• Marketing and incentives can drive downloads, but they do not ensure continued use.
• Platform updates can make third-party apps redundant, so apps need functionality or experience that remains useful after new OS features arrive.
• Developers should watch reviews, support messages, and other feedback, then address the problems that lead users to abandon the app.