Menu Search
Jump to the content X X
Smashing Conf Barcelona

You know, we use ad-blockers as well. We gotta keep those servers running though. Did you know that we publish useful books and run friendly conferences — crafted for pros like yourself? E.g. our upcoming SmashingConf Barcelona, dedicated to smart front-end techniques and design patterns.

Lessons Learned From An App Graveyard

Guesstimates by analysts put the number of mobile app downloads this year at somewhere between 56 and 82 billion1, with the average user downloading somewhere between 26 and 41 apps2, with a smaller subset of those apps being used on a regular basis. Other numbers indicate that 95% of downloaded apps are abandoned within a month and 26% of apps are only used once3.

Depending on the user, these abandoned apps are deleted or ignored, never to be opened again. I choose to leave these ignored apps on my phone and tablet, and at last count, I had over 375 apps on my iPhone. I turned off badges for my App Store app because it was a constant reminder that over 250 apps are waiting to be updated, which is intentional. A majority of those outdated apps lie in what I refer to as my app graveyard — buried beyond the first two screens of apps.

Lessons from an app graveyard
Illustration by Nancy C Xu.

My app graveyard is the final resting place for apps that I have downloaded, tried or used briefly but have since left neglected. I leave them on my phone and tablet as a constant reminder of what killed these apps. The following are lessons from my app graveyard that I keep in mind when designing apps, and they might help you, too.

Further Reading on SmashingMag:

Lesson 1: Validate The Need For An App Link

Don’t stretch Apple’s catchphrase “There’s an app for that” too far — not everything has to exist as an app. A recent study9 (PDF, 2 MB) by Compuware found that smartphone users prefer mobile apps to mobile websites, but other research10 shows organizational strategy shifting away from native mobile apps towards Web experiences. If your content and functionality can be better served to users through a responsive website or Web app, then you have no real need for a native app. While native apps can easily use a device’s capabilities, a few features, such as GPS, can be used by websites, too.

Couple that with offline storage and many websites can do whatever their native equivalents currently do. Visitors to Kansas City11 can easily do everything they need to from the VisitKC mobile website, instead of downloading and installing the dedicated app, which is now in my app graveyard.

Visit KC - site vs app12 (left) can do everything the VisitKC app (right) has to offer. (Large views: left13, right14)

How do you decide whether you need an app? The decision should be driven by business goals, user needs and the user experience. The short version is, if you plan to primarily offer content and basic functionality that users will access infrequently from different platforms and devices, then those users might be best served with a responsive website. Also, consider the time, effort and cost involved in creating a platform-specific native app, as well as the ongoing maintenance.

Additional Reading Link

Lesson 2: Make Sure The App Works As Expected Link

This one might sound like common sense, but you would be surprised by how many apps do not work as expected or end up crashing (see the image below), often after an update — and that’s not just from personal experience. One- and two-star reviews in the App Store often complain about just that. Look at reviews of Apple’s own Find My Friends or the beautifully designed alarm app Rise — when apps do not do the one thing they are supposed to do, users will stop using it or will use a competing app instead.

Staples’ app had problems authenticating users and would repeatedly lock users out of their accounts, even though the same credentials worked on the website. And the flight-tracking functionality in United’s app frequently does not work, although it works just fine on United’s mobile website, as shown below.

United's mobile app not as reliable as their mobile site19
(Large views: left20, right21)

One way to avoid this is by thoroughly testing your app22 when releasing a new version or after an OS release. Test on actual devices, with bonus points for testing in mobile contexts (for example, testing an alarm app during deep sleep). Another ongoing proactive method is to use analytics tools23 to monitor where your app fails users or even crashes.

Problems faced with mobile apps
Source: “Mobile Apps: What Consumers Really Need and Want4924,” Compuware (PDF, 2 MB)

Lesson 3: Don’t Drain The User’s Device Link

Apps should judiciously use a device’s resources, including memory, bandwidth and power. Apps that do not minimize their use of a device’s location capabilities or that do not disable location updates as soon as possible are common offenders. Earlier this year, the Taxi Magic app alone drained about 20% of my battery during a 40-minute ride to the airport, leaving me hunting for juice on my way home. Staples’ location-based alerts appear to be active and display the location-indicator arrow even after the app is closed, and even after the app says it will affect battery life (below).

