As devices have become more powerful and grown to encompass more facets of our lives, apps have proliferated in both quantity and complexity, and it may be time to reconsider whether apps should be this way.
More often than not, apps wind up being more complex than they really should be and create significant user experience overhead as users try to solve their needs. This growing overhead has three root causes:
- Medium - apps are fullscreen experiences with access to the device's full capabilities, which suggests to developers to expand into those broad constraints, and they are launched from the springboard which adds to a base level of UI overhead.
- Marketplace - the App Store's compensation model (one-time, sub, IAP) and prerequisites (branding and shelf display) suggest developers create products that compete in ways that grow them into businesses, not just tools.
- Momentum - apps are central to the knowledge reservoir that exists among device users; they understand and use apps to solve problems, which creates expectation and demand for companies to use the medium of apps to interface with their customers.
The Medium of Apps
Apps as a medium encompass many different needs from the very small to downright massive. Some needs require complex interfaces, others don't really require interfaces at all. Some are single-purpose, others very multi-purpose. It's also worth reminding ourselves that not all apps solve needs, and not all needs are solved (or solved well) by apps as a medium.
Using apps right now incurs a fixed cost of overhead that is worth questioning. Users must:
- Make the connection that the need they have may be solved by an app they have (if not, go to the App Store)
- Remember the app icon or name
- Find the app either spatially on the springboard or via search
- Launch the app
- Navigate to find the part of the UI where the app does the thing they want from it
- Look at or use the thing, hopefully remembering how to
- Usually then navigate to another app to do a related thing
Meanwhile, apps litter the springboard and app switcher UIs, and with each app the overall device experience worsens just a little bit as all apps become harder to find and navigate between.
The App Store Drives Apps to Become Businesses
In addition to the fixed costs of the medium, the conditions for feature creep come from the increasingly direct coupling of app <-> business, which act as a variable cost of complexity depending on the market the app is in. The competitive business environment of the App Store creates strong business incentives to:
- Add duplicative capabilities to solve for minimum work complexity, so you don't have to navigate to other apps as much to do the thing
- Create eye-catching app branding so you can more easily find it next time among a sea of other apps on the springboard
- Add ways to bookmark, tag, or otherwise organize data in app
- Add user accounts with required logins to own user relationship
- Offer in-app upsells
- Add permissions prompts for capabilities you don't want
- Announce changes to app in pop-ups
- Send notifications to re-engage and stay top of mind with users
- Create non-standard UI to differentiate app from others, making it harder to navigate
- Update the app frequently so when you go back to it, it's changed
As app developers add more of these features, their financial costs rise and the app may switch to a subscription model to keep it afloat.
To get a little silly, imagine a wrench you bought was also a brand you had to interact with to use, had its own Instagram account talking about what bolts it turned today, and required a subscription to turn more than 10 bolts a month. That honestly feels like the state of many apps today.
I'm reminded of music albums that only had one or two good songs and 10 tracks of filler, or books that had a few good points among chapters and chapters of blah blah blah. These have to expand themselves to a size necessary to be sold in the markets they're in. Apps are no different.
Where To Go Next With Apps
Right now, apps are the only way to solve user needs on mobile devices , and both the grain size feels too large, and the user experience holding it all together is starting to show its limits. There are many apps that would better meet user needs if they were unbundled into some different modalities:
- Widgets and UI cards that only popped up in the appropriate context
- Content libraries outside springboard (e.g. games)
- Overlays on a map or camera view
- Services available to query, likely via voice interface
- Automations or 'butler' bots that would do certain things for you automatically
Of course, any system is more than the sum of its parts. These would need to be weaved in elegantly into the overall user experience of the operating system, which likely would involve a near complete overhaul of things like springboard. And there's a strong user education component to introducing these new concepts. It will take years to build up the knowledge reservoir across hundreds of millions of device users, so any changes to apps must be introduced incrementally.
In closing, I think there's a lot of opportunity to create the tooling and user experience context to allow developers to unbundle apps, and so avoid some of the trappings of the current trend of app feature creep. It's a big undertaking, but this feels like where the puck is going.
I'm not anti-subscription; in fact, I think it's often the best way to align user need and business need over time. My critique is that a lot of this is an unnecessary artifact of the business environment and primacy of apps on mobile devices. Most user needs are not worthy of this level of complexity. ↩︎
Aside from voice assistants, which are getting smarter about connecting to services and meeting some needs. Unfortunately their capabilities are largely unknown and invisible to users right now. Hopefully that will change! ↩︎