--- title: The Return to Simplicity Why Less Is Trending More description: Why are digital products getting harder to use? This article explores the case for simplicity, what brands get right, and how to avoid the common mistakes. image: https://weareaffective.com/hubfs/learning-centre-images/the-return-to-simplicity-why-less-is-trending-more.webp --- [Skip to content](https://weareaffective.com/learning-centre/the-return-to-simplicity-why-less-is-trending-more#main-content) [![we\_are\_affective\_logo\_200](https://weareaffective.com/hs-fs/hubfs/we_are_affective_logo_200.png?width=175&height=48&name=we_are_affective_logo_200.png "we_are_affective_logo_200")](https://weareaffective.com) - [Home](https://weareaffective.com) - About Us - [Our Story](https://weareaffective.com/about) - [How We Work](https://weareaffective.com/how-we-work) - Our Services - [App Planning & Strategy](https://weareaffective.com/app-planning-strategy) - [App Design](https://weareaffective.com/app-design-agency) - [App UX Design](https://weareaffective.com/app-ux-design) - [App UI Design](https://weareaffective.com/app-ui-design) - [App Technical Architecture](https://weareaffective.com/app-architecture) - [Existing App Audits](https://weareaffective.com/app-audit) - [Case Studies](https://weareaffective.com/case-studies) - [Pricing](https://weareaffective.com/pricing) - [Learning Centre](https://weareaffective.com/learning-centre) - [Get Started](https://weareaffective.com/get-started) Expert Guide Series # The Return to Simplicity Why Less Is Trending More Table of Contents Somewhere along the way, digital products stopped feeling like tools and started feeling like obligations. Open a travel booking app and you're met with loyalty tier prompts, destination inspiration feeds, price alerts, and a personalisation quiz before you've had a chance to search for flights. Open a food delivery service and it pushes notifications about rewards, referral bonuses, and limited-time offers before you've decided what you want for dinner. The product is technically doing more, but the experience of using it has quietly become harder work. > A growing number of users are walking away from complexity, choosing products that ask less of them upfront. This is not accidental. Over the past decade, product teams have added features to solve problems, retain users, and chase engagement. Each addition made individual sense. Together, they created something exhausting. And users, it turns out, have noticed. The appetite for simplicity is about [cognitive and emotional load](https://weareaffective.com/user-psychology-app-design), about what a product asks of you before it gives you anything back. What we find, working across products in health, property, fitness, and sport, is that the products doing best right now are the ones that have made a deliberate decision about what not to show, and when not to show it. That decision is harder than it looks, and most products get it wrong in one direction or another. ## The Complexity Creep That Got Us Here Product complexity rarely arrives all at once. A feature gets added for a good reason, then another, then another, until the product is carrying the weight of every decision ever made inside a business. This is complexity creep, and it is almost universal in digital products that have been running for more than a couple of years. The logic that drives it is reasonable on the surface. A team identifies that users are churning at a particular point, so they add guidance. Another team sees an opportunity to cross-sell, so they add a prompt. A third team wants to collect data, so they add a questionnaire. Nobody is making a bad decision in isolation. But nobody is accounting for the cumulative weight of all those decisions landing on the same user at the same time. The result is products that present everything at once because every team believes their piece is the priority. There is no single moment of failure, which is partly why it is so hard to fix. The product director looking at the analytics sees decent headline numbers. What they do not see is the user who opened the app three times, felt vaguely overwhelmed each time, and quietly stopped coming back. According to [Think with Google](https://business.google.com/in/think/future-of-marketing/mobile-app-marketing-strategy-best-practices/), 21% of users will give up on an app if they do not understand it quickly. That is not a patience problem. That is a design problem that compounds over time. ## Why Users Are Pushing Back The pushback against complexity is not a new preference, but it is getting louder. Users have more choices than ever, and switching costs are low. If one property search app exhausts you with filters and prompts, another one is a download away. The tolerance for friction has dropped, and products that once survived on the strength of their feature set now need to survive on the quality of the experience. What this means in practice is that users are gravitating toward products that feel like they are on their side. A product that asks you to complete a seven-step setup before showing you anything useful is signalling that its own operational needs come before yours. A product that gets out of the way and lets you do the thing you came to do is signalling the opposite. That signal matters, particularly in the first thirty seconds of a new user's experience, which is where [most abandonment happens](https://weareaffective.com/learning-centre/what-curiosity-looks-like-in-a-first-session-and-why-most-products-design-past-i). The emotional dimension of this is real. When a product asks too much too soon, it creates a particular kind of [low-level anxiety](https://weareaffective.com/learning-centre/how-to-read-a-user-session-recording-for-emotional-signal-rather-than-task-compl), the feeling that you are behind, that you are doing it wrong, that this is going to be more complicated than you hoped. That anxiety does not need to be dramatic to be effective at driving users away. It just needs to be present. ## UX/UI design built around *real* psychology We design app interfaces around how people actually think and behave. User research, psychology-driven UX/UI design and technical specs delivered as one complete package. [See how we work](https://weareaffective.com/how-we-work) [Get started](https://weareaffective.com/get-started) No commitment ## The Cost of Asking Too Much: Cognitive and Emotional Overload The clearest illustration of this problem is a piece of work we did for a BMW fleet vehicle product. The app was designed to help drivers record damage and file reports after an accident. The problem the client brought to us was straightforward: users were not completing the process properly. Forms were left half-finished, photo uploads were missing, reports were going in without the information needed to process them. The interface was technically simple. It said "upload your photos" and provided a form. The problem was that it expected users to know which angles to photograph, what detail to capture, and how to fill in a structured damage report, all while standing at the side of a road having just had an accident. The cognitive demands of the task were normal. The emotional state of the user was not. > Asking a stressed user for precise, structured input is not a design problem you solve with better copy. What the product needed was a redesign of what it asked for and when. Reduce the immediate demands to what was genuinely necessary in that moment. Defer anything that could wait until the user was calm, seated, and at home. The interface was structured around the product's reporting logic, not around the human being using it under duress. That mismatch is where the failures were coming from. When a [user is overwhelmed](https://weareaffective.com/learning-centre/why-most-business-apps-fail-and-how-your-digital-business-can-avoid-the-same-fat), even tasks that seem straightforward in normal circumstances become barriers they will avoid rather than push through. ## Simplicity as a Trust Signal: What Headspace Got Right Headspace is worth examining because it understood something that most health and wellness apps still get wrong. The opening screen removes the two things that most reliably break trust in that category: a sign-up gate and a diagnostic questionnaire. There is no "how are you feeling today?" prompt. There is no onboarding flow that asks about your mental health history before you have decided whether you trust the product. By asking nothing upfront, Headspace communicates that it is not extracting from you before it has given you anything. That absence of demand is itself a message. The app [earns credibility by not overstepping](https://weareaffective.com/learning-centre/what-makes-users-trust-a-product-enough-to-enter-their-card-details) the relationship it has with a user who has known it for approximately four seconds. The design detail that makes this work is that the interface does the emotional work, not the copy. The breathing animation on the opening screen is slowing users down before they have read a single word. The product is producing a calmer emotional state through how it functions, not through promises about what it will do. That is the difference between a product that tells you it is calming and one that actually is. Most wellness apps fall into the first category. Before your next round of user testing, ask each participant to describe how they feel during the session, not what they think of the design. Frustration and confusion tend to appear in the emotional report before they appear in the task data. ## The Difference Between Simple and Stripped Down Simplicity is frequently misunderstood as reduction. Remove enough things and you have a simple product. That is not quite right, and acting on it tends to create a different kind of problem. There is a real danger that products oversimplify to the point where they hide information that users actually need. The goal is not to show less for its own sake. The goal is to show the right thing at the right moment. Those are very different design problems. One asks "what can we cut?" and the other asks "what does this user need right now, given what they know and how they feel?" The answer to the second question changes across the user journey. A new user needs different things from a user three months in. A user who has just completed their first task is in a different receptive state from one who is still figuring out the basics. Layering information across those states, so that complexity arrives only when the user is ready to receive it, is what distinguishes genuine simplicity from a stripped-down product that leaves users without what they need. The practical test is whether removing something costs the user anything. If it does, you have not simplified, you have degraded. If it costs them nothing, you were carrying unnecessary weight. Map your product's information against two axes: how often users need it, and how ready they are to receive it when they first arrive. Anything that scores low on both should come later, not earlier. ## Timing Information to the User's State, Not the Product's Logic We built a concierge app for residents moving into a new block of flats. The residents were typically high-net-worth individuals, and the expectation was that they would want comprehensive information available immediately. Most building management apps default to exactly that: a full directory of the building, emergency procedures, recycling points, local area guides, all surfaced at once. We did the opposite. We recognised that the emotional state of someone who has just moved is highly variable and often overwhelming. Some residents had just bought their first property. Others had moved following a separation. The common thread was that none of them were in a mental state that was receptive to large volumes of information, regardless of how well organised it was. So we drip-fed notifications over time, matching content to when users would actually need it. Recycling information went out a couple of days after move-in. Local area recommendations arrived over the first weekend. Emergency procedures were surfaced early but not buried under everything else. The experience felt human rather than transactional, because it was timed to the user's state rather than the product's internal logic about what a complete onboarding looks like. This is the practical difference between [information architecture and emotional design](https://weareaffective.com/user-psychology-app-design). The information was the same in both versions. What changed was the sequencing, and the sequencing changed everything about how it felt to receive it. ## When Simplification Fails: The Football App Problem We worked on a grassroots football app where the client arrived with a clear conviction: the booking process needed to be more intuitive. They had mapped their individual features against best-in-class single-purpose competitors and found their product wanting on each comparison. We pushed back on the framing, but ultimately made the changes they were asking for. The changes made little to no difference to the metrics they cared about. The real problem was not the booking flow. The problem was that the [product was trying to do too many things](https://weareaffective.com/learning-centre/5-things-that-make-the-difference-between-so-so-apps-and-stellar-apps-what-your-) in one place. There was a reason those features existed across several separate apps in the market. Each of those apps had been built around a single purpose, with an interface tuned to that purpose and nothing else. Combining them into one product meant that no single flow could be optimised for its specific user state, because every screen was also carrying the weight of everything else the product wanted to be. Despite genuine efforts to create something cohesive and emotionally grounded, the result was overly complex and too verbose for the audience and its core purpose. The booking process was fine. The product around it was the issue. When someone says a product is not intuitive, they are almost never pointing at a single screen. They are describing a feeling that has built up across the whole experience of using it. ## Context Determines What Simple Actually Means The word "intuitive" gets used as though it describes an objective property of an interface. It does not. What [feels intuitive to a radiographer](https://weareaffective.com/learning-centre/why-do-some-apps-feel-like-they-were-made-just-for-you) reading a medical imaging platform would feel incomprehensible to a first-time user of a consumer health app. What feels appropriately guided and supportive to a novice user feels patronising and slow to an expert. The criteria shift entirely based on who is using the product and what they are trying to accomplish. This matters because simplification strategies cannot be universal. For expert users in high-stakes, time-sensitive environments, stripping away guidance is often the right move. Every extra step between the user and the action they need to take is a cost. For users who are new to a category, or operating in a lower-stakes context with more time, guidance and education are what prevent confusion, anxiety, and abandonment. | User type | Context | What simple means | | --- | --- | --- | | Expert user | High-stakes, time-sensitive | Remove guidance, surface the action directly | | Novice user | Lower-stakes, exploratory | Layer guidance, educate before asking for input | | Stressed user | Emotionally overwhelmed | Reduce demands, defer non-essential requests | | Returning user | Familiar with core flow | Surface advanced features, reduce repetition | The design question is not "how do we make this simpler?" but "simpler for whom, and in what state?" Getting that wrong in either direction produces a product that fails its users, either by overwhelming them or by underestimating them. ## What Businesses Get Wrong When They Try to Simplify The most common mistake we see when a product team decides to simplify is that they start cutting without first understanding why users are struggling. They remove features, reduce copy, and tighten the visual design. Sometimes this helps. Often it does not, because the complexity was not in the individual elements but in the relationship between them. A fitness app we worked on had an early abandonment problem during its orientation flow. The team's instinct was to cut questions. Our recommendation was different: keep the questions, but tell users at the start how long the process would take. That single framing change, telling people [what to expect before they began](https://weareaffective.com/learning-centre/what-a-development-team-actually-needs-to-know-about-the-user-before-sprint-one), changed how users entered the flow. They came in prepared rather than uncertain. The drop-off rate fell significantly. The fix was not fewer questions but a clearer contract with the user about what was being asked of them. Before removing anything from an onboarding flow, test what happens when you add a time estimate at the start. Framing the commitment often reduces abandonment more effectively than reducing the number of steps. The second mistake is treating simplification as a one-time project rather than an ongoing design question. A product that is appropriately simple for its users in year one will accumulate complexity again by year three, because teams keep adding things. The question of what to surface, when, and for whom needs to be revisited as the product and its user base evolve. - Start with user emotional state, not feature lists, when auditing what to cut - Test framing and sequencing before removing content - Distinguish between complexity that burdens users and complexity that serves them - Revisit simplification decisions as the product matures ## Conclusion The return to simplicity is a response to a decade of products that prioritised feature completeness over the experience of using them. Users have become better at recognising products that are built around their needs versus products that ask them to serve the product's needs, and they are choosing accordingly. The work of simplification is harder than it appears because the answer is never just "show less." It is about understanding what a user needs at each point in their journey, what emotional state they are in, and what that state means for what the product should and should not be asking of them. That requires a different kind of design thinking, one that treats timing and sequencing as core decisions rather than finishing touches. What the BMW fleet app, the concierge product, and the football app all have in common is that their complexity problems were not primarily visual or structural. They were emotional. The products were misaligned with the state of the people using them. Getting that alignment right is what produces the kind of simplicity users actually respond to, not fewer features, but better judgement about when to use each one. If your product is losing users at points you cannot fully explain, or if your team is debating what to cut without being sure they are cutting the right things, [let's talk about your product experience](https://weareaffective.com/get-started). ## Frequently Asked Questions What is complexity creep and how does it affect digital products? Complexity creep is the gradual accumulation of features that each made sense individually but together create an overwhelming experience for users. It happens when different teams add prompts, guidance, and questionnaires without accounting for the combined weight of all those additions landing on the same user at once. Why are users increasingly abandoning feature-heavy apps? Users now have more choices than ever, and switching between apps is quick and easy, so tolerance for friction has dropped significantly. According to Think with Google, 21% of users will give up on an app if they do not understand it quickly, which points to a design problem rather than a problem with user patience. What does the trend towards simplicity actually mean for product design? It means making deliberate decisions about what not to show users, and when not to show it. The products performing best right now are those that get out of the way and let users complete the task they came to do, rather than front-loading them with prompts and personalisation quizzes. How does cognitive and emotional load relate to product simplicity? Cognitive and emotional load refers to the effort a product demands from a user before giving anything back in return. When a product asks too much upfront, whether through setup steps, notifications, or loyalty prompts, it signals that its own operational needs come before the needs of the user. Why is complexity creep so difficult to identify and fix from within a product team? Because there is no single moment of failure, headline analytics can appear healthy even while users are quietly disengaging. The user who opened an app three times, felt vaguely overwhelmed, and stopped returning will not show up clearly in the data that product directors typically review. Which types of products are most affected by this shift towards simplicity? The trend is visible across a wide range of digital products including travel booking apps, food delivery services, property search tools, health apps, and fitness platforms. Essentially, any product that has been running for more than a couple of years is likely carrying the accumulated weight of many past decisions. What signal does a complicated onboarding process send to new users? A lengthy or complicated setup process signals to users that the product's own operational needs take priority over theirs. Products that allow users to complete their intended task quickly and without unnecessary steps send the opposite signal, which builds trust from the very first interaction. Is the preference for simpler products a new trend? The preference for simplicity is not new, but it is becoming louder and more consequential as competition between digital products increases. Because switching costs are low, users no longer need to tolerate friction, and products that once relied on a broad feature set now need to compete on the quality of the overall experience. ## Related Articles [![We Are Affective](https://weareaffective.com/hubfs/we_are_affective_logo_mark.svg)](https://weareaffective.com) 20-22 Wenlock Road London, N1 7GU United Kingdom +44 20 4572 8062 [hello@weareaffective.com](mailto:hello@weareaffective.com) Services [App planning & strategy](https://weareaffective.com/app-planning-strategy) [App design](https://weareaffective.com/app-design-agency) [App UX design](https://weareaffective.com/app-ux-design) [App UI design](https://weareaffective.com/app-ui-design) [App technical architecture](https://weareaffective.com/app-architecture) [Existing app audits](https://weareaffective.com/app-audit) Legal [Privacy policy](https://app.termly.io/policy-viewer/policy.html?policyUUID=b8fa9921-7518-4fb5-8ddd-9dc7f5977ed2) [Terms](https://app.termly.io/policy-viewer/policy.html?policyUUID=8b6a6ad5-91bd-4176-a5f7-6d36b0398f70) Case studies [TravAI](https://weareaffective.com/case-studies/travai) [Meditech](https://weareaffective.com/case-studies/harley) [WorkingWeight](https://weareaffective.com/case-studies/workingweight) [SkinSync](https://weareaffective.com/case-studies/skinsync) [Three Lochs](https://weareaffective.com/case-studies/three-lochs) [Drift](https://weareaffective.com/case-studies/drift) About us [Our Story](https://weareaffective.com/about) [How We Work](https://weareaffective.com/how-we-work) Guides [Creating an app](https://weareaffective.com/how-to-create-an-app) [Building an MVP](https://weareaffective.com/building-an-mvp) [Cost and budgeting](https://weareaffective.com/app-development-cost) [App technology](https://weareaffective.com/app-development) [Planning and strategy](https://weareaffective.com/app-planning-strategy) [User research](https://weareaffective.com/app-user-research) [Onboarding design](https://weareaffective.com/app-onboarding-design) [User psychology](https://weareaffective.com/user-psychology-app-design) [Launch and growth](https://weareaffective.com/app-launch-growth) Copyright © 2026, weareaffective.com. All rights reserved.