Staples app location based alert issue
Before and after a Staples app update with location-based alerts. (Large views: left25, right26)

Apple’s “iOS App Programming Guide” offers some factors to consider when tuning an app’s performance27. Android has corresponding best practices28.

Lesson 4: Follow Design Standards And Guidelines Link

The mobile experience is built from individual elements29 that require careful consideration. For instance, apps with a unique interaction design should onboard new users with a quick introduction or a short tutorial on using the app upon first launching, with options for the user to skip and view it later. Yet many unintuitive apps do not do this or do not even offer help, forcing users to give up.

Spellcheck is not an option either, as Mitt Romney’s mobile developers quickly discovered last year when they misspelled “America” in one of their photo-sharing banners as “Amercia30”. Though the app was updated within a day, I did not update, but rather buried it in my app graveyard as a reminder that the little details matter.

With Mitt app spelled Amercia.
“Bart Simpson is with Mitt.” (Image: Joao Correia31)

When designing for different platforms, follow the design elements and conventions of the respective platforms, be it iOS32, Android33 or Windows34.

Lesson 5: Earn Your Users’ Trust By Addressing Privacy And Security Concerns Link

Ask only for what you need — don’t collect or access information that is not required for the app to function. Many apps need access to such device information as contacts, calendar and photos to be useful, but an app should be transparent about why it needs that data and how it will be used. Apps that consume or store sensitive information (such as financial data) should demonstrate their trustworthiness up front or risk being abandoned.

One app in my graveyard is Card Mate Pro, which stores credit-card information but does not impart a feeling of security or confidence. Another common reason that apps are abandoned is that they ask users to register (or use social sign-in) in order to gain functionality that does not depend on having a profile. The app for Moe’s Southwest Grill (a fast-food chain) required registration before users could use any functionality in the app, including locating restaurants and browsing the menu.

Moe's app required users to login to use the app
Previous versions of Moe’s app required users to register or log in to use it.

Additional Reading Link

  • “Best Practices for Mobile App Developers,” Future of Privacy Forum

Lesson 6: Give Users Control And Ownership Of Their Data Link

Apps that create, capture or store user data should offer a way for users to save, back up or archive that information. A couple of apps that capture and organize my kids’ artwork now lie in my app graveyard because there’s no way for me to save or back up those pictures to iCloud or Dropbox. Every app, free or paid, is at the mercy of its developer and can be discontinued at any time35 or removed from the App Store, as recently happened with the to-do app Orchestra36 and Apple’s own Cards. Enabling users to easily save their own data gives them confidence that they won’t lose it forever if the app were to be discontinued or automatically upgraded37.

Dead App infographic by Stardust
A part of
38StarDust’s mobile reputation infographic39 shows just how many apps are dead. (Large view40)

Lesson 7: Don’t Bait And Switch Link

Descriptions in the App Store (even for free apps) should clearly indicate what is included in the purchase price and what is available via in-app purchases, which will help users decide whether to buy and download that app. Not making this clear up front41 is wrong, as is forcing users to rate or share an app in order to enable features that they’ve already paid for.

Step Out Alarm Clock is one such app in my graveyard. While it forces you to wake up, it also forces you to rate the app to unlock features that are listed as part of the paid app. While we’re on the topic of ratings and reviews, when prompting users to rate an app, wait until they’ve had an opportunity to use it, and give them the option to rate it later or never rate it, and honor their selection.

Step Out Alarm App does a bait and switch
Step Out Alarm Clock forces users to rate the app to unlock features listed as part of the paid app.

Lesson 8: Load The App Quickly, Without Fanfare Or Annoyance Link

The “iOS Human Interface Guidelines42.” recommend enabling your users to begin using your app immediately:

“It’s often said that people spend no more than a minute or two evaluating a new app. When you make the most of this brief period by presenting useful content immediately, you pique the interest of new users and give all users a superior experience.”

Apple goes on to recommend avoiding a splash screen or other “launch” experience, and instead using a simple launch image43. While resource-intensive apps such as games need a few seconds to load, games are among the biggest offenders44 of the recommendation against splash screens. Moe’s Southwest Grill launches with its loud signature “Welcome to Moe’s” yell, without any option to mute it — which I discovered in a client’s quiet office. The developers have since listened to feedback, and an update last December allows users to mute the greeting.

Lesson 9: Marketing And Incentives Only Go So Far Link

Apps need marketing — and sometimes incentives — to get noticed and downloaded. However, that alone does not guarantee continued usage. The reservation system45 that the developers of Mailbox followed when they launched earlier this year, to stagger the app’s rollout, added to the hype for the app. Like many others46, I haven’t used Mailbox since I downloaded it to try it out.

Mailbox's reservation system added to the hype

An incentive will get users to download and try an app, but engagement will not last long47. The preceding lessons should help you create a good first impression, but users will often need to be nudged to continue using the app. This could take the form of reminders to use the app, as 1 Second Everyday does, or subtle email messages, if users have given you their email address and permission to contact them.

Lesson 10: What The App Store Gives, Apple Can Take Away Link

With each iOS release, third-party apps become redundant as their primary functionality in integrated into the new OS. iOS 7 suddenly made flashlight apps and bubble-level apps redundant. Still, some third-party apps have survived and thrived by offering additional unique functionality or a better experience. Examples include Instapaper and Pocket (formerly Read It Later), both of which were supposed to be killed by Safari’s Reading List in iOS 5 but are still alive and actively used today, two iOS releases later.

What’s A Developer To Do? Link

The lessons above are just a few of the reasons why an app may be downloaded by many but actively used by few. The Compuware study mentioned earlier found that 79% of consumers would retry a mobile app only once or twice if it failed to work the first time, and only 16% would give it more than two attempts. This gives app developers a small window of opportunity to make a good impression. So, put your best foot forward, and make sure your app is ready for prime time before launching. As shown below, abandonment is perhaps the least damaging response to a poor app experience.

User reaction to poor mobile app experiences
48Mobile Apps: What Consumers Really Need and Want4924,” Compuware (PDF, 2 MB). (Large view50)

If you already have an app struggling in the App Store, make sure to monitor social-media feedback, support emails, reviews on third-party websites, and App Store reviews and ratings to glean the reasons for the abandonment of your app. Services such as App Annie51 and App Figures52 will consolidate your reviews, which are a great source to learn about problems as well as suggestions for features. Prioritize and address these problems in your next release, and improve the app’s quality after launch53 to reduce the chance of your app joining users’ graveyard.

What other lessons have you learned from your own app graveyard? We would love for you to share them in the comments below.

(al, ea)

Footnotes Link

  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
  7. 7
  8. 8
  9. 9
  10. 10
  11. 11
  12. 12
  13. 13
  14. 14
  15. 15
  16. 16
  17. 17
  18. 18
  19. 19
  20. 20
  21. 21
  22. 22
  23. 23
  24. 24
  25. 25
  26. 26
  27. 27
  28. 28
  29. 29
  30. 30
  31. 31
  32. 32
  33. 33
  34. 34
  35. 35
  36. 36
  37. 37
  38. 38
  39. 39
  40. 40
  41. 41
  42. 42
  43. 43
  44. 44
  45. 45
  46. 46
  47. 47
  48. 48
  49. 49
  50. 50
  51. 51
  52. 52
  53. 53

↑ Back to top Tweet itShare on Facebook

Lyndon Cerejo is a certified user experience strategist in Capgemini's Rapid Design & Visualization practice, with a successful track record with clients including Allstate, American Express, Coca-Cola, General Motors, Merrill Lynch, and Wal-Mart. His key areas of expertise are user experience analysis, information architecture, rapid prototyping, usability testing, online strategy & marketing. He is the co-author of - a book about marketing adaptations on the Internet.

  1. 1

    Now you know How to Promote an App :)

  2. 3

    Regarding Lesson 5 (Privacy): Unfortunately you have to request several rights (e.g. details about the user, location, etc.) if you want to embed ads into your app :-( I did not find any advert provider which only uses the data connection. Of course I know why they want these information, but only as a developer. Previously I did not install some of the apps because why does a torch light app need to know where I am? That’s annoying, and that’s why I don’t have ads in my free application, so I’d really like to see an adprovider just providing the ad without user details (even though you would earn less than with other adproviders).

  3. 4

    Not sure if this article is only about iOS but as a Android user, what annoys me the most is developers who don’t allow their application to be stored on the external SD card. Kind of related to #6 though.

  4. 5

    Please stop using the word “responsive” for adaptive design concepts. Responsive is the time delay between user action and the response of the device. If the delay is too much the application is deemed unresponsive. Design that scales to different devices and screen sizes is called adaptive.

    • 6

      Daniel Schwarz

      December 2, 2013 2:42 am

      Unfortunately, the term “responsive” has become too widespread now. You are right, though.

    • 7

      Jason McGovern

      December 2, 2013 5:39 am

      There’s a distinction between responsive web design as Ethan Marcotte defined it and what adaptive design is. Adaptive is a subset of responsive in terms of design.

    • 9

      I think you’ll find that term responsive is more commonly used to refer to design concepts. I suppose you could argue that a responsive web page is any page that responds to a users action, but why would you need to define this sort of behavior? Adaptive and responsive web design concepts are much more than device scaling.

    • 10

      Lol what a ridiculous comment. Surely you knew before you posted it that “responsive web design (RWD)” has already caught on on a mass scale and is now the accepted term for “responsive websites”. Lol. But its cool, stay on your tirade, I’m sure you’ll get us all to quit calling it responsive.

      • 11

        Well … it is too late it seems, to evolve into thinking beings, to criticize our methods and adapt to situations. Let’s ride the wave of responsive web design. Hooray! Long live RWD!

      • 12

        Exactly, let’s change now the wordwide accepted term RWD! lol

  5. 14

    Can you reccommend some third-party apps that seem to get everything right? OR which apps do you find yourself using most often?

    • 15

      Lyndon Cerejo

      December 2, 2013 7:34 pm

      Jarod – that’s a great topic for another article, but here are third-party (non-native) apps that I find myself using regularly:

      For work
      – HoursTracker (track time spent on projects)
      – ownCloud (dropbox equivalent)

      Loyalty & retail
      – CardStar (manage loyalty cards)
      – Starbucks (payment convenience, loyalty, and offers in one)
      – Price Check by Amazon (also doubles as a Santa-wish-list for kids)

      – United Airlines (primary airline. As the article was going through the editorial process, United made significant enhancements to the app, making it much more useful!)
      – TripIt (travel itineraries and shared trips)

      Life & hobby
      – Walk Tracker Pro (note to self: start use it more frequently)
      – Flipboard (customized news mag)
      – Lapse It Pro (photography)

      – WhatsApp Messenger (cross device messaging)
      – Facebook
      – LinkedIn

  6. 16

    Mailbox app is pretty great, what didn’t you like about it?

    • 17

      Lyndon Cerejo

      December 2, 2013 7:42 pm

      Mazurka, the biggest shortcoming of the Mailbox app for me was that is only supported Gmail, so I could not get a consolidated view of all my email accounts. I’ll try it again when I can centrally manage all my email accounts.

  7. 18

    I actually appreciated the Mailbox reservation system and still use the app every day.

    It gave me confidence that the developers knew what they were doing and that they care about the user experience (and more importantly, about a good email system).

    If they didn’t choose this system and their servers wouldn’t be able to keep up with the demand, I would’ve ditched it right away and never looked back. Building trust is very very important, especially when dealing with something as sensitive as Email. So I think they handled it perfectly well.

  8. 19

    Thanks for sharing. Great article.

  9. 20

    Lyndon. Agree ! App user experience is KEY to app adoption. Sometimes, an app is revived because the company decides to go back and make some changes, based on real life testing and feedback.

    Like the latest update to the LinkedIn app. Its just so much easier to navigate within the app and visually is more appealing too. Was this the version you were referring to in the previous comment?

  10. 21

    srinivasa dasari

    December 4, 2013 5:08 am

    Thanks for sharing Lyndon, Great article.

  11. 22

    Marcin Raczkowski

    December 5, 2013 10:25 am

    If paid up made me rate it to unlock features the’d get a review that they surelly didn’t count on. I understand free app doing this, but after I’ve paid for it they can ask for it, but not lock me out of features to get it.

  12. 23

    Finally, somebody points out that forcing users to register makes them abandon the app!
    The best are the apps that give you the possibility to “register later” and then pop up the registration screen every time you open the app. Even better when you can’t delete the app, because it is included with the “system”.


↑ Back to top