<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by The Distance on Medium]]></title>
        <description><![CDATA[Stories by The Distance on Medium]]></description>
        <link>https://medium.com/@TheDistance?source=rss-733ae949c85b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Rfl_uZFNa9bKjW8rFK0bZw.png</url>
            <title>Stories by The Distance on Medium</title>
            <link>https://medium.com/@TheDistance?source=rss-733ae949c85b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:14:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@TheDistance/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Your next user might never search for your app]]></title>
            <link>https://medium.com/@TheDistance/your-next-user-might-never-search-for-your-app-0c15278244cc?source=rss-733ae949c85b------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c15278244cc</guid>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[app-store]]></category>
            <dc:creator><![CDATA[The Distance]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 11:58:19 GMT</pubDate>
            <atom:updated>2026-11-04T11:58:19.352Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Picture a Friday afternoon. You’re wrapping up for the week and you remember you promised to sort dinner for the family. You don’t unlock your phone, scroll to the food delivery app you always use, find last week’s order and tap through the checkout. You just ask your phone to reorder the usual from the curry house down the road, and a minute later it tells you the order is on its way.</strong></p><p>Somewhere in that exchange, a decision was made about which app got the job. You didn’t make it, at least not consciously. The assistant did, based on what you asked for, what you have installed and what each of those apps has told the operating system it’s able to do. That small moment is the reason we wanted to write this piece, because it changes something that product owners have taken for granted for well over a decade.</p><p>We’ve written before about how the App Store isn’t the only way people will find your app, looking at the different routes people take to discover something new. This post picks up where that one left off. We want to talk about what happens when people stop searching for apps at all and start asking for outcomes instead, and what it means for you if you own an app, or you’re planning to build one.</p><p>We’ll walk through what has actually changed this year, what’s still informed guesswork, and the practical things you can start thinking about now so your app is the one an assistant reaches for.</p><h3>How people find apps today</h3><p>For most of the life of the smartphone, finding an app has started with a search. You know roughly what you want, you open the App Store or Google Play, you type a few words and you pick from the results. Apple’s own figures show just how central that habit is. According to Apple Ads, <a href="https://ads.apple.com/app-store">70% of App Store visitors use search to discover apps, and almost 65% of downloads happen directly after a search</a> (that’s based on Apple’s 2022 data).</p><p>That behaviour has shaped an entire discipline. App store optimisation exists because the person doing the searching is also the person doing the choosing. You give them the right keywords so they find you, the right screenshots so they understand you, and enough good reviews that they trust you more than the app sitting just below yours in the results. Everything about the model assumes a human is scanning a list and making a judgement.</p><p>It’s worth pausing on that assumption, because it’s the part that’s starting to give way. When someone asks an assistant to get something done, there’s no list to scan. The assistant does the scanning on their behalf, and it’s looking for very different signals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*Pb1fdriBoAmoq4YY" /></figure><h3>What’s actually changed this year</h3><p>It would be easy to treat all of this as a distant prediction, but 2026 has been the year the three biggest assistant platforms moved from talking about it to shipping it. It’s worth looking at each one, because they’re arriving at the same place from slightly different directions.</p><h3>Apple: a smarter Siri built on Gemini</h3><p>In January, Apple and Google announced a multi-year collaboration under which <a href="https://blog.google/company-news/inside-google/company-announcements/joint-statement-google-apple/">the next generation of Apple Foundation Models will be based on Google’s Gemini models and cloud technology</a>, helping to power future Apple Intelligence features including a more personalised Siri. Apple then used WWDC in June to show what that Siri looks like, including deeper links into the apps on your phone.</p><p>The piece that matters most for app owners is a framework called <a href="https://developer.apple.com/documentation/appintents">App Intents</a>. App Intents is the way an iOS app tells the system what it can do, such as “start a workout”, “book a table” or “show my latest invoice”, in a structured form that Siri, Spotlight, Shortcuts and widgets can all understand and call. It isn’t new, as it’s been around since iOS 16, but its role has grown considerably. Coverage of WWDC26 reported that <a href="https://bitrise.io/blog/post/wwdc26-under-the-radar">Apple formally deprecated SiriKit, leaving App Intents as the framework Siri uses to call into third-party apps</a>, with a window of a couple of years before older SiriKit-based features stop working.</p><p>In practical terms, if your iOS app doesn’t describe its key actions through App Intents, the new Siri has very little to work with when someone asks for something your app could have helped with.</p><h3>Google: Gemini getting things done inside Android apps</h3><p>Google has been heading the same way on Android. In February, the Android team announced AppFunctions, which lets apps expose data and functionality directly to AI agents and assistants such as Gemini, so the assistant can find the right function and run it from a natural-language request. In the same announcement, Google described a separate UI automation framework that lets Gemini carry out multi-step tasks in installed apps, starting as a beta with a curated selection of food delivery, grocery and rideshare apps in the US and Korea.</p><p>The line from that announcement that we keep coming back to is from Matthew McCullough, VP of Product Management for Android Development, who wrote that success is shifting from getting users to open your app, to successfully fulfilling their tasks and helping them get more done faster. That’s Google telling app makers, fairly directly, that the measure of a good app is changing.</p><p>Google has also been clear about where the user stays in control. The same post explains that people can watch a task’s progress, take over manually at any point, and that Gemini is designed to alert users before completing sensitive tasks such as making a purchase. We’ll come back to why that matters for design.</p><h3>OpenAI: apps that live inside the conversation</h3><p>The third piece of the picture sits outside the phone’s operating system altogether. In October 2025, OpenAI introduced <a href="https://openai.com/index/introducing-apps-in-chatgpt/">apps in ChatGPT and the Apps SDK</a>, letting third-party services such as Booking.com, Spotify and Zillow run inside a chat, with their own interactive interface.</p><p>At the same launch, OpenAI said developers building with the SDK could reach over 800 million ChatGPT users, and Sam Altman told the DevDay audience that <a href="https://techcrunch.com/2025/10/06/sam-altman-says-chatgpt-has-hit-800m-weekly-active-users/">more than 800 million people now use ChatGPT every week</a>.</p><p>What’s interesting here is how OpenAI describes discovery. People can call an app by name, but ChatGPT can also suggest one when it’s relevant to the conversation, so someone talking about buying a home might be offered the Zillow app without ever asking for it.</p><p>OpenAI has since opened a directory where people can browse and add apps, but that “suggested at the right moment” behaviour is the part that feels genuinely different from a store. It’s worth noting that when apps first launched, they weren’t available to users in the UK, the European Economic Area or Switzerland, so if your audience is mainly in the UK it’s a channel to keep an eye on rather than rely on today.</p><h3>From searching to asking: how an assistant chooses an app</h3><p>This is the part where we have to be honest about what’s known and what isn’t. None of these companies publish the exact logic their assistants use to pick one app over another, and we’d be wary of anyone who claims to know it precisely. What we can do is look at how these systems are built and reason about the signals they’re likely to rely on.</p><p>The simplest way we’ve found to explain it is the difference between browsing a high street and asking a concierge. When you browse, you walk past the shop windows and decide for yourself which one looks right. When you ask a concierge, you say what you want, and they send you somewhere based on what they know about the options and about you. The shop with the most eye-catching window doesn’t automatically win. The one that clearly does what you asked, and that the concierge trusts to deliver, does.</p><p>An assistant is in that concierge role. When someone asks for something, it’s likely to be weighing up questions such as these:</p><ul><li><strong>Is there an app installed that can do this?</strong> For Siri and Gemini, apps already on the device are the natural starting point, so being installed and set up still matters a great deal.</li><li><strong>Has the app described an action that matches the request?</strong> An app that has clearly declared “reorder a previous purchase” is in a far better position than one that only exposes “open app”.</li><li><strong>Can the assistant collect what the action needs?</strong> If an action needs a date, a location and a number of people, the assistant has to be able to gather those from the request or ask for them.</li><li><strong>What has this person done before?</strong> Habits and previous choices are useful context, which is why the app someone already uses will often get the job.</li><li><strong>Is the user comfortable with it?</strong> Permissions, and whether the user has connected the app, decide whether the assistant can act at all.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*vUfNbjM11NhYb4fl" /></figure><h3>Your app’s capabilities are now part of its shop window</h3><p>For years, the shop window for an app has been its store listing. In an intent-led world, a growing share of that window is made up of the actions you expose to the operating system and to assistants. That shifts some decisions that used to sit purely with developers into the hands of product owners, because they’re really decisions about what your product is for.</p><p>The first decision is which jobs a person could reasonably hand over to an assistant. This is rarely every feature. In our experience, most apps have two or three tasks that account for the bulk of what people come to do, such as checking a balance, booking a slot, reordering something, logging an activity or finding a document. Those are the actions worth describing really well first, because they’re the ones people are most likely to ask for in their own words.</p><p>The second is how each action is named and described. This is where it starts to feel a lot like writing store copy, except the first reader is a machine. A vague description makes it harder for the assistant to match a request to your app, while a precise one, written in the language your users would naturally use, makes it easier. It’s worth bringing the same care to this that you’d bring to a product page.</p><p>The third is what each action needs from the user and what it gives back. If someone asks to book a table, the assistant needs to know the restaurant, the time and the party size, and it needs to know what to do if one of those is missing. When the booking is made, your app needs to send back something the assistant can turn into a clear confirmation. Getting these inputs and results right is the difference between an assistant that completes the job and one that gives up halfway and sends the user into your app to finish it.</p><p>The last is trust. Every action you expose raises questions about what data the assistant can see and what it’s allowed to do without asking first. That’s partly a technical matter, but it’s also a product and brand decision, because the way your app behaves when someone isn’t looking at it says a lot about how much you respect the people using it.</p><h3>Designing for being invoked, not just opened</h3><p>One of the quieter consequences of all this is that some of your users will complete a task without ever seeing your interface. For anyone who has spent months refining a checkout flow or an onboarding journey, that can feel like a loss. We’d encourage you to see it a little differently, because it opens up a new set of design questions that are genuinely interesting to work through.</p><p>Think about how your brand comes across in a single line of confirmation. When Siri or Gemini tells someone their order is placed, what does that message say, and does it sound like you? It’s a very small surface, but for some people it will become the most frequent contact they have with your product, so the tone, the clarity and the detail all matter.</p><p>Then there’s the question of when to bring someone back into the app. Some tasks are perfectly suited to being handled in the background. Others involve a meaningful choice, a payment, or something personal enough that a person will want to see it properly before agreeing.</p><p>Google’s own approach, where Gemini checks with the user before sensitive actions like purchases, is a useful model here. Part of designing for assistants is deciding, deliberately, where those handover points sit, and making sure that when someone does land in your app, it picks up exactly where the assistant left off so they don’t have to start again.</p><p>Finally, it’s worth thinking about how you’ll measure success. If a growing number of tasks happen without anyone opening your app, then sessions, screen views and time in app will tell you less about how well you’re serving people. Completed tasks, repeat use of an action and the rate at which assistant-led tasks need a person to step in are likely to become far more useful numbers. That’s very much in line with Google’s point about success moving towards fulfilling tasks rather than getting people to open the app.</p><h3>Where to start</h3><p>You don’t need to rebuild your app to get ready for this. For most products, it’s a case of looking at what you already have through a slightly different lens and making some focused changes. If you’re wondering where to begin, this is roughly the order we’d suggest.</p><ul><li><strong>List your most important tasks.</strong> Write down the handful of things most of your users come to your app to do, ideally backed up by your analytics rather than gut feel.</li><li><strong>Check what you already expose.</strong> Many apps already have some Siri Shortcuts, App Intents or Android shortcuts in place, often added a few years ago and rarely revisited, so it’s worth knowing where you’re starting from.</li><li><strong>Map those tasks to each platform.</strong> Work out which tasks should become App Intents on iOS and AppFunctions on Android, and whether a ChatGPT app would make sense for your audience and your market.</li><li><strong>Write clear, specific action descriptions.</strong> Treat them with the same care as your store listing, using the words your users would actually say.</li><li><strong>Decide where a person must confirm.</strong> Anything involving money, personal information or sending something on someone’s behalf should have a clear checkpoint.</li><li><strong>Agree how you’ll measure it.</strong> Set up tracking for completed tasks and assistant-led use before you launch, so you can see whether the work is paying off.</li></ul><p>If you’re planning a new app rather than updating an existing one, the advantage is that you can build these actions in from the start. It’s much easier to design a product around clearly defined tasks from day one than to retrofit them later.</p><h3>How we approach this at The Distance</h3><p>We’ve been building apps since 2009, and if there’s one thing that experience has taught us, it’s that the way people use their phones changes faster than most product roadmaps do. Voice assistants, widgets, wearables and now AI assistants have each asked app owners to rethink where their product shows up and how people reach it. The apps that cope best are the ones built around a clear understanding of what people are actually trying to get done.</p><p>That’s why, when we work with a partner on a new app or a significant update, we spend a lot of time early on understanding the real tasks people come to the app for, the language they use to describe them and the moments where they need to be in control. That understanding has always shaped how we design screens and journeys. Increasingly, it also shapes which actions we expose to Siri, Gemini and other assistants, and how we describe them.</p><p>If we were sitting across the table from you today, our advice would be fairly simple. Don’t treat AI assistants as a separate channel to bolt on later. Treat them as another way people will reach the most important parts of your app, and make sure those parts are described clearly enough that an assistant can find them, understand them and use them well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*HtI61zwuDVTUPr2b" /></figure><h3>Frequently asked questions</h3><h3>Will AI assistants replace the App Store?</h3><p>Not any time soon. People still need to find, install and trust an app before Siri or Gemini can use it, and stores remain the main place that happens. What’s changing is how often people open an app once it’s installed, and how they first come across one, which is why it’s worth thinking about both.</p><h3>What is App Intents, and does my iOS app need it?</h3><p>App Intents is Apple’s framework for describing what your app can do so that Siri, Spotlight, Shortcuts and widgets can use those actions. With SiriKit being phased out, it’s the route Siri uses to work with third-party apps, so if you want your app to be useful to the new Siri, it’s well worth adopting for your key tasks.</p><h3>How does Gemini use third-party apps on Android?</h3><p>Google offers two routes. AppFunctions lets your app describe specific functions that Gemini can find and run, and a separate UI automation framework lets Gemini carry out tasks in some apps on the user’s behalf, starting with selected food delivery, grocery and rideshare apps.</p><h3>Do I need to rebuild my app to work with Siri or Gemini?</h3><p>Usually not. In most cases it’s about adding well-designed actions on top of the features you already have, then testing how they behave when an assistant calls them. The bigger work tends to be deciding which tasks to expose and how to describe them.</p><h3>How will I know if an assistant is using my app?</h3><p>You’ll need to plan for it in your analytics. Track when actions are triggered from outside the app, how often they complete without a person stepping in, and how often someone chooses to carry on in the app itself.</p><h3>Getting ready for the next way people find you</h3><p>The way people find and use apps is moving from what they search for to what they want done. Search and the app stores aren’t going anywhere, but alongside them, a growing share of decisions about which app gets used will be made by an assistant acting on someone’s behalf, and the apps that describe their capabilities clearly are the ones those assistants will reach for.</p><p>If you’d like to know how ready your app is for Siri, Gemini and the assistants that follow, we’d be happy to look through it with you and talk about where to start.</p><p><a href="https://thedistance.co.uk/contact-us">Talk to us about your app]</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c15278244cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[App or website: What’s best for your business?]]></title>
            <link>https://medium.com/@TheDistance/app-or-website-whats-best-for-your-business-6653b49fa1d6?source=rss-733ae949c85b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6653b49fa1d6</guid>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[The Distance]]></dc:creator>
            <pubDate>Tue, 03 Nov 2026 10:46:01 GMT</pubDate>
            <atom:updated>2026-11-03T10:46:01.652Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Updated October 2026: we’ve refreshed this guide to reflect how apps and websites have changed since we first wrote it in 2023.</em></p><p><strong>Sooner or later, most businesses ask the same question: do we need an app, or will our website do the job? In an ideal world you’d have both. In practice, budget, timelines and team size mean you have to decide what comes first. In this guide, we look at the questions that should shape that decision, how the answers have shifted since we first wrote about this in 2023, and where an app genuinely earns its place.</strong></p><h3>What’s the difference between an app and a website?</h3><p>An app (short for application) is software people download to their phone from the App Store or Google Play. It lives on their home screen, can keep working without a connection, and can use more of the phone’s hardware than a website can. When people say “app” today, they nearly always mean a mobile app, built for the small, touch-led screens we carry everywhere.</p><p>A website is a set of pages under one domain that anyone can open in a browser, on any device, with nothing to install. It’s usually the first place people find you, and it’s where you’ll publish essentials like your privacy policy, including the one your app will need.</p><p>Between the two sits the installable website, often called a progressive web app or PWA. It’s a website people can add to their home screen, where it opens in its own window and behaves a little more like an app. We’ll come back to what that can and can’t do later on, because it’s become a more realistic option than it was a few years ago.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*BIm3zEPzxfxx2yF3" /></figure><p>Whatever else you decide, your website needs to work well on every screen size. That approach is called responsive design, and it’s been the expected standard for years. If your site still struggles on a phone, fix that first, because it affects everything else in this article.</p><h3>How often will people use you?</h3><p>How often people need you is one of the biggest factors in this decision. If your business relies on people coming back regularly, an app makes a lot of sense. It sits on their home screen, one tap away, and that small saving in effort adds up over weeks and months.</p><p>Think about the apps you open without a second thought: maps, banking, travel, fitness. Uber, Strava and Google Maps all depend on people building them into a daily routine, and being on the home screen is a big part of how that habit forms.</p><p>Notification badges, the small counters on an app’s icon, play a similar role. They give people a reason to come back, as long as what’s waiting for them is worth the tap.</p><p>If people only need you now and then, to check opening times, book once a year or read up before buying, a good website will usually serve them better. It’s easier to find and there’s nothing to install. How often people visit isn’t the only factor, though.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*mTLEWbZ3HjdQ0JtS" /></figure><h3>How will people find you?</h3><p>Apps are more convenient once they’re installed, but they ask more of someone who’s only just heard of you. A first visit almost always starts with a search, a link, a social post or, more and more often, an answer from an AI assistant like ChatGPT or Gemini. All of those lead to a website. Very few people go looking in an app store for a brand they don’t know yet.</p><p>That’s why your website does the heavy lifting early on, and why your app needs a clear route in from it. We look at the different ways people discover apps in <a href="https://thedistance.co.uk/insights/the-app-store-isn&#39;t-the-only-way-people-will-find-your-app">The App Store isn’t the only way people will find your app</a>.</p><p>Once someone has installed your app, the picture flips. Content can load from the device rather than a server, people stay signed in, and you’re always within reach.</p><p>Put simply, your website wins before someone downloads your app, and your app wins after.</p><h3>Does your product need the phone’s hardware?</h3><p>Websites can do far more with a phone than they used to. Most can now use the camera, ask for your location and let you sign in with your face or fingerprint using passkeys. So the real question is how far beyond that your product needs to go.</p><p>Apps still have a clear edge when a product depends on the device itself. That includes connecting to other hardware over Bluetooth or NFC, tracking location in the background, working with health and fitness data, and showing live updates on the lock screen or a smartwatch. On iPhone, websites still can’t use Bluetooth, USB or NFC at all. Uber remains a good example: its whole service depends on precise, continuous location, which an app handles far better than a browser.</p><h3>Do people need it to work without signal?</h3><p>Websites have improved here too. A well-built installable website can save some content to the device and keep going through a patchy connection. Storage is tighter and less predictable than in an app, though, so it’s rarely something you’d want a business-critical product to rely on.</p><p>If your users work where signal drops out, such as engineers on site, staff in warehouses or passengers underground, offline support stops being a nice extra and becomes the point of the product. That’s where apps are still the dependable choice.</p><p>If working offline isn’t central to what your product does, don’t let it drive the decision on its own.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*6yetK5KYkRblqvQ7" /></figure><h3>How much control do you want over the experience?</h3><p>You’ve got big plans for a customer touchpoint that looks like nothing else on the market. It’s entirely unique and original. How do you realise this dream? By developing an app or creating a website?</p><p>Before we provide an answer, let’s acknowledge that there’s a reason websites and apps typically resemble one another. A standard format is easier to use. We intuitively understand where to look, what to click or tap, and how things work. But let’s go back to our entirely original (but definitely hypothetical) customer touchpoint. In this example, an app is the better option.</p><p>Generally, apps are more of a blank design canvas. Apps can be more free-form and are open to more creative design. Mobile websites exist within the restrictions of an internet browser. How you navigate a website is built into the browser (via the back and forward buttons, the search bar etc.) and experience conditions user behaviour. We tend to engage with browsers in the same way, following the same patterns and habits, no matter what website we visit.</p><p>Developers can design apps to reflect your particular aesthetic vision and to perform and function in a way that meets your business needs. Advanced touchscreen gestures allow for a more interactive experience and a wider “vocabulary” with which to engage users — you can swipe, drag, pinch and double tap your way around an app. It’s so much more expressive. On the other hand, your business model may not require that design freedom. If you’d like to see how the platforms themselves think about this, <a href="https://developer.apple.com/design/human-interface-guidelines">Apple’s Human Interface Guidelines</a> and <a href="https://m3.material.io/">Google’s Material Design</a> are both worth a read.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*c9Ndivk8y-AU9a1j" /></figure><h3>Is personalisation key to your model?</h3><p>In the modern business landscape, personalisation is increasingly important. It helps to tailor services to specific users, allows for bespoke product recommendations and enables you to deliver relevant content. Though both websites and mobile apps allow for personalisation, there are notable differences in how they do so.</p><p>Apps are far more open to customisation than websites. Users can dictate their preferences and set the app up to reflect the way they use it. <a href="https://thedistance.co.uk/insights/how-apps-drive-customer-engagement-effectively">Apps also track user engagement</a>, allowing you to refine the content you push. By utilising geo-location features, they can even push location-specific offers and content.</p><p>Websites are by no means fixed — they also offer a degree of customisation. It’s just not as extensive as apps. Websites are very adept at collecting user data and harvesting the information that powers your analytics. However, they’re less flexible when it comes to delivering personalised experiences.</p><p>If personalisation is central to your product, an app gives you the most room to do it well. Android shows how far this can go. Its dynamic colour system, refreshed in 2025 as part of Material 3 Expressive, lets apps take on the colours someone has chosen for their phone, so your app feels like part of their device. Apple and Google also now let apps use AI that runs on the phone itself, which opens up smarter, more personal features without sending everything to a server. You can see how we approach this in our <a href="https://thedistance.co.uk/solutions/ai-forward">AI app development work</a>.</p><h3>Where and when will people use it?</h3><p>Think about the moments your product is used in. Phones are brilliant for quick, focused tasks: checking a balance, approving a request, logging a job on site, or seeing what’s changed since yesterday. Apps can go further still, with home screen widgets, lock screen updates and watch apps that put the key information in front of people before they’ve even opened anything.</p><p>Read our article: <a href="https://thedistance.co.uk/insights/app-ux-optimisation">The Essential Guide to App UX Optimisation</a></p><p>If your users mostly sit at a desk working through detailed reports, a phone app might not be the first thing to build. Your website analytics will tell you how many people already visit on mobile and what they’re trying to do when they arrive. That’s a good place to start.</p><h3>Making the most of push notifications</h3><p>Push notifications are still one of the biggest advantages an app has. A message that lands on someone’s lock screen is far more likely to be seen than an email sitting in an inbox. That reach needs handling with care, though. Send too many and people switch them off. Send too few and you’re leaving a useful channel unused.</p><p>Websites can send notifications too, and since 2023 that has included iPhone. There’s a catch, though. On iPhone, only websites that someone has added to their home screen can send them, and only after that person has tapped to agree (<a href="https://webkit.org/blog/13878/web-push-for-web-apps-on-ios-and-ipados/">WebKit</a>). A normal browser tab can’t receive them at all. Few people take the extra step of adding a website to their home screen, so in practice most iPhone users will only get your notifications if you have an app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*KCkereKbOxCvJC9n" /></figure><h3>Recognising support and maintenance is key</h3><p>Many businesses choose between an app and a website based on initial investment costs and how complex the solutions are to implement. Far too many forget to consider the long-term maintenance spending required to support an app or website.</p><p>Apps generally need more ongoing care. Apple and Google release new versions of iOS and Android every year, and both regularly raise the standards an app has to meet to stay in their stores. Apple has removed older apps that haven’t been updated for a long time, so leaving an app untouched puts your brand at risk. In practice, it’s a choice between <a href="https://thedistance.co.uk/insights/why-do-apps-need-ongoing-maintenance">supporting your app</a> or retiring it.</p><p>So weigh up what an app will cost to run over several years, not just what it costs to launch. Working with a team that supports what it builds makes those costs far more predictable.</p><p>Websites also need regular maintenance and support. However, it’s typically easier and cheaper to perform. Unlike apps, websites don’t require users to download an update or go through an approval process. Developers can make incremental changes. This ability to tweak the website and make subtle alterations can be extremely beneficial.</p><h3>What about installable websites?</h3><p>Installable websites, often called progressive web apps, have come a long way. They’re well supported on Android, and since iOS 26 a website added to an iPhone’s home screen opens as a web app by default. For simple products, like a booking form or a tool only a handful of people use, they can be a sensible, low-cost step.</p><p>The trade-offs are real, though. People have to find the “add to home screen” option themselves, because there’s no app store listing to guide them. On iPhone, they still can’t connect to Bluetooth or NFC devices, and notifications only work once they’ve been installed. Apple also decides how they behave on iPhone, and that can change. In early 2024 it briefly removed support for them in the EU before reversing the decision. If your product is central to how you serve your customers, that’s a lot of uncertainty to build on.</p><h3>Building for iPhone and Android without doubling the cost</h3><p>Cost used to be one of the strongest arguments for choosing a website: build it once and it works everywhere. That gap has narrowed a lot. Cross-platform frameworks like React Native let one team build a single app that runs natively on both iPhone and Android, with most of the code shared between them. You still get the home screen presence, notifications, offline support and hardware access we’ve covered above, without paying for two separate builds.</p><p>React Native is our preferred way to build apps, and you can read more about why on our <a href="https://thedistance.co.uk/other-services/react-native-app-developers-uk">React Native app development</a> page.</p><h3>A quick way to decide</h3><p>An app is likely to be the right call if:</p><ul><li><strong>People will use it weekly or more.</strong> Being on their home screen keeps you part of their routine.</li><li><strong>It has to work where the signal is patchy.</strong> Apps handle offline use far more reliably than websites.</li><li><strong>It depends on the phone’s hardware.</strong> Think Bluetooth, NFC, background location, health data or wearables.</li><li><strong>Timely notifications matter.</strong> On iPhone, an app is still the dependable way to reach people.</li><li><strong>Personalisation is central to what you offer.</strong> Apps give you the most room to tailor the experience.</li></ul><p>Your website may be enough for now if:</p><ul><li><strong>People only need you occasionally.</strong> A good website serves one-off visits well.</li><li><strong>Your main goal is reaching new customers.</strong> Search, social and AI answers all lead to websites first.</li><li><strong>Most of your visitors use a desktop.</strong> Your analytics will show you whether that’s true.</li></ul><p>Most businesses end up with both: a website that helps people find you and an app that keeps them coming back. The real question is which to put first.</p><h3>What next?</h3><p>There’s rarely one right answer for every business. Work through the questions above and you’ll probably find that an app wins on some and your website wins on others.</p><p>Give each question a weight based on what matters most to your customers and how your business makes money. Nearly every business needs a website to be found. But if what you offer depends on regular use, the phone’s hardware, reliable notifications or working offline, an app could be central to where you go next.</p><p>If you’re weighing this up, it helps to talk it through with people who’ve seen it play out many times. We design, build and support apps for iPhone and Android, and every project starts with <a href="https://thedistance.co.uk/solutions/the-journey">The Journey</a>, our way of making sure an idea is worth building before anyone writes a line of code. <a href="https://thedistance.co.uk/contact-us">Get in touch</a> and we’ll give you an honest view, even if that view is that your website will do the job for now.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6653b49fa1d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is your Android app ready for Zero-Tap sign-in?]]></title>
            <link>https://medium.com/@TheDistance/is-your-android-app-ready-for-zero-tap-sign-in-567810358d15?source=rss-733ae949c85b------2</link>
            <guid isPermaLink="false">https://medium.com/p/567810358d15</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[android-apps]]></category>
            <category><![CDATA[android-app-developers]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[The Distance]]></dc:creator>
            <pubDate>Wed, 28 Oct 2026 12:46:13 GMT</pubDate>
            <atom:updated>2026-10-28T12:46:13.696Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>When someone gets a new phone, they expect their favourite apps to come with them. Their photos, contacts and settings might transfer across in a matter of minutes, but opening an app and finding themselves signed out can interrupt that experience. Suddenly, they’re searching for passwords, waiting for verification codes or trying to remember which email address they used to register in the first place.</strong></p><p>Google wants to make that process easier for Android users, and it’s introducing a new requirement that app owners need to be aware of. From April 2027, apps on Google Play that support user sign-in must support Zero-Tap Sign-In restoration, allowing users to regain access to their accounts when they move to a new Android device and restore their data.</p><p>For businesses with an existing Android app, the deadline is an opportunity to review how users sign in and whether their current authentication setup is ready. It also raises a wider question about whether passwords remain the right approach for their product, particularly as passwordless sign-in and passkeys become more widely adopted.</p><p>So, what does Google’s requirement involve, and what should app owners consider before April 2027?</p><h3>What is Android Zero-Tap Sign-In?</h3><p>Zero-Tap Sign-In is a feature that allows users to remain signed in to an app when moving from one Android device to another, without having to manually enter their credentials again.</p><p><a href="https://developer.android.com/identity/sign-in/restore-credentials">Google’s Restore Credentials API</a> enables an app to securely restore a user’s authenticated state when their data is transferred to a new device. For example, someone moving to a new phone could open their travel app and access their bookings without having to remember their password and sign in again.</p><p>The feature restores an existing signed-in state rather than removing authentication altogether. Users still need to register and authenticate when creating an account, and apps must continue to respect sign-outs and protect account access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*WQ3LryEjytUS9ymJ" /></figure><h3>What is the April 2027 deadline?</h3><p>Google has confirmed that, from April 2027, apps distributed through Google Play that support user sign-in, whether login is compulsory or optional, must support Zero-Tap Sign-In restoration when users move from their previous Android device to a new one and choose to restore their data.</p><p>The requirement applies to both device-to-device transfers and cloud backups. Google has also confirmed that the Restore Credentials API is available on Android 9 and above, covering a broad range of Android devices.</p><p>The consequences of failing to meet the requirement are worth understanding. This isn’t simply a recommendation for developers who want to offer a better user experience. It’s an upcoming Google Play requirement, so businesses should assess how it applies to their app and plan any necessary changes ahead of the deadline.</p><p>There are some exceptions. Google currently excludes games from the requirement, with further guidance expected for gaming authentication use cases. Certain permanently private and enterprise device-management apps are also outside its scope. Apps with strict regulatory or compliance requirements, including some financial services and healthcare products, may be eligible to request an exemption through Google Play.</p><p>Google also recognises qualifying apps that were already using the Block Store API to restore sign-in states by 30 September 2026 as compliant with the requirement.</p><h3>What will app developers need to do?</h3><p>Implementation involves more than updating the login screen. Restore Credentials needs to work with the app’s existing authentication system, backend and account-management processes. The work involved will depend on the product’s architecture and how its current sign-in functionality is built.</p><h3>1. Integrate the Restore Credentials API</h3><p>Google recommends implementing Restore Credentials through Android’s Credential Manager. Developers need to create a restore credential for authenticated users, make it available for transfer to a new device and use it to restore access when required.</p><p>The <a href="https://developer.android.com/identity/sign-in/restore-credentials-implementation">implementation documentation</a> explains the technical steps. Restore Credentials can work alongside existing authentication methods, including passwords and Sign in with Google, so apps don’t necessarily need to replace their current sign-in process.</p><h3>2. Check the backend and account security</h3><p>The backend must validate restore credentials before granting access. Developers also need to ensure that credentials are removed when users sign out or their access is revoked, and account permissions continue to work as intended.</p><p>Google’s implementation guidance notes that apps already using passkeys may be able to reuse their existing server-side authentication infrastructure. This makes the deadline a useful opportunity to review the wider authentication setup, rather than treating credential restoration as an isolated task.</p><h3>3. Test the complete device-transfer journey</h3><p>Before release, developers should test account restoration across devices, including cases where credentials are unavailable, sessions have expired or access has been revoked. They should also check that relevant app data and preferences transfer as expected, as restoring a user’s identity doesn’t automatically restore every part of their app experience.</p><p><a href="https://developer.android.com/identity/sign-in/test-restore-credentials">Google’s Restore Credentials testing guide </a>explains how to test the process using Android devices and emulators.</p><h3>Is it time to review your app’s authentication?</h3><p>Android’s Zero-Tap Sign-In requirement focuses on restoring access when users move to a new device, but it also presents an opportunity to review how people authenticate in your app more broadly.</p><p>Traditional passwords remain common, but they can create friction for users and additional work for support teams when people forget their credentials or struggle to regain access. Passwordless options, including passkeys, offer another approach by allowing users to authenticate using methods such as their device’s biometrics or screen lock.</p><p>Passkeys can also provide stronger protection against phishing than traditional passwords when implemented correctly. They won’t be the right choice for every product or every sign-in scenario, but they’re worth considering as part of a wider authentication strategy.</p><p>There is a useful connection here with Restore Credentials, too. Google’s implementation guidance explains that apps using passkeys may be able to reuse their existing server-side authentication infrastructure for credential restoration. The two features serve different purposes, but reviewing them together could help businesses make more informed decisions about their authentication setup.</p><p>We’ve explored this in more detail in our article <a href="https://thedistance.co.uk/insights/how-android-passkeys-are-changing-the-game-for-app-security">How can Passkeys improve in-app user security for Android and iOS?</a>, including how passkeys work and what they could mean for app security.</p><h3>How The Distance helps businesses prepare</h3><p>At The Distance, we help businesses understand how platform changes affect their apps and plan the technical work needed to respond. For Zero-Tap Sign-In, that starts with reviewing the existing authentication system, identifying any changes required across the app and backend, and planning implementation and testing ahead of the deadline.</p><p>It’s also an opportunity to look at the wider product. Whether you’re maintaining an established app or planning a new one, we can help you assess your authentication options, including passkeys and passwordless sign-in, and make decisions that suit your users, security requirements and long-term roadmap.</p><h3>Start preparing for Android’s 2027 requirement</h3><p>April 2027 may feel a long way off, but reviewing your authentication system now gives you more time to understand the work involved and plan it alongside other development priorities.</p><p>If you’re unsure whether your Android app is ready, The Distance can help you review your current setup, assess your options and plan the next steps.</p><p><a href="https://thedistance.co.uk/contact-us">Talk to our team about your app</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=567810358d15" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What do Apple and Google look for when approving an app?]]></title>
            <link>https://medium.com/@TheDistance/what-do-apple-and-google-look-for-when-approving-an-app-c83ca18a70e4?source=rss-733ae949c85b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c83ca18a70e4</guid>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[The Distance]]></dc:creator>
            <pubDate>Thu, 22 Oct 2026 08:46:01 GMT</pubDate>
            <atom:updated>2026-10-22T08:46:01.615Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Building an app is one thing, but getting it published on the App Store and Google Play is another. You might have a clear idea, a well-designed interface and a development team ready to bring everything together, but there are still a few important things to consider before your app is ready to reach its audience.</strong></p><p>One of the questions we often need to address when discussing a new app project is why it can’t simply replicate an existing product, turn a website into an app or rely on a standard template to get something live quickly. The answer comes down to what the finished product offers its users, how it works on their devices and whether it meets the requirements of the platforms where it will be published.</p><p>Apple and Google both want apps to provide a reliable, useful experience, but they have their own guidelines covering everything from minimum functionality and user privacy to technical compatibility. These requirements can influence decisions made much earlier in a project than you might expect, which is why we think they’re worth understanding before development begins.</p><p>So, what exactly do the app stores look for, and what should you consider if you’re planning to build an app of your own?</p><h3>Why Apple and Google might reject your app</h3><p>Let’s start with something that can catch businesses off guard. Having an app that works doesn’t automatically mean it will be approved for publication.</p><p>Apple and Google review submissions against their respective requirements, looking at areas such as functionality, technical quality, security, privacy and the experience offered to users. An app might work perfectly well in a development environment but still fall short of what a platform expects from a product available to the public.</p><p>There’s a good reason these checks matter. According to Apple’s 2025 App Store Transparency Report, <a href="https://www.apple.com/legal/app-store/transparency/2025/">Apple reviewed more than 9.1 million app submissions during 2025 and rejected 2,093,244 of them</a>. That’s approximately 23% of submissions reviewed, although the figure relates to submissions rather than unique apps, as developers can submit an app more than once.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*SrmqnHu3hnPvZCOC" /></figure><p>The report also records more than 1.35 million rejections under performance-related guidelines, alongside over 415,000 under design guidelines. These categories can overlap with other reasons for rejection, but they demonstrate that getting an app ready for publication involves more than checking whether its features work.</p><p>This doesn’t mean you should expect your app to be rejected, or that the process needs to be complicated. It means that understanding the requirements early gives you a better opportunity to make the right decisions, identify potential issues and prepare a product that meets the standards expected of it.</p><p>You can explore the requirements directly in <a href="https://developer.apple.com/app-store/review/guidelines/">Apple’s App Store Review Guidelines</a> and <a href="https://support.google.com/googleplay/android-developer/answer/9876937">Google Play’s Developer Programme Policies</a>.</p><h3>Your app needs to offer more than a template</h3><p>One of the conversations we regularly need to have with prospective partners is around how much of an app can be built using existing components or a standard template.</p><p>Reusable technology has a valuable role in app development. It can help development teams work more efficiently, reduce the amount of duplicated work and give businesses a more cost-effective starting point. The important distinction is between reusing technology to build a product and reusing a product without giving users anything meaningful or distinctive.</p><p>Apple’s minimum functionality guideline explains that apps should offer features, content and interfaces that go beyond a repackaged website. It also places restrictions on apps that primarily serve as marketing material, advertisements or collections of links rather than providing an adequate level of utility or entertainment. Google Play has its own policies covering repetitive content and apps that provide limited functionality or content.</p><p>In practical terms, imagine a business that already has a website containing information about its services. Turning every page into a mobile screen doesn’t necessarily give users a compelling reason to download an app. If they can do exactly the same things through their mobile browser, without any additional convenience or useful functionality, the product may struggle to meet the expectations of the app stores.</p><p>Now consider a different approach. The business identifies what its customers need to do regularly and builds an app around those activities. Users might be able to manage bookings, receive relevant notifications, access personalised information or complete tasks while they’re away from their desks. These features have a clear purpose because they support the way people interact with the business.</p><p>That doesn’t mean every app needs an entirely original concept or a long list of complicated features. A relatively simple product can still provide considerable value if it solves a specific problem well. What matters is that the functionality makes sense for the intended audience and gives the product a clear reason to exist.</p><p>This is also why we don’t see reusable technology and bespoke development as opposing approaches. The right foundations can help us build more efficiently, but the product itself still needs to be designed around its users, objectives and requirements.</p><h3>Does your app need to use device functionality?</h3><p>Another question worth asking is what your app will do that makes sense on a mobile device, rather than simply on a website.</p><p>Modern smartphones give developers access to a range of capabilities, including cameras, GPS, biometric authentication, Bluetooth and push notifications. Depending on the product, these features can make everyday tasks easier, provide information at the right moment or allow users to interact with a service in ways that wouldn’t be possible through a standard website alone.</p><p>For example, a travel app might use location services to help someone find nearby facilities, while a field operations app could allow employees to capture photographs, record information, and update job details while working on site. A healthcare app might use notifications to remind users about an activity or appointment, while biometric authentication could make signing in more convenient for a product handling sensitive information.</p><p>In each case, the functionality supports a particular user need. It isn’t there simply to demonstrate that the app can access the device’s capabilities.</p><p>It’s important to understand that Apple and Google don’t require every app to use every available device feature. A product shouldn’t request access to someone’s camera, location or contacts unless that access is necessary for its intended functionality. Instead, the question is whether the app makes appropriate use of the capabilities that genuinely benefit its users.</p><p>This is particularly relevant when businesses ask whether they should build a mobile app or a mobile-friendly website. Both can be valuable, but the right choice depends on what people need to accomplish, how frequently they’ll use the product and whether access to device capabilities would improve the experience.</p><p>If users primarily need to read information or browse a small collection of pages, a responsive website might be all they need. If they’re regularly completing tasks, interacting with other users, receiving updates or using features that benefit from integration with their device, a mobile app could be a better fit.</p><p>Thinking about this distinction at the beginning of a project helps you decide what you’re actually building and why. It also makes it easier to prioritise features that provide value rather than adding functionality simply to make the app appear more sophisticated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*iIxv091XctjpyAey" /></figure><h3>Functionality, stability and user experience matter</h3><p>Once you’ve established what your app needs to do, the next consideration is how reliably it does it. It’s easy to concentrate on the features that will make your product stand out, particularly when you’re working towards a launch date. However, the quality of the experience depends just as much on whether those features work as expected and whether users can navigate the app without running into problems.</p><p>Imagine downloading an app to manage an important booking, only to find that the confirmation screen doesn’t load. Perhaps the app crashes when you try to upload a photograph, or you can create an account but can’t complete the next step. Even if the product looks great, these problems make it difficult for users to achieve what they came to do.</p><p>Apple’s review guidelines cover performance, completeness and other aspects of app quality. Google Play also sets expectations around functionality, stability and the experience offered to users. Both platforms can reject submissions that fail to meet their requirements.</p><p>This is why testing needs to be part of the development process rather than something left until the final few days before launch. Teams need to check that the main user journeys work correctly, that features behave as expected and that the app performs appropriately across the devices and operating system versions it intends to support.</p><p>Testing should also account for what happens when things don’t go to plan. What happens if someone loses their internet connection halfway through a task? Can they recover from an error without losing their progress? Does the app explain what they need to do next if a service is temporarily unavailable?</p><p>These details might not be the first things you think about when planning a new product, but they can make a real difference to how useful and dependable it feels.</p><p>It’s also worth distinguishing between an app that’s technically complete and one that’s ready to launch. A feature might work in isolation but still create problems when it interacts with another part of the product. Reviewing the app as a whole helps identify these issues before they affect users.</p><p>A thorough quality assurance process gives the team time to find and resolve problems before submission, although no amount of testing can guarantee that an app will never encounter an issue after release. The aim is to launch with confidence that the product has been tested against its intended use and the requirements of the platforms it will run on.</p><h3>The technical requirements behind your app</h3><p>Not every app store requirement is visible to the person using the product. Some of the most important decisions happen behind the scenes, in the technology used to build the app and the way it interacts with the operating system.</p><p>Apple and Google regularly update their technical requirements to reflect changes in their platforms, including improvements to security, privacy and performance. Developers need to keep up with these changes when building new apps and maintaining existing ones.</p><p>For Android, one important example is the target API level. This determines the version of Android an app is designed to target and influences how it interacts with the operating system. Google Play uses target API requirements to encourage developers to adopt newer platform behaviour and security improvements.</p><p>As of 31st August 2026, new apps and app updates submitted to Google Play generally need to target Android 16 (API level 36) or higher. Existing apps generally need to target Android 15 (API level 35) or higher to remain available to new users on newer Android versions. There are exceptions for certain device categories and circumstances, so the specific requirements should always be checked before submission. You can find the latest details in <a href="https://support.google.com/googleplay/android-developer/answer/11926878">Google Play’s target API level requirements</a>.</p><p>Third-party software development kits, commonly known as SDKs, are another consideration. These are collections of tools and functionality that developers can integrate into an app rather than building everything from scratch. An app might use an SDK for analytics, payments, maps, notifications or other services.</p><p>Using an SDK doesn’t automatically create a problem, but developers need to understand what it does, what permissions it requires and how it handles information. A third-party library can affect the app’s privacy disclosures, security and compatibility, so it’s important to assess these dependencies rather than treating them as a minor implementation detail.</p><p>The same principle applies to the wider architecture of the product. The technology needs to support the features you’re planning to deliver, work with the relevant platform requirements and allow for ongoing maintenance as those requirements change.</p><p>This is particularly important for businesses planning to keep their app for several years. Launching is only one stage of a product’s life, and the decisions made during development can influence how straightforward it is to update, improve and support the app in the future.</p><h3>Privacy and permissions need to be considered from the start</h3><p>Technical compliance is only part of the picture. If your app collects personal information or accesses sensitive device features, you also need to consider how that information is handled and what users are told about it.</p><p>Depending on the product, this could include account details, location data, photographs, contact information, payment information or information about someone’s activity. The requirements will vary according to what the app does, the information it processes and the relevant platform policies and laws.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*OUaSEZxQjWux1a4R" /></figure><p>Both Apple and Google have rules covering privacy disclosures, permissions and data handling. Google Play, for example, requires developers to provide appropriate disclosures and obtain consent where its policies require them, particularly when an app accesses personal or sensitive information in ways users might not reasonably expect. Apple’s guidelines also cover data collection, privacy practices and the use of sensitive information.</p><p>The important thing is to make these decisions while the product is being designed, rather than waiting until the app is ready to submit.</p><p>Let’s say your app needs access to a user’s location. The team should establish why that access is needed, when it should be requested and how the information will be used. If location access is only required for a particular feature, there may be no reason to request it as soon as someone opens the app. Explaining the purpose clearly and requesting permission at an appropriate point can help users understand what’s happening and make an informed decision.</p><p>The same applies to third-party SDKs. If a library collects information or accesses device functionality, the app’s wider privacy approach needs to account for that behaviour. Choosing a library without understanding its data practices can create problems later, particularly if the app’s disclosures don’t accurately reflect what happens behind the scenes.</p><p>Getting privacy right isn’t simply a matter of satisfying a review checklist. It’s part of building a product that people can trust, especially when they’re sharing information or relying on the app to manage something important.</p><h3>What should you consider before building an app?</h3><p>By this point, you might be wondering what all of this means for your own idea. Do you need to understand every technical requirement before approaching a development team? Not necessarily, but there are a few questions worth exploring before you commit to a particular approach.</p><h3>What problem will the app solve?</h3><p>Start with the people who will use it and what they need to achieve. A clear understanding of the problem helps you decide which features are essential and which can wait. It also gives you a stronger basis for explaining why an app is the right solution.</p><h3>Why does it need to be a mobile app?</h3><p>Think about how people will use the product and whether mobile-specific functionality would make a meaningful difference. You don’t need to include every possible feature, but you should understand the value an app offers compared with a website or another digital service.</p><h3>Which features are essential for the first release?</h3><p>It’s tempting to include everything you can imagine, particularly when you’re investing in a new product. However, identifying the features that support the core purpose of the app helps you focus your budget and development time on what matters most. An MVP should still provide a useful, complete experience for its intended purpose.</p><h3>What technical requirements could affect the project?</h3><p>The answer will depend on your product. An app that uses location services, handles sensitive information or integrates with external systems may have different considerations from a straightforward content-based product. Identifying these requirements early gives the team time to assess the right technology and plan the work properly.</p><h3>How will the app be maintained after launch?</h3><p>Platform requirements change, operating systems evolve and users’ expectations develop over time. It’s worth considering how the app will be monitored, updated and supported once it’s live, including who will be responsible for addressing issues and keeping its technology up to date.</p><p>These questions don’t need to be answered in isolation. Working through them with an experienced product and development team can help you understand the options, identify potential challenges and make informed decisions before development gets under way.</p><p>That’s where discovery becomes particularly valuable. By exploring the objectives, audience, requirements and technical considerations before committing to a build, you can establish a clearer direction for the product and reduce the likelihood of discovering major issues later in the process.</p><h3>Building an app that’s ready for the app stores</h3><p>Apple and Google have their own requirements, and meeting them involves more than getting the code to work. Your app needs to offer meaningful functionality, provide a reliable experience, handle information appropriately and use technology that meets the relevant platform standards.</p><p>The good news is that these considerations don’t need to stand in the way of a good idea. When they’re understood early, they can help shape a better product by encouraging you to focus on what users actually need and how the app will work in practice.</p><p>At The Distance, we believe the strongest apps start with a clear understanding of the problem they’re solving. From discovery and product design through to development, testing and ongoing support, our approach considers the product as a whole, including what it needs to achieve and the requirements it needs to meet.</p><p>If you’re planning a mobile app and want to understand what’s involved before committing to development, we’d be happy to talk through your idea and help you work out the right next steps.</p><p><a href="https://thedistance.co.uk/contact-us">Discuss your app idea with The Distance</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c83ca18a70e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The App Store isn’t the only way people will find your app]]></title>
            <link>https://medium.com/@TheDistance/the-app-store-isnt-the-only-way-people-will-find-your-app-b2cacd1a3d82?source=rss-733ae949c85b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b2cacd1a3d82</guid>
            <category><![CDATA[app-store]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[The Distance]]></dc:creator>
            <pubDate>Tue, 20 Oct 2026 09:31:01 GMT</pubDate>
            <atom:updated>2026-10-20T09:31:01.691Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>For years, building an app has meant thinking carefully about how someone will find it. You create the product, publish it to the App Store or Google Play, work on your screenshots and description, encourage reviews, invest in acquisition and hope that when someone searches for something you offer, your app appears somewhere near the top.</strong></p><p>That model still matters. The App Store and Google Play are not disappearing, and for many products they will remain an important part of discovery for a long time. But there is another way of thinking about app discovery that is becoming increasingly important, and it starts with a much simpler question: <strong>what if people stop looking for apps altogether?</strong></p><p>Imagine someone saying, “I need to find a hotel near Manchester for Friday night, somewhere with parking and a late check-in.” Today, they might open Google, search for hotels, visit a few websites, perhaps open Booking.com or another travel app, enter their dates, apply filters and work their way through the results.</p><p>In an increasingly AI-led world, they could instead tell an assistant what they want to achieve and let it work out which services can help. The person doesn’t necessarily need to know which app they want. They don’t even necessarily need to know which website they need. They simply need to describe the outcome they are looking for.</p><p>That distinction might sound small, but for product owners it has some pretty significant implications. Because if the next generation of digital products is increasingly discovered through conversations, recommendations and actions from AI assistants, being a good app may no longer be enough.<strong> </strong>Your product also needs to be understandable and usable by the systems helping people find what they need. And we’re already seeing the foundations of that shift being built.</p><h3>From searching for an app to asking for an outcome</h3><p>The traditional app discovery journey is relatively straightforward. You have a need, so you search for an app that might solve it. You might search for “running tracker”, “budgeting app”, “train tickets”, “meal planner” or “photo editor”. You are effectively translating your problem into the language of the app marketplace.</p><p>The app store then gives you a collection of products that it believes match that search. The problem is that people don’t always think in product categories. They think about what they are trying to do.</p><p>Someone doesn’t necessarily wake up thinking, “I need a personal finance application with budgeting functionality.” They might think, “I need to work out where all my money is going this month.”</p><p>Someone travelling might not think, “I need a rail booking application.” They might think, “I need to get from Leeds to London tomorrow morning and I’d rather not change trains.”</p><p>Someone managing a field team doesn’t necessarily think, “I need a workforce management platform.” They might think, “I need to know which engineer can get to this job today.”</p><p>This is where conversational AI changes the starting point. Instead of translating the problem into something that a search engine or app store understands, the person can describe the problem in their own words and let the system interpret the intent behind it. That is a much more natural interaction.</p><p>It also creates a new question for product teams: <strong>if someone describes the problem your product solves without mentioning your product category, will the system understand that your app can help? </strong>That’s a very different kind of discoverability.</p><h3>AI is already becoming part of the discovery journey</h3><p>It is easy to think of this as something that will happen several years from now, but people are already using generative AI to research products, services and decisions.</p><p>Adobe’s analysis of more than a trillion visits to US retail websites found that <a href="https://blog.adobe.com/en/publish/2025/03/17/adobe-analytics-traffic-to-us-retail-websites-from-generative-ai-sources-jumps-1200-percent">traffic arriving from generative AI sources increased by 1,200%</a> in February 2025 compared with July 2024. In the same research, 39% of surveyed US consumers said they had used generative AI for online shopping, with product research and recommendations among the most common uses.</p><p>The numbers have continued moving in the same direction. Adobe reported that <a href="https://business.adobe.com/uk/blog/ai-driven-traffic-surges-across-industries">generative AI referrals to retail websites were up 693.4% year-on-year </a>during the 2025 holiday shopping season, while those AI-referred visits converted 31% better than other traffic sources.</p><p>That doesn’t mean everyone has suddenly abandoned Google or started shopping entirely through AI. The proportion of traffic coming from AI remains smaller than established channels, and these figures are primarily US data. What the numbers do show is something more useful: <strong>AI is becoming another layer between a person’s need and the product or service they eventually choose. </strong>And that layer is becoming increasingly capable of doing more than simply providing a link.</p><h3>The really interesting part is what happens after discovery</h3><p>Recommending an app is one thing, but being able to actually use it is another. Imagine saying: “Find me a train to London tomorrow morning, book the cheapest flexible option and put it in my calendar.” In a traditional journey, you would probably move between several interfaces. You might search for trains, compare options, choose a ticket, enter your details, complete the payment and then add the journey to your calendar.</p><p>An AI assistant could eventually become the layer coordinating that experience. It could understand what you’re asking for, identify the services capable of completing each part of the task, pass the relevant information between them and ask for confirmation where necessary.</p><p>The important thing here is that the user isn’t necessarily thinking about individual apps. They’re thinking about the task.</p><p>Apple is already building towards this model with <strong>App Intents</strong>, which allows developers to make an app’s actions and content discoverable by Apple Intelligence and available through experiences such as Siri, Spotlight and Shortcuts. Apple’s current developer documentation describes App Intents as the mechanism for connecting an app’s capabilities to Apple Intelligence and Siri AI.</p><p>Apple’s 2026 documentation goes further, describing how app actions can be understood through structured schemas so that Siri can interpret natural language and connect it to the appropriate action. Apple also describes experiences where actions can work across apps, allowing a person to move content or complete parts of a task between different services.</p><p>That is an important change in the role of an app. The app is no longer necessarily the place where the entire interaction has to happen. It can become a <strong>capability that another interface calls upon</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*pYceRt4QVGUCGzIu" /></figure><h3>Your app could become a capability, not just a destination</h3><p>This is probably the biggest idea for product owners to get their heads around. For a long time, the goal has been to get someone into your app. You want them to download it, open it, navigate through it, complete a task and come back again.</p><p>But AI assistants introduce another possibility. Your product could provide a particular capability that someone accesses without consciously thinking about opening your app. Think about a hotel booking app… Its value isn’t really “having a mobile application”, its value is helping someone find and book somewhere to stay.</p><ul><li>A travel app might provide live journey information.</li><li>A finance app might provide account information or help someone understand a transaction.</li><li>A fitness app might provide a workout or track an activity.</li><li>A retail app might help someone find a product and place an order.</li></ul><p>The interface is one way of delivering those capabilities, but it isn’t the capability itself. That distinction becomes increasingly important when designing products for an AI-led ecosystem. Instead of asking only: “What screens should our app have?” Product teams may increasingly need to ask: “What can our product do, and how could someone ask for those things?” That’s a much more interesting design question.</p><h3>Apple is already asking developers to think this way</h3><p>This isn’t just theoretical product strategy. Apple’s developer guidance gives us a pretty clear indication of the direction of travel.</p><p>With App Intents, developers can describe the actions their apps perform and the entities those actions operate on. Apple Intelligence can then use that information to understand the app’s capabilities. Apple specifically recommends identifying the actions people perform most often and considering the contexts in which those actions are useful. There’s another subtle but important piece here: <strong>language</strong>.</p><p>Apple’s documentation recommends using familiar terms for app content and actions because those terms help people interact with the product naturally through Siri. In other words, the way you describe your product’s capabilities matters. That’s something we already think about when we’re designing digital products.</p><p>A feature might have one name internally, another name in the database and something completely different in the interface because that’s the language users naturally understand. When AI is involved, that becomes even more important.</p><p>If your system calls something a “journey object” but your customer calls it a “booking”, you’ve got a language problem to solve. The machine needs to understand the structure of the product, while the person needs to be able to describe what they want naturally. Good product architecture sits in the middle.</p><h3>And Google is heading in a similar direction</h3><p>Apple isn’t alone. Google is also developing ways for Android apps to expose their capabilities to AI agents and assistants.</p><p>Android’s <strong>AppFunctions</strong> API is currently described by Google as an experimental preview that allows apps to provide functions, data and actions to the Android operating system so they can be used by proactive features, agents and assistants such as Gemini. Google describes AppFunctions as a mobile equivalent of tools within the Model Context Protocol, or MCP.</p><p>There is an important caveat here: Google’s documentation says that AppFunctions integration with Gemini was in private preview as of May 2026. So this shouldn’t be interpreted as saying that every Android app can already be freely controlled by Gemini in the way described above. What it does show is where the platform itself is heading. The operating system is starting to provide mechanisms for apps to expose <strong>functions</strong> rather than simply presenting an interface.</p><p>That distinction matters. A traditional integration might say:“Here’s a button that opens our app.” An AI-oriented integration starts to look more like: “Here’s an action our product can perform.” That is a much more flexible building block.</p><h3>Discovery could become contextual</h3><p>There is another reason this matters, App stores are relatively static environments. You search for something, and you receive results. AI assistants can potentially understand far more context around the request.</p><p>Consider these two searches: “Restaurant booking app” and: “Find me somewhere for dinner near the station tonight. I’m meeting two colleagues, one is vegetarian, and I’d rather somewhere we can actually talk.”</p><p>The second request contains considerably more information. An assistant can potentially use the person’s location, time, preferences, previous behaviour, calendar and other context to determine what they actually need.</p><p>Apple’s current Apple Intelligence documentation specifically talks about personal context, semantic search, app entities and contextual awareness. Developers can make app content available to the system and provide information about what is happening within an app so that Siri can better understand references such as “this photo” or “that message”.</p><p>This moves discovery away from a simple list of keywords and towards something much closer to <strong>contextual matching</strong>. And that changes what it means to be discoverable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*IlHaV7OJOBDNq1Oi" /></figure><h3>The new app store might be the conversation itself</h3><p>We’re not suggesting that the App Store suddenly becomes irrelevant. There will still be plenty of reasons to browse an app marketplace. People will continue discovering brands, comparing products, reading reviews and deliberately looking for apps.</p><p>But there could be another route into the product… the conversation. Someone might ask an assistant: “What’s the best way to keep track of my medication?” The assistant might explain a few options, they might then say: “Can you help me set that up?”</p><p>At that point, the interaction could potentially move from <strong>recommendation</strong> to <strong>action</strong>. The user hasn’t necessarily searched for your app, they haven’t necessarily seen your App Store screenshots and they haven’t necessarily read your carefully crafted app description. Instead, the assistant has effectively become the discovery layer. That creates an entirely different competitive environment.</p><h3>This doesn’t mean app store optimisation is dead</h3><p>It’s worth being clear about this because it would be easy to overreact. Your App Store listing still matters. Your Google Play listing still matters. Your website still matters. Your SEO still matters. Reviews, ratings, brand recognition, performance, accessibility and a good onboarding experience still matter too.</p><p>In fact, some of these things may become even more important because AI systems need reliable information from somewhere. What changes is that <strong>they are no longer the only discovery surfaces you need to think about</strong>. We’ve already seen a similar transition on the web.</p><p>Companies used to think primarily about ranking on traditional search engines. Then search became more conversational, featured snippets became more important, and now generative AI systems can summarise information and recommend businesses directly.</p><p>Adobe’s research has found rapid growth in AI-driven referral traffic and argues that <a href="https://business.adobe.com/uk/blog/the-explosive-rise-of-generative-ai-referral-traffic">appearing in generative AI responses is increasingly becoming part of the consumer consideration journey</a>. The same principle can start to apply to apps. You need to think about how your product can be understood, recommended and accessed by systems sitting between your customer and your interface.</p><h3>So what does this mean if you’re building an app?</h3><p>This is where the conversation becomes much more practical. If you’re currently planning an app, you don’t need to throw your existing product strategy in the bin and start building an AI agent tomorrow. What you do need is to think beyond the interface. Start with the jobs your product actually helps people complete, not the screens, not the features, not the technology. The jobs.</p><p>If your app allows someone to book a service, what exactly does “book a service” involve?</p><ul><li>What information does the user need to provide?</li><li>What decisions do they make?</li><li>Which parts can be automated?</li><li>Which actions need confirmation?</li><li>What information does the system need to retrieve?</li><li>What happens when there are multiple possible results?</li><li>What happens when the user’s request is ambiguous?</li><li>And which parts of that journey genuinely require the person to open the app?</li></ul><p>These questions are useful even if AI never enters the picture, because they force you to understand what your product actually does. But they also create the foundations for agentic experiences later.</p><h3>Design the capability before you design the screen</h3><p>One of the biggest mistakes we see in product development is starting with screens because they’re tangible. It’s much easier to draw a login screen than it is to define the underlying product logic. But when you start thinking about AI interactions, the limitations of a screen-first approach become obvious.</p><p>An assistant doesn’t necessarily need to know that your booking button is blue and sits in the top-right corner. It needs to understand:</p><ul><li>what a booking is</li><li>how to find one</li><li>how to create one</li><li>what information is required</li><li>what options are available</li><li>what actions are safe to perform automatically</li><li>which actions require confirmation</li><li>what happens when something goes wrong</li></ul><p>That is product thinking rather than interface thinking. And it’s something we put a lot of emphasis on during discovery.</p><p>Before we start building, we want to understand the problem, the audience, the journeys and the requirements properly. That gives us a much stronger foundation for deciding which experiences belong in the interface, which should be automated and where AI could genuinely add value. The technology comes afterwards.</p><h3>Think about your product as a set of actions</h3><p>A useful exercise for any product team is to take your existing app and temporarily ignore the screens. Instead, make a list of the things a user can actually do. For example:</p><p><strong>A travel product might allow someone to:</strong></p><ul><li>Search for journeys</li><li>Compare departure times</li><li>Check availability</li><li>Buy a ticket</li><li>View a booking</li><li>Change a journey</li><li>Cancel a booking</li><li>Download a ticket</li><li>Get disruption information</li></ul><p><strong>A finance product might allow someone to:</strong></p><ul><li>Check a balance</li><li>Search transactions</li><li>Categorise spending</li><li>Move money</li><li>Set a payment</li><li>Freeze a card</li><li>Find a statement</li><li>Understand a transaction</li></ul><p><strong>A field service product might allow someone to:</strong></p><ul><li>Create a job</li><li>Assign an engineer</li><li>Check availability</li><li>View a route</li><li>Update job status</li><li>Add notes</li><li>Upload evidence</li><li>Notify a customer</li></ul><p>Suddenly, the product looks very different. Instead of a collection of screens, you have a collection of capabilities. And those capabilities are much easier to reason about in an AI-powered world.</p><h3>But not every action should be available to an AI</h3><p>This is where good product thinking becomes particularly important. It would be tempting to make everything executable through an assistant. But convenience isn’t the only consideration.</p><p>Imagine an AI assistant being able to move money, cancel a booking, delete an account or send a sensitive message without any confirmation. The technology might be capable of doing it, but that doesn’t automatically make it a good experience.</p><p>Apple’s current App Intents guidance explicitly includes mechanisms for confirmation around destructive or sensitive actions and ownership of entities.</p><p>That’s an important principle for anyone building an AI-enabled product. The question isn’t simply “can the AI do this?” It’s: “Should the AI do this, and under what conditions?”</p><p>Some actions can be safely automated. Some should require confirmation. Some might need additional authentication. Some should remain entirely inside the product’s existing interface. That needs to be considered during product design rather than bolted on after the AI has been introduced.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*Wi3zdVHONuYvL3An" /></figure><h3>The interface might become smaller, not bigger</h3><p>There’s another interesting consequence. For years, digital products have accumulated features, such as:</p><ul><li>More dashboards.</li><li>More menus.</li><li>More settings.</li><li>More tabs.</li><li>More notifications.</li><li>More things competing for attention.</li></ul><p>But if people can simply ask for something directly, some of those journeys can become considerably shorter.</p><p>Instead of opening an app, finding the right section, selecting an item and completing a series of steps, the user might be able to express what they want in one natural request. That doesn’t mean the interface disappears. There will always be situations where visual interaction is better. Complex decisions, browsing, comparison, exploration and reassurance are all areas where a screen can be incredibly useful.</p><p>But it does mean we can start asking whether every action deserves its own journey through the UI. Some things might be better handled conversationally, some might be better automated, some might work better through voice, some might happen through notifications, widgets or wearable devices, and some will still belong exactly where they are today: inside the app.</p><p>The future isn’t necessarily about replacing one interface with another. It’s about having <strong>the right interface for the job</strong>.</p><h3>Your brand experience needs to survive outside your app</h3><p>This creates a slightly uncomfortable question for product owners. If an AI assistant becomes the interface between your customer and your product, how much of your brand experience actually survives? A beautifully designed app can communicate a huge amount through visual hierarchy, animation, typography, tone and interaction.</p><p>A conversational assistant can’t necessarily reproduce all of that. So your brand needs to become clearer at the level of the product itself.</p><ul><li>What does your service sound like?</li><li>How does it respond when something goes wrong?</li><li>What information does it prioritise?</li><li>How does it explain decisions?</li><li>When does it ask for confirmation?</li><li>How does it handle uncertainty?</li><li>What does it do when it doesn’t know the answer?</li></ul><p>These are becoming part of product design too. The experience of using your product might eventually begin before someone sees your interface and continue after they’ve left it.</p><h3>This also changes how we think about product analytics</h3><p>Today, many teams measure things like:</p><p><strong>Download → open → sign up → screen → screen → conversion.</strong></p><p>That’s useful, but an AI-led product ecosystem creates additional questions.</p><ul><li>How often is your capability being invoked?</li><li>Which requests are people making?</li><li>Which requests fail?</li><li>Where does the assistant need clarification?</li><li>Which actions are completed successfully?</li><li>Which actions result in the user being sent into the app?</li><li>Which tasks are now completed without opening the app at all?</li></ul><p>That last metric could feel strange at first. After all, product teams have spent years trying to increase app engagement. But if someone can complete exactly what they need without opening six screens, that might actually be a better product experience. The goal isn’t necessarily to maximise the amount of time someone spends inside your app. The goal is to <strong>help them accomplish something valuable</strong>.</p><p>That distinction is going to become increasingly important as AI removes friction from digital experiences.</p><h3>There is still a lot to work out</h3><p>It would be easy to read all of this and assume that we’re heading towards a world where everyone simply talks to an AI and apps disappear into the background. We’re not there. There are still significant questions around privacy, permissions, reliability, authentication, commercial relationships, platform access and user trust.</p><p>And the underlying technologies are developing quickly. Google’s AppFunctions, for example, is still described as an experimental preview, while Apple’s capabilities and developer frameworks are continuing to evolve. There will also be plenty of situations where people deliberately want to use an app.</p><p>If you’re booking a complicated holiday, managing your investments, designing a room or browsing a huge catalogue, there is real value in having a rich visual environment where you can explore and make decisions. So we don’t think the future is “apps versus AI”. It’s more interesting than that, it’s apps plus AI plus whatever interface makes the most sense at the time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*1HPGeXz1WeAQT65a" /></figure><h3>The app may become one part of a much bigger product</h3><p>This is the shift we think product owners should pay attention to. An app used to be the product. Increasingly, an app is becoming one part of a product ecosystem. The same underlying service might be available through:</p><ul><li>A traditional mobile app</li><li>A website</li><li>Voice</li><li>An AI assistant</li><li>A wearable</li><li>A widget</li><li>Notifications</li><li>Messaging</li><li>An API</li><li>An automated workflow</li><li>An AI agent</li></ul><p>The customer doesn’t necessarily care which one they’re using, they care that they can get something done. That means the job of a product team is becoming less about designing a single interface and more about designing a <strong>digital service that can work across different interfaces</strong>. And that is a very different way of approaching product development.</p><h3>What should product owners be doing now?</h3><p>If you’re already running an app, start by looking at the actions that matter most. Here are some questions to ask yourself:</p><ul><li>What do people repeatedly come into your product to do?</li><li>Which of those actions are relatively simple?</li><li>Which require lots of navigation?</li><li>Which involve information that could be retrieved automatically?</li><li>Which could benefit from natural language?</li><li>Which would be useful outside the app?</li><li>Then look at the structure underneath.</li><li>Are those capabilities exposed cleanly through APIs?</li><li>Are your data models well defined?</li><li>Can individual actions be triggered independently of the UI?</li><li>Do you have clear permissions around what can and cannot happen?</li><li>Do your systems know the difference between searching, previewing and committing an action?</li></ul><p>If you’re planning a new product, this thinking can happen even earlier. During discovery, you can map the user’s jobs, define the underlying capabilities and identify where traditional interfaces, automation and AI each make sense. That can save you from building an experience around assumptions that may look increasingly outdated as the platforms around it evolve.</p><h3>The next app you build might not feel like an app</h3><p>This is perhaps the most exciting part of where all of this is heading. We have spent decades designing digital products around the idea that a person opens something, navigates it and performs an action. Now we’re starting to build products where the person can simply describe what they want and the technology works out how to make it happen.</p><p>The app doesn’t disappear. The value it provides doesn’t disappear. The need for thoughtful design certainly doesn’t disappear. What changes is <strong>where the interaction begins</strong>.</p><p>It might begin with Siri or Gemini, it might begin with a voice command, a notification, a wearable or an AI agent, and sometimes it will still begin with someone tapping your icon because they simply want to explore your product themselves.</p><p>For product owners, that means the question isn’t just: “How do we get people to download our app?” It is becoming: “How do we make our product useful wherever our customers are asking for help?” That’s a much bigger opportunity.</p><p>And, from our perspective, it’s exactly why the best product development starts with understanding the problem rather than jumping straight into the interface. If you understand what people are trying to achieve, the technology can evolve around that goal, whether the final experience is an app, a website, an AI agent, a voice interaction or something we haven’t quite imagined yet.</p><p>Because the next generation of apps may not always ask people to find the app first, they may simply help them get what they need.</p><p>Ready to think beyond the app? The way people discover and interact with digital products is changing. If you’re exploring what AI, automation or new interfaces could mean for your product, our team can help you understand where the opportunities are and what it would take to turn them into something real.</p><p><a href="https://thedistance.co.uk/contact-us">Talk to our product team</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b2cacd1a3d82" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What the rise of foldable phones means for apps]]></title>
            <link>https://medium.com/@TheDistance/what-the-rise-of-foldable-phones-means-for-apps-2ec63c2bfdda?source=rss-733ae949c85b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ec63c2bfdda</guid>
            <category><![CDATA[apple-duo]]></category>
            <category><![CDATA[foldable-phone]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[The Distance]]></dc:creator>
            <pubDate>Wed, 14 Oct 2026 09:28:55 GMT</pubDate>
            <atom:updated>2026-10-14T09:28:55.463Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Ever since Samsung released the Galaxy Fold in 2019, a debate has raged over whether flip and fold phones are the future of mobile technology. By 2025, will we all have an elegant foldable phone in our pocket? Or is the technology a flash in the pan?</strong></p><p>Today (Sept 2022), flip and fold phones are still a relatively niche market. Of the 1.5 billion smartphones sold globally in 2021, only 7 million were foldables (<a href="https://www.wired.com/story/folding-phones-are-here-to-stay/">Wired</a>). However, that figure (and foldable’s total market share) is growing quickly. Foldable sales in 2021 represented a 264.3% increase on 2020s numbers and annual sales are expected to hit 27.6 million units by 2025 (IDC). Samsung has just launched the Galaxy Z Flip 4, while <a href="https://www.mi.com/xiaomimixfold2">Xiaomi</a>, <a href="https://consumer.huawei.com/en/phones/mate-xs2/">Huawei</a> and <a href="https://www.techradar.com/news/motorolas-samsung-galaxy-z-flip-4-rival-is-reportedly-going-global">Motorola</a> have all announced new foldable releases, too. This suggests foldable phones are here to stay. Or does it?</p><p>In this article, we examine whether foldable phones are the future of mobile technology and how that impacts app developers. But a quick note before we start. Throughout this piece, we use the term flip phones to refer to both flip and fold phones. We recognise there is a difference but the base technology is largely the same and we feel comfortable bracketing them together for convenience’s sake.</p><h3>2026 update — from experiment to an established category</h3><p>Fast forward to today, and the foldable conversation has quietly shifted. What once felt like a bold experiment has now become an established part of the smartphone market, with manufacturers investing in different form factors and users becoming increasingly familiar with the idea of a device that can change shape. That changes the conversation for product teams, too. Foldables are no longer something to design around if they eventually become popular enough. They are part of the wider range of screen sizes and shapes that a modern app needs to be prepared for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*jIG5sqCJd32dEosA" /></figure><p>Samsung, in particular, has doubled down on its commitment to foldables. The Galaxy Z Flip and Z Fold ranges are no longer framed as futuristic novelties, but as refined, repeatable upgrades that sit comfortably alongside its flagship devices.</p><p>Each iteration has focused less on proving the concept and more on improving durability, battery life, camera quality and software polish — all signs of a manufacturer playing the long game rather than chasing headlines.</p><h3>Are foldable phones the future?</h3><p>The question has changed. It is no longer simply whether foldables will become the future of mobile technology. They have already had enough influence on the market that product teams need to consider what they mean for the products being built today.</p><p>That does not mean every business needs to redesign its app specifically around a foldable device. Adoption will vary by market, audience and use case. But it does mean treating foldables as a temporary phase or an edge case is becoming harder to justify.</p><p>For developers, the more useful question is what happens when a device can move between very different screen configurations. A product designed responsively from the outset can adapt to those changes much more naturally, while one built around fixed layouts may require significant redesign as new form factors appear.</p><h3>There are hidden industry dynamics at play</h3><p>Though it would be nice to think that the technology industry is perfectly meritocratic and the best, most useful products always rise to the top, it is simply not the case. Technological evolution depends on adoption. Adoption is determined by a range of other forces, many of them market-based.</p><p>Which brings us on to market forces, foldable phones and the giant elephant in the room. Apple. The company with the second-largest smartphone market share — a company renowned for its trendsetting, industry-defining technology — is yet to produce a foldable phone. That is not to say they won’t. There are rumours that Apple is scheduling a foldable phone release for 2024–2025, but the company does not comment on upcoming technology, so we have no way of knowing if that is true.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*6tXbnGUlHlTYPCby" /></figure><h3>2026 update — Apple has finally entered the foldable market</h3><p>Well, the rumours can finally be put to bed. In September 2026, Apple officially unveiled the iPhone Duo, its first ever foldable iPhone and one of the biggest changes to the iPhone’s design since the original was launched in 2007.</p><p>That makes this a particularly interesting moment for foldable technology. For years, Samsung, Huawei, Xiaomi, Motorola and others have been trying to prove that folding screens have a genuine place in the smartphone market. Apple has now made its position clear: foldables are no longer something happening around the edges of the smartphone industry. They are part of the iPhone ecosystem.</p><p>The iPhone Duo takes a slightly different approach to the category, opening to reveal a 7.6-inch display while retaining a 5.4-inch outer screen when folded. Apple says both displays share the same aspect ratio, allowing content to scale proportionally between them, while iOS 27 has been redesigned to adapt to the different ways the device can be held and used.</p><p>And that last point is perhaps more important than the hardware itself.</p><p>Apple isn’t simply putting a folding screen onto an existing iPhone. The company has designed the hardware and software together, with the foldable format creating new opportunities for multitasking, gaming, photography, video calls and hands-free use. The camera experience, for example, makes use of the outer display in ways that aren’t possible on a traditional iPhone, while the larger inner display gives apps considerably more room to work with.</p><p>For product teams, this also makes responsive design a priority rather than an assumption. A book-style foldable can introduce a large, square or near-square working area that looks and behaves very differently from the tall, narrow screens most mobile interfaces have traditionally been designed around.</p><p>That has implications beyond simply making an interface fit. Navigation may need to change position, content may need to reflow, controls may need to become more accessible across a wider layout and components that work well in a portrait phone view may suddenly have much more space around them. Designing these behaviours from the beginning is far easier than trying to retrofit them once a product is already in development.</p><p>The arrival of a foldable iPhone therefore makes one thing particularly clear: responsive design can no longer be treated as making a desktop layout shrink down to mobile, or making an existing mobile interface stretch when a larger screen appears. It needs to account for the possibility that the shape and context of the screen itself can change.</p><p>For app developers, this makes Apple’s entry particularly significant. Until now, supporting foldables could reasonably be viewed as a decision based on the size of the Android foldable audience. With Apple now introducing its own interpretation of the format, product teams have another major ecosystem to consider, along with another set of screen sizes, orientations and interaction patterns.</p><h3>A strategic attempt to change the rules of the game?</h3><p>If you think we are overstating the importance of market dynamics in determining foldable technology’s success, think again. Conor Pierce, head of Samsung’s UK Mobile Division, stated explicitly that their foldable phones are a deliberate attempt to shake up the industry and erode Apple’s influence.</p><p>At the moment, people view smartphone technology through the prism of Apple vs <em>the others</em>. To counter this, Samsung wants to shift the discourse away from operating systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*GMskwrqhu3sZ1if1" /></figure><blockquote><strong>“What we want to try to do is disrupt and change the game when it comes to an OS conversation. When you walk into a store, ‘do you want a folding phone or do you want a flat phone?’ should be the first question you’re asked”</strong></blockquote><blockquote><a href="https://www.theguardian.com/technology/2021/sep/01/foldable-phone-techscape"><strong><em>Conor Pierce, in The Guardian</em></strong></a></blockquote><p>Marketing is another force at play in the foldable phone debate. When originally released, several designs (most notably the Motorola Razr) appeared to rely heavily on the nostalgia vibe. For some companies, emerging foldable technology seemed like a way to make money off a renewed interest in the light-hearted innocence of the pre-internet nineties and early noughties. Bucket hats, CDs, reboots of questionable ’90s TV shows and clamshell phones are all back in. Didn’t you know?</p><p>This gave some credibility to the idea that foldable technology was a bit of a gimmick. Three years on, this theory does not hold up well. The big tech players are investing heavily in foldable and adoption is on the rise. If it was a gimmick at the start, it certainly is not now.</p><h3>2026 update — Beyond Samsung is a crowded, competitive foldable landscape</h3><p>Samsung may have led the charge, but the foldable market has now become a genuinely competitive space. Huawei, Xiaomi, Motorola, Google and, most significantly, Apple have all developed their own interpretations of what a foldable phone should be.</p><p>This growing diversity is important. It suggests that foldables are no longer being developed around a single dominant vision. Instead, manufacturers are testing different assumptions about how people actually want to use these devices. Do users want a compact phone that unfolds occasionally, or a tablet-like screen they access multiple times a day? Is the outer screen a convenience feature, or a fully functional interface in its own right?</p><p>As competition increases, so does pressure on software and user experience. Hardware innovation can only go so far on its own. The real differentiator is increasingly how well the device integrates with apps, services and daily workflows — which brings the conversation back, once again, to developers.</p><h3>What do foldable phones mean for app developers?</h3><p>The other key issue for foldable phones is app development. On the first release, app compatibility was one of the biggest complaints. Apps were not designed for this new type of device and a considerable number did not perform well. Some did not fit the screen, others did not function as they should and many were simply not available for download on foldable phones.</p><p>While those early teething problems have eased, they are not entirely gone. Foldable phones still pose several challenges for app developers. These include:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*LHwOjsH8fZMzS1y4" /></figure><h3>Aspect ratio</h3><p>For years, mobile app design has largely been built around tall portrait screens, with landscape layouts added where necessary. Foldables have changed that assumption. Different devices can introduce dramatically different aspect ratios, and book-style foldables can move between a conventional phone display and a much larger, square or near-square screen.</p><p>This means responsive and adaptive design needs to be considered at the beginning of a project, rather than treated as something to address if a particular foldable becomes popular. Layouts need to respond to significant changes in available space without making the interface feel stretched, empty or difficult to navigate.</p><p>Square and near-square screens are particularly important because they can expose assumptions that are easy to make when designing for a conventional phone. A layout that feels natural on a tall portrait screen may suddenly have too much horizontal space, while navigation and content hierarchies can become awkward if they simply expand without being reconsidered.</p><p>The answer isn’t to create a separate version of an app for every possible device. It is to build flexible layouts and components that can respond intelligently to different dimensions and states.</p><h3>Resizeable apps</h3><p>Just as important is app continuity — how apps transition from one aspect ratio to another. Developers need to ensure that this transition feels natural and does not suffer from lag or bugs.</p><h3>Multi-window for multitasking</h3><p>A bigger screen size means there is more scope for multi-window multitasking. Browsing your photos on one part of the screen while typing a message on the other, for instance. Running multiple apps at the same time has the potential to radically alter the way we interact with our devices and how apps interact with one another. Developers will have to factor in new actions and gestures (such as <em>drag and drop</em>) to accommodate these capabilities.</p><h3>Foldable states</h3><p>Foldable phones also open up the possibility of a whole range of new display ‘states.’ With non-foldable models, there are two principal states. Portrait and landscape. But flip phones can be <em>folded</em>, <em>open</em>, or <em>half-open</em>. Apps may behave differently in each state.</p><p>When <em>half-open</em>, the top screen could be a chat interface and the bottom a keyboard, resulting in a display that resembles a traditional laptop setup. When <em>open</em>, the keyboard may take up less space, allowing for easier multitasking.</p><p>Secondary screens are typically included on the exterior of foldable phones to display notifications and other information, ensuring users don’t always have to open the device. These screens present another whole range of challenges and possibilities. What information should they include? How can they be used to streamline and simplify the user experience?</p><p>This is perhaps where foldable phones show the most potential. Whether app developers can take advantage of these capabilities may also determine how successful the technology is.</p><h3>2026 update — Why foldables should now influence product design</h3><p>When foldables first re-emerged, many product teams quite reasonably chose to wait and see. Supporting them felt like a future problem, something to revisit once adoption reached a meaningful level.</p><p>That approach is becoming less useful. More major manufacturers are committing to different versions of the format, and Apple has now brought the book-style foldable into the iPhone ecosystem.</p><p>For product teams, the practical takeaway isn’t that every app needs a dedicated foldable experience. It’s that responsive design needs to account for a much wider range of screen configurations from the beginning, particularly square and near-square layouts.</p><p>The same principles also make products better prepared for tablets, larger phones and whatever form factors emerge next. Foldables are therefore less about designing for one particular device and more about avoiding an app architecture that assumes tomorrow’s screens will look exactly like today’s.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*fj3LnwZqVFSUlQqP" /></figure><h3>2026 — Foldables are changing how we design</h3><p>Foldables have become more than a question of whether people will eventually replace their traditional smartphones. They have changed the assumptions we make about what a mobile device looks like, how much space an app has to work with and how users move between different ways of interacting with a product.</p><p>The arrival of the iPhone Duo makes that shift particularly difficult for product teams to ignore. Foldables are now represented across the major smartphone ecosystems, while book-style devices introduce screen configurations that are very different from the tall portrait displays that have dominated mobile design.</p><p>That doesn’t mean every app needs a bespoke foldable experience. It does mean responsive and adaptive design should be considered from the beginning of a project, particularly when thinking about square and near-square layouts.</p><p>Foldables may or may not become the dominant smartphone format. We don’t need to predict that to know they’re already influencing how digital products should be designed.</p><p>If you’re looking to create a foldable-friendly app for your business, The Distance can help.</p><p><a href="https://thedistance.co.uk/contact-us">Chat to one of our experienced team members today!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ec63c2bfdda" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The questions we’re asked about building apps]]></title>
            <link>https://medium.com/@TheDistance/the-questions-were-asked-about-building-apps-4c70aeecebd3?source=rss-733ae949c85b------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c70aeecebd3</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <category><![CDATA[mobile-app-agency]]></category>
            <dc:creator><![CDATA[The Distance]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 09:01:03 GMT</pubDate>
            <atom:updated>2026-09-21T09:01:03.991Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Building an app sounds simple enough. You have an idea, you find a development team, you build it, put it in the App Store and wait for people to use it. Of course, anyone who has actually built a product knows it rarely works that way.</strong></p><p>Before development even begins, there are decisions to make about the problem you’re solving, who you’re solving it for, what the first version should contain and whether an app is even the right solution. Then there are questions around budgets, technology, design, accessibility, testing, AI, launch and what happens once the product is finally in people’s hands.</p><p>These are the questions we hear all the time at The Distance. Sometimes they come from someone with a fully formed product idea. Sometimes they’re from a business that knows there is a problem worth solving but isn’t sure what the solution should look like yet. And sometimes they’re from an established organisation with an existing app that has reached the point where it needs to evolve.</p><p>After working through these decisions with product owners across different industries and at different stages of their journey, we’ve found that the same themes tend to come up again and again. So, rather than answering each question in isolation, we’ve brought them together in one place.</p><p>Whether you’re considering your first app, planning the next version of an existing product or simply trying to understand what is involved before you start speaking to development agencies, this guide will help you understand the questions worth asking, the decisions worth making and some of the common mistakes we’ve seen along the way. And perhaps most importantly, it’ll help you understand where you don’t need to have all the answers yourself.</p><h3>Before starting the project</h3><p>The earliest stage of an app project is often where the biggest decisions are made, even though there isn’t any code to show for it yet. It’s tempting to think that the first step is choosing a development agency or starting to write a specification, but we’d encourage you to step back from the solution for a moment.</p><p>Before deciding what you’re going to build, you need to understand why you’re building it. That means getting comfortable with the problem, understanding the people experiencing it and making sure there is a genuine opportunity behind the idea.</p><h3>How do I know what features my app actually needs?</h3><p>This is one of the easiest questions to get backwards. A lot of product owners start with a feature list because it’s something tangible. You can write down “login”, “payments”, “notifications”, “profiles” and “booking”, and suddenly it feels as though you’ve defined the product.</p><p>But a list of features doesn’t necessarily tell you what the product needs to do. We prefer to start with the experience we’re trying to create and the problems we’re trying to solve. Once we understand those, the features become much easier to work out.</p><p>Think about what your user is actually trying to achieve. If you’re building a travel app, for example, the important question isn’t necessarily “what features should a travel app have?” It might be “what does someone need to be able to do before, during and after their journey, and where are the points at which the current experience isn’t working?”</p><p>That shift in thinking can completely change the product. Instead of adding features because they seem useful, you’re considering each one in the context of a real user need and a business objective. We also need to think about what belongs in the first version.</p><p>Not everything that could eventually be part of the product needs to be there on day one. Trying to build everything at once can make a project more expensive, more complicated and harder to validate. That doesn’t mean you should build a deliberately poor first version, either.</p><p>A good first version should contain enough of the right experience to solve the core problem properly. It should give users something valuable and give the business something it can learn from. The distinction is important.</p><p><strong>An MVP shouldn’t mean “the app with the fewest possible features”. It should mean the smallest version of the product that can deliver meaningful value and help you learn.</strong></p><p>That’s a much more useful way of deciding what belongs in version one.</p><h3>How do I validate my app idea before spending money?</h3><p>You don’t necessarily need to build an app to find out whether people want it. In fact, we’d strongly recommend finding ways to learn before committing to development wherever possible.</p><p>Validation can take many forms, depending on the idea. You might speak to people who experience the problem you’re trying to solve. You might research competitors and alternatives. You might prototype an experience and put it in front of potential users. You might test a particular assumption with a lightweight experiment.</p><p>The important thing is that you’re looking for evidence rather than simply asking people whether they think your idea sounds good. There’s a big difference between someone saying, “That sounds useful,” and someone demonstrating that they have a genuine problem they’re already trying to solve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*HL2RxPyXdCqaCXMp" /></figure><p>When we’re working through an idea during <a href="https://thedistance.co.uk/insights/why-the-discovery-phase-is-key-to-building-the-right-app">Discovery</a>, we’re interested in understanding the behaviours behind the problem. What are people doing today? What frustrates them? What are they willing to change? What would make the proposed solution genuinely useful?</p><p>That information gives you something much more valuable than reassurance. It gives you direction. And validation shouldn’t stop once development begins. Good product development is a continuous process of learning, testing and improving. The more uncertainty you can remove before making expensive decisions, the better.</p><h3>Budget, business case and investment</h3><p>Once you’ve established that there’s a genuine opportunity, the conversation inevitably moves towards money. And understandably so. An app isn’t just a development project. It’s an investment in a product that will need to create enough value to justify the money, time and resources put into it.</p><h3>What ongoing costs should I expect after my app launches?</h3><p>One of the biggest misconceptions we come across is that the main cost of an app is the development itself. Development is a significant part of the investment, but launching an app doesn’t mean the costs stop.</p><p>Depending on your product, there may be ongoing infrastructure and hosting costs, third-party services, API usage, analytics, monitoring and other technology costs. There are also the costs associated with maintaining the app itself, fixing issues, supporting users and keeping it compatible with new operating system versions and devices.</p><p>Then there’s the product side.</p><p>Your users’ expectations will change. Your business will change. Your competitors will change. New technologies will emerge. You may discover that something you thought users wanted isn’t particularly useful, while another opportunity becomes much more important. A successful app therefore needs to evolve.</p><p>This doesn’t mean you need a huge development team working on it indefinitely, but you should think about maintenance and future development as part of the product lifecycle from the beginning.</p><p>When we’re planning an app with a client, we don’t just think about what needs to exist on launch day. We also think about how the product needs to be supported, monitored and evolved afterwards. Because the real measure of an app isn’t whether you managed to get it into the App Store. It’s whether it continues to deliver value once it’s there.</p><h3>Can I start small and add features later?</h3><p>Yes, and in many cases, that’s exactly what we’d recommend. The important distinction is between <strong>starting small</strong> and <strong>building something that isn’t fit for purpose</strong>.</p><p>Starting small means identifying the core problem and building the experience necessary to solve it properly, while deliberately leaving less important features for later. That’s a sensible product strategy because it allows you to learn from real users before making bigger investments. The trick is to make sure the foundations are right.</p><p>If you know that the product will eventually need additional capabilities, integrations or user journeys, those future requirements should be considered when the product and technical architecture are being planned. You don’t necessarily need to build them yet, but you don’t want to make decisions today that make tomorrow unnecessarily difficult or expensive.</p><p>We’ve found that the strongest products tend to evolve in stages. You start with a clear purpose, learn how people use the product, understand where the opportunities are and then use that information to decide what comes next. That gives you something much more valuable than a giant roadmap created months before anyone has used the product… it gives you a product roadmap based on evidence.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*CrG7LvHAYsqwUjXh" /></figure><h3>What happens if my app project runs over budget?</h3><p>The best way to deal with a project going over budget is to understand why it happened in the first place. Sometimes it’s because the scope has changed. Sometimes new technical requirements emerge. Sometimes assumptions made at the beginning turn out not to be correct. And sometimes the original scope simply wasn’t defined in enough detail.</p><p>This is another reason we place so much importance on Discovery. The earlier you can identify uncertainty, the easier it is to make an informed decision about it. That doesn’t mean every project can be predicted down to the last pound. Software development involves complexity, and there will always be things you learn along the way. What matters is how that uncertainty is managed.</p><p>If a new requirement appears halfway through a project, for example, you should be able to understand what it means for the timeline, budget and existing scope. You can then make a decision about whether it’s important enough to include now, move something else out or leave it for a later version.</p><p>The worst situation is when changes happen quietly, and the impact only becomes apparent when the budget has already disappeared. Good communication, clear priorities and a shared understanding of the product are therefore just as important to managing a budget as the original estimate itself.</p><h3>Strategy and Discovery</h3><p>This is the part of an app project that can be difficult to explain because, at first glance, it can look like you’re paying someone to talk about your app rather than build it. But the thinking that happens before development can have an enormous impact on what eventually gets built.</p><h3>What decisions should we make before development starts?</h3><p>You don’t need to have every decision made before you speak to an agency. That’s what a good product team is there to help with. But there are some fundamental questions that need answering before development can sensibly begin. You should understand:</p><ul><li>Who the product is for</li><li>What problem you’re solving</li><li>Why that problem matters</li><li>What the business needs the product to achieve</li><li>What the core user journeys look like</li><li>Which features are essential to those journeys</li><li>What success will look like</li><li>Which platforms and devices are relevant</li><li>What integrations or technical requirements exist</li><li>What constraints the project needs to work within</li><li>How the product might evolve after launch</li></ul><p>The important thing is that these decisions shouldn’t be made independently. Your technical choices affect your budget. Your business objectives affect your feature priorities. Your users’ needs affect the experience you design. Your future plans affect the architecture you put in place today.</p><p>That’s why we don’t see strategy, design and technology as separate conversations. They’re all parts of the same product decision.</p><h3>How do I know which features should be in version one?</h3><p>We’d start by asking what the product absolutely needs to do to solve its core problem. From there, features can be considered against several factors: how much value they provide to users, how important they are to the business, how complex they are to build, what risks they introduce and whether other features depend on them.</p><p>This is where prioritisation becomes useful. Imagine you have twenty potential features. If you simply ask, “Would this be useful?”, you might end up saying yes to all twenty. Instead, ask: <strong>If we don’t build this, can the product still solve the core problem?</strong></p><p>If the answer is yes, that feature might not need to be part of version one. That doesn’t mean it isn’t valuable. It might simply mean that its value can be explored later, once you’ve learned more about the product and its users.</p><p>We’ve seen projects become considerably more complicated because the first version was treated as an opportunity to build every idea anyone had ever discussed. The better approach is to create a focused product that does the important things well, rather than an enormous product that tries to do everything.</p><h3>Should we build what customers ask for or what the business needs?</h3><p>The answer is usually somewhere in between. Customers are an incredibly important source of information, but their requests shouldn’t automatically become product requirements. If ten customers ask for a particular feature, that’s useful information. But the next question should be: <strong>what problem are those customers trying to solve?</strong></p><p>A customer might ask for a specific feature because they’ve already imagined the solution. That doesn’t necessarily mean their proposed solution is the best one. The same applies to the business.</p><p>A feature might be strategically important to the organisation, but if customers don’t understand it, can’t use it or don’t see the value, it may not achieve what the business expects.</p><p>The role of product strategy is to bring those perspectives together. We look at what customers need, what the business needs to achieve, what the evidence tells us and what is technically and commercially realistic. That allows you to make decisions based on the bigger picture rather than simply building the loudest request.</p><h3>How do I turn customer feedback into useful product decisions?</h3><p>Customer feedback becomes useful when you stop treating it as a list of instructions and start looking for the problems underneath it. Imagine a customer says, “We need a better search.” That’s a useful observation, but it isn’t necessarily a requirement to redesign the search function.</p><ul><li>Why isn’t the current search working?</li><li>Are people struggling to find particular information?</li><li>Are they using the wrong terminology?</li><li>Are there too many results?</li><li>Are they looking for something that doesn’t exist?</li><li>Is search even the right solution?</li></ul><p>Those questions can lead you towards a much better product decision.</p><p>We recommend looking for patterns rather than reacting to individual comments. Combine qualitative feedback with quantitative information wherever possible, and consider what you’re hearing alongside your wider business objectives. One person’s request shouldn’t automatically determine your roadmap. But repeated evidence of a genuine problem absolutely should influence it.</p><p>This is where good product teams earn their keep. Our job isn’t simply to take everything a client or customer says and turn it into a feature. It’s to help interpret the information, challenge assumptions and work out what will genuinely improve the product.</p><h3>AI and the changing app landscape</h3><p>AI has introduced a slightly different set of questions for anyone thinking about building a digital product.m The most common one is probably some variation of: <strong>if AI can do more of this for users, do we still need an app? </strong>It’s a fair question. But we think the answer is more interesting than simply saying apps are here to stay.</p><h3>Will users still open apps if AI assistants can do things for them?</h3><p>We think people will continue to use apps, but the way they interact with products is likely to change. For years, the dominant model has been that a user opens an app, navigates through its interface and performs an action. AI introduces another possibility.</p><p>Instead of navigating through an interface, someone might simply tell an assistant what they want to achieve and let it work out the steps. That doesn’t make the underlying product irrelevant. It changes the relationship between the user and the product.</p><p>A travel company, for example, may still need an app where customers can manage bookings, access important information and complete tasks. But there may also be value in allowing an AI assistant to retrieve that information, make changes or perform actions on the user’s behalf.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*tcnWK5llJvp6jay3" /></figure><p>So the question we would ask isn’t, “Will AI replace my app?” It’s: <strong>Where will my users expect to interact with my product in the future? </strong>That might still be a mobile app. It might be a web experience. It might be through an AI assistant. It could be several of these at once.</p><p>The strongest products will be prepared for that reality rather than assuming there will only ever be one interface between the user and the service.</p><h3>Should I design my app for humans, AI agents or both?</h3><p>Increasingly, we’d argue that you should be thinking about both. Your human users still need an experience that makes sense to them. It needs to be understandable, accessible and enjoyable to use. But if you want AI agents to interact with your product, there are other considerations. Can an agent:</p><ul><li>understand what your product does?</li><li>access the information it needs?</li><li>securely perform actions?</li><li>structure systems in a way that allows those actions to happen reliably?</li></ul><p>This means thinking beyond the interface.</p><p>An app isn’t just the screens someone sees. Behind those screens are APIs, data, authentication, permissions, business rules and systems that make the experience possible. As AI becomes another way of interacting with those systems, the underlying product architecture becomes increasingly important.</p><p>This is something we’re particularly interested in at The Distance because we’ve been exploring the idea of products existing beyond a traditional visual interface. The future isn’t necessarily about choosing between a beautiful app and an AI agent. It may be about building a product that can support both.</p><h3>Does my new app need AI?</h3><p>No. And we’d be suspicious of anyone who told you that every new app does.</p><p>AI is incredibly useful when it’s solving a problem that genuinely benefits from it. But adding AI simply because it’s currently popular can introduce unnecessary cost, complexity and uncertainty.</p><p>Start with the problem. If users need help understanding large amounts of information, generating content, making sense of complex data, interacting conversationally or automating a task that requires judgement, AI might be a very good fit.</p><p>But sometimes a normal feature is better. If someone needs to press a button to book a ticket, there’s no reason to introduce an AI model just for the sake of it. Good technology choices aren’t about using the newest technology available. They’re about choosing the technology that helps you solve the problem effectively. AI should be treated in exactly the same way.</p><h3>Design, UX and accessibility</h3><p>Once you’ve worked out what you’re building, you need to make sure people can actually use it. And this is where good app design goes considerably further than making something look nice.</p><h3>How do I make my app work well across different screen sizes and devices?</h3><p>You can’t assume that everyone will experience your app in exactly the same way. Different phones have different screen sizes, aspect ratios, resolutions and capabilities. People can also change text sizes, accessibility settings and display preferences, while operating systems introduce their own conventions and behaviours.</p><p>That’s why responsive and adaptive thinking needs to be part of the design process from the beginning. Rather than designing a single screen at a single size and hoping it scales correctly, you need to understand how the interface behaves across different conditions. Such as:</p><ul><li>Where does content wrap?</li><li>What happens when text becomes larger?</li><li>Does an important button remain accessible?</li><li>What happens on a smaller screen?</li><li>What happens when someone rotates their device?</li><li>Can someone using assistive technology understand what’s happening?</li></ul><p>These are part of designing a product that works for real people. And testing is just as important as design here. A design can look perfect in a design tool and behave very differently when it’s running on an actual device.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*fMTpDlGLX2T3vNOz" /></figure><h3>Should my iOS and Android apps look exactly the same?</h3><p>Not necessarily. Your iOS and Android products should feel like the same product, but that doesn’t mean every interaction needs to be identical. Both platforms have established conventions around navigation, controls, gestures and interaction patterns. Users have developed expectations based on the devices they use every day.</p><p>Ignoring those conventions can make an app feel unfamiliar, even when the underlying functionality is exactly what the user needs.</p><p>At the same time, you don’t want to create two completely unrelated products. Your brand, visual identity, core journeys and overall experience should feel consistent. The trick is understanding where consistency matters and where adapting to the platform creates a better experience.</p><p>That’s something we consider during the UX and UI design process rather than simply taking one set of screens and copying them across both platforms. Good cross-platform design isn’t about making everything identical. It’s about making everything feel intentional.</p><h3>Launch, testing and what happens afterwards</h3><p>Getting an app into development can feel like the main challenge, but the final stages of a project raise some equally important questions.</p><h3>Is the App Store still the best way to reach app users?</h3><p>The App Store and Google Play remain important distribution channels for mobile apps, but they aren’t necessarily the only way people should interact with your product. The right answer depends on what you’re building and how your users behave.</p><p>Some products benefit enormously from being installed on a phone. If someone uses the product frequently, needs notifications, relies on device capabilities or wants quick access, a native app can make a lot of sense. For other experiences, a web app or progressive web experience may be more appropriate.</p><p>And as we’ve discussed, AI assistants are creating another potential channel through which people can interact with digital services. So rather than starting with the assumption that you need an App Store app, we’d recommend starting with the user journey.</p><p><strong>Where will your customers be, what will they be trying to do and what is the most useful way for your product to meet them there?</strong></p><p>The answer might be an app. It might be a web experience. It might be both. The important thing is that the technology follows the product strategy rather than the other way around.</p><h3>What does “done” actually mean when building an app?</h3><p>This is a deceptively difficult question…</p><ul><li>Does “done” mean the developers have finished writing the code?</li><li>Does it mean the app has passed QA?</li><li>Does it mean it’s been submitted to the App Store?</li><li>Does it mean users can download it?</li><li>Or does it mean the product is achieving the outcomes you originally wanted?</li></ul><p>We’d argue that all of those are milestones, but none of them necessarily mean the product is finished.</p><p>A development team might complete everything in the agreed scope, only for the product team to discover after launch that users are struggling with a particular journey. That’s not necessarily a sign that development failed. It’s a reminder that software products exist in the real world, where people behave in ways that aren’t always predictable.</p><p>We therefore think about “done” in stages. A feature can be development complete. It can be tested. It can be ready for release. It can be live. And then it needs to prove its value. That last part is often overlooked. Launching an app isn’t the end of product development. It’s the point at which you finally have the opportunity to learn from real usage at scale.</p><h3>Why does my app need testing if everything works on my phone?</h3><p>Because your phone isn’t everyone’s phone. An app that works perfectly on one device can behave differently elsewhere because of differences in screen size, operating system versions, hardware, network conditions, permissions, settings and other factors.</p><p>Then there are the situations you probably don’t encounter during your own testing, such as:</p><ul><li>What happens when someone loses their internet connection halfway through an action?</li><li>What happens if they enter something unexpected?</li><li>What happens if they deny a permission?</li><li>What happens when the device has very little storage?</li><li>What happens when the app is interrupted?</li><li>What happens when an operating system update changes something your app relies on?</li></ul><p>Testing is about finding those situations before your users do. It’s also about more than checking whether buttons work. Good QA considers functionality, usability, performance, accessibility, compatibility and the wider experience.</p><p>This is why we treat testing as part of the development process rather than something that happens at the very end as a final tick-box exercise. The earlier you find problems, the easier they generally are to address. And the less likely your users are to become the people who discover them for you.</p><h3>The questions to ask before building an app</h3><p>If there’s one thing we hope you take away from all of these questions, it’s that building an app isn’t really about answering, “How quickly can we get this developed?”</p><p>It’s about making good decisions in the right order. Before:</p><ul><li>you worry about individual features, understand the problem.</li><li>you decide how much to spend, understand the opportunity.</li><li>you start development, understand what the first version genuinely needs to achieve.</li><li>choosing technology, understand the product and the people using it.</li><li>adding AI, understand whether AI actually solves the problem better.</li><li>launching, test the product in the real conditions your users will experience.</li></ul><p>And once the product is live, keep learning.</p><p>The best app projects we’ve worked on aren’t the ones where every decision was somehow perfect from day one. They’re the ones where there was a clear process for asking questions, challenging assumptions, testing ideas and using what we learned to make better decisions. That’s ultimately what good product development is about.</p><p>You don’t need to arrive at your first conversation with an agency knowing exactly what needs to be built, which technology should be used or what every screen should look like. In fact, if you already have all of those answers, it’s still worth asking whether the assumptions behind them have been tested.</p><p>What you do need is a clear understanding of the problem you’re trying to solve and a willingness to explore the best way of solving it. That’s where we come in.</p><p>At The Distance, we work with businesses from the early stages of an idea through strategy, Discovery, UX and UI design, development, testing, launch and ongoing evolution. Our role isn’t simply to take a specification and turn it into an app. It’s to help you make the decisions that give the product the best possible chance of succeeding. Because ultimately, the goal isn’t to build an app. <strong>It’s to build the right product.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c70aeecebd3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What the rise of foldable phones means for apps]]></title>
            <link>https://medium.com/@TheDistance/what-the-rise-of-foldable-phones-means-for-apps-3f8d36f006a9?source=rss-733ae949c85b------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f8d36f006a9</guid>
            <category><![CDATA[foldable-phone]]></category>
            <category><![CDATA[apple-duo]]></category>
            <category><![CDATA[phone]]></category>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[The Distance]]></dc:creator>
            <pubDate>Fri, 18 Sep 2026 08:01:04 GMT</pubDate>
            <atom:updated>2026-09-18T08:01:04.161Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This blog was originally written in 2022 but has been updated in 2026 to fit the latest phone releases.</em></p><p><strong>Ever since Samsung released the Galaxy Fold in 2019, a debate has raged over whether flip and fold phones are the future of mobile technology. By 2025, will we all have an elegant foldable phone in our pocket? Or is the technology a flash in the pan?</strong></p><p>Today (Sept 2022), flip and fold phones are still a relatively niche market. Of the 1.5 billion smartphones sold globally in 2021, only 7 million were foldables (<a href="https://www.wired.com/story/folding-phones-are-here-to-stay/">Wired</a>). However, that figure (and foldable’s total market share) is growing quickly. Foldable sales in 2021 represented a 264.3% increase on 2020s numbers and annual sales are expected to hit 27.6 million units by 2025 (IDC). Samsung has just launched the Galaxy Z Flip 4, while <a href="https://www.mi.com/xiaomimixfold2">Xiaomi</a>, <a href="https://consumer.huawei.com/en/phones/mate-xs2/">Huawei</a> and <a href="https://www.techradar.com/news/motorolas-samsung-galaxy-z-flip-4-rival-is-reportedly-going-global">Motorola</a> have all announced new foldable releases, too. This suggests foldable phones are here to stay. Or does it?</p><p>In this article, we examine whether foldable phones are the future of mobile technology and how that impacts app developers. But a quick note before we start. Throughout this piece, we use the term flip phones to refer to both flip and fold phones. We recognise there is a difference but the base technology is largely the same and we feel comfortable bracketing them together for convenience’s sake.</p><h3>2026 update — from experiment to an established category</h3><p>Fast forward to today, and the foldable conversation has quietly shifted. What once felt like a bold experiment has now become an established part of the smartphone market, with manufacturers investing in different form factors and users becoming increasingly familiar with the idea of a device that can change shape. That changes the conversation for product teams, too. Foldables are no longer something to design around if they eventually become popular enough. They are part of the wider range of screen sizes and shapes that a modern app needs to be prepared for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*hyXtrdnYQSSswpnK" /></figure><p>Samsung, in particular, has doubled down on its commitment to foldables. The Galaxy Z Flip and Z Fold ranges are no longer framed as futuristic novelties, but as refined, repeatable upgrades that sit comfortably alongside its flagship devices.</p><p>Each iteration has focused less on proving the concept and more on improving durability, battery life, camera quality and software polish — all signs of a manufacturer playing the long game rather than chasing headlines.</p><h3>Are foldable phones the future?</h3><p>The question has changed. It is no longer simply whether foldables will become the future of mobile technology. They have already had enough influence on the market that product teams need to consider what they mean for the products being built today.</p><p>That does not mean every business needs to redesign its app specifically around a foldable device. Adoption will vary by market, audience and use case. But it does mean treating foldables as a temporary phase or an edge case is becoming harder to justify.</p><p>For developers, the more useful question is what happens when a device can move between very different screen configurations. A product designed responsively from the outset can adapt to those changes much more naturally, while one built around fixed layouts may require significant redesign as new form factors appear.</p><h3>There are hidden industry dynamics at play</h3><p>Though it would be nice to think that the technology industry is perfectly meritocratic and the best, most useful products always rise to the top, it is simply not the case. Technological evolution depends on adoption. Adoption is determined by a range of other forces, many of them market-based.</p><p>Which brings us on to market forces, foldable phones and the giant elephant in the room. Apple. The company with the second-largest smartphone market share — a company renowned for its trendsetting, industry-defining technology — is yet to produce a foldable phone. That is not to say they won’t. There are rumours that Apple is scheduling a foldable phone release for 2024–2025, but the company does not comment on upcoming technology, so we have no way of knowing if that is true.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*XZR53EzXiTm7Dbpb" /></figure><h3>2026 update — Apple has finally entered the foldable market</h3><p>Well, the rumours can finally be put to bed. In September 2026, Apple officially unveiled the iPhone Duo, its first ever foldable iPhone and one of the biggest changes to the iPhone’s design since the original was launched in 2007.</p><p>That makes this a particularly interesting moment for foldable technology. For years, Samsung, Huawei, Xiaomi, Motorola and others have been trying to prove that folding screens have a genuine place in the smartphone market. Apple has now made its position clear: foldables are no longer something happening around the edges of the smartphone industry. They are part of the iPhone ecosystem.</p><p>The iPhone Duo takes a slightly different approach to the category, opening to reveal a 7.6-inch display while retaining a 5.4-inch outer screen when folded. Apple says both displays share the same aspect ratio, allowing content to scale proportionally between them, while iOS 27 has been redesigned to adapt to the different ways the device can be held and used.</p><p>And that last point is perhaps more important than the hardware itself.</p><p>Apple isn’t simply putting a folding screen onto an existing iPhone. The company has designed the hardware and software together, with the foldable format creating new opportunities for multitasking, gaming, photography, video calls and hands-free use. The camera experience, for example, makes use of the outer display in ways that aren’t possible on a traditional iPhone, while the larger inner display gives apps considerably more room to work with.</p><p>For product teams, this also makes responsive design a priority rather than an assumption. A book-style foldable can introduce a large, square or near-square working area that looks and behaves very differently from the tall, narrow screens most mobile interfaces have traditionally been designed around.</p><p>That has implications beyond simply making an interface fit. Navigation may need to change position, content may need to reflow, controls may need to become more accessible across a wider layout and components that work well in a portrait phone view may suddenly have much more space around them. Designing these behaviours from the beginning is far easier than trying to retrofit them once a product is already in development.</p><p>The arrival of a foldable iPhone therefore makes one thing particularly clear: responsive design can no longer be treated as making a desktop layout shrink down to mobile, or making an existing mobile interface stretch when a larger screen appears. It needs to account for the possibility that the shape and context of the screen itself can change.</p><p>For app developers, this makes Apple’s entry particularly significant. Until now, supporting foldables could reasonably be viewed as a decision based on the size of the Android foldable audience. With Apple now introducing its own interpretation of the format, product teams have another major ecosystem to consider, along with another set of screen sizes, orientations and interaction patterns.</p><h3>A strategic attempt to change the rules of the game?</h3><p>If you think we are overstating the importance of market dynamics in determining foldable technology’s success, think again. Conor Pierce, head of Samsung’s UK Mobile Division, stated explicitly that their foldable phones are a deliberate attempt to shake up the industry and erode Apple’s influence.</p><p>At the moment, people view smartphone technology through the prism of Apple vs <em>the others</em>. To counter this, Samsung wants to shift the discourse away from operating systems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*6JCfBil4arYwNY7O" /></figure><blockquote><strong>“What we want to try to do is disrupt and change the game when it comes to an OS conversation. When you walk into a store, ‘do you want a folding phone or do you want a flat phone?’ should be the first question you’re asked”</strong></blockquote><blockquote><a href="https://www.theguardian.com/technology/2021/sep/01/foldable-phone-techscape"><strong><em>Conor Pierce, in The Guardian</em></strong></a></blockquote><p>Marketing is another force at play in the foldable phone debate. When originally released, several designs (most notably the Motorola Razr) appeared to rely heavily on the nostalgia vibe. For some companies, emerging foldable technology seemed like a way to make money off a renewed interest in the light-hearted innocence of the pre-internet nineties and early noughties. Bucket hats, CDs, reboots of questionable ’90s TV shows and clamshell phones are all back in. Didn’t you know?</p><p>This gave some credibility to the idea that foldable technology was a bit of a gimmick. Three years on, this theory does not hold up well. The big tech players are investing heavily in foldable and adoption is on the rise. If it was a gimmick at the start, it certainly is not now.</p><h3>2026 update — Beyond Samsung is a crowded, competitive foldable landscape</h3><p>Samsung may have led the charge, but the foldable market has now become a genuinely competitive space. Huawei, Xiaomi, Motorola, Google and, most significantly, Apple have all developed their own interpretations of what a foldable phone should be.</p><p>This growing diversity is important. It suggests that foldables are no longer being developed around a single dominant vision. Instead, manufacturers are testing different assumptions about how people actually want to use these devices. Do users want a compact phone that unfolds occasionally, or a tablet-like screen they access multiple times a day? Is the outer screen a convenience feature, or a fully functional interface in its own right?</p><p>As competition increases, so does pressure on software and user experience. Hardware innovation can only go so far on its own. The real differentiator is increasingly how well the device integrates with apps, services and daily workflows — which brings the conversation back, once again, to developers.</p><h3>What do foldable phones mean for app developers?</h3><p>The other key issue for foldable phones is app development. On the first release, app compatibility was one of the biggest complaints. Apps were not designed for this new type of device and a considerable number did not perform well. Some did not fit the screen, others did not function as they should and many were simply not available for download on foldable phones.</p><p>While those early teething problems have eased, they are not entirely gone. Foldable phones still pose several challenges for app developers. These include:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*2wcbOgyBeWKDk1Fx" /></figure><h3>Aspect ratio</h3><p>For years, mobile app design has largely been built around tall portrait screens, with landscape layouts added where necessary. Foldables have changed that assumption. Different devices can introduce dramatically different aspect ratios, and book-style foldables can move between a conventional phone display and a much larger, square or near-square screen.</p><p>This means responsive and adaptive design needs to be considered at the beginning of a project, rather than treated as something to address if a particular foldable becomes popular. Layouts need to respond to significant changes in available space without making the interface feel stretched, empty or difficult to navigate.</p><p>Square and near-square screens are particularly important because they can expose assumptions that are easy to make when designing for a conventional phone. A layout that feels natural on a tall portrait screen may suddenly have too much horizontal space, while navigation and content hierarchies can become awkward if they simply expand without being reconsidered.</p><p>The answer isn’t to create a separate version of an app for every possible device. It is to build flexible layouts and components that can respond intelligently to different dimensions and states.</p><h3>Resizeable apps</h3><p>Just as important is app continuity — how apps transition from one aspect ratio to another. Developers need to ensure that this transition feels natural and does not suffer from lag or bugs.</p><h3>Multi-window for multitasking</h3><p>A bigger screen size means there is more scope for multi-window multitasking. Browsing your photos on one part of the screen while typing a message on the other, for instance. Running multiple apps at the same time has the potential to radically alter the way we interact with our devices and how apps interact with one another. Developers will have to factor in new actions and gestures (such as <em>drag and drop</em>) to accommodate these capabilities.</p><h3>Foldable states</h3><p>Foldable phones also open up the possibility of a whole range of new display ‘states.’ With non-foldable models, there are two principal states. Portrait and landscape. But flip phones can be <em>folded</em>, <em>open</em>, or <em>half-open</em>. Apps may behave differently in each state.</p><p>When <em>half-open</em>, the top screen could be a chat interface and the bottom a keyboard, resulting in a display that resembles a traditional laptop setup. When <em>open</em>, the keyboard may take up less space, allowing for easier multitasking.</p><p>Secondary screens are typically included on the exterior of foldable phones to display notifications and other information, ensuring users don’t always have to open the device. These screens present another whole range of challenges and possibilities. What information should they include? How can they be used to streamline and simplify the user experience?</p><p>This is perhaps where foldable phones show the most potential. Whether app developers can take advantage of these capabilities may also determine how successful the technology is.</p><h3>2026 update — Why foldables should now influence product design</h3><p>When foldables first re-emerged, many product teams quite reasonably chose to wait and see. Supporting them felt like a future problem, something to revisit once adoption reached a meaningful level.</p><p>That approach is becoming less useful. More major manufacturers are committing to different versions of the format, and Apple has now brought the book-style foldable into the iPhone ecosystem.</p><p>For product teams, the practical takeaway isn’t that every app needs a dedicated foldable experience. It’s that responsive design needs to account for a much wider range of screen configurations from the beginning, particularly square and near-square layouts.</p><p>The same principles also make products better prepared for tablets, larger phones and whatever form factors emerge next. Foldables are therefore less about designing for one particular device and more about avoiding an app architecture that assumes tomorrow’s screens will look exactly like today’s.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*otgO-aM_5PV52QrU" /></figure><h3>2026 — Foldables are changing how we design</h3><p>Foldables have become more than a question of whether people will eventually replace their traditional smartphones. They have changed the assumptions we make about what a mobile device looks like, how much space an app has to work with and how users move between different ways of interacting with a product.</p><p>The arrival of the iPhone Duo makes that shift particularly difficult for product teams to ignore. Foldables are now represented across the major smartphone ecosystems, while book-style devices introduce screen configurations that are very different from the tall portrait displays that have dominated mobile design.</p><p>That doesn’t mean every app needs a bespoke foldable experience. It does mean responsive and adaptive design should be considered from the beginning of a project, particularly when thinking about square and near-square layouts.</p><p>Foldables may or may not become the dominant smartphone format. We don’t need to predict that to know they’re already influencing how digital products should be designed.</p><p>If you’re looking to create a foldable-friendly app for your business, The Distance can help.</p><p><a href="https://thedistance.co.uk/contact-us">Chat to one of our experienced team members today!</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f8d36f006a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What will the next generation of apps look like?]]></title>
            <link>https://medium.com/@TheDistance/what-will-the-next-generation-of-apps-look-like-2c63614f0d40?source=rss-733ae949c85b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c63614f0d40</guid>
            <category><![CDATA[app-building]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[mobile-application]]></category>
            <category><![CDATA[mobile-apps]]></category>
            <category><![CDATA[apps]]></category>
            <dc:creator><![CDATA[The Distance]]></dc:creator>
            <pubDate>Wed, 16 Sep 2026 12:00:19 GMT</pubDate>
            <atom:updated>2026-09-16T12:00:19.893Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>For years, when we talked about building an app, there was a fairly simple picture in our heads. You downloaded it from the App Store, opened it on your phone, tapped your way through a few screens and eventually got to whatever it was you actually wanted to do.</strong></p><p>Maybe you booked a train, checked your bank balance, ordered some food, tracked your fitness or bought a pair of shoes. The app was the destination, and the interface was the route you took to get there. That model has served us pretty well.</p><p>But something interesting is happening now. The way we interact with technology is starting to change, and it is happening much faster than the traditional app model was designed for.</p><p>Instead of opening an app to find something, we can ask an assistant to find it for us. Instead of navigating through five screens to complete a task, an AI agent can potentially do it on our behalf. Instead of looking at a phone, we might speak to a device in our ear, glance at information through smart glasses or interact with technology through a watch.</p><p>The technology is changing, but perhaps the bigger change is happening somewhere else: <strong>our expectations are changing too.</strong></p><p>In the UK, <a href="https://www.gov.uk/government/statistics/dsit-public-engagement-survey-20252026/dsit-public-engagement-survey-20252026">54% of adults reported using an AI-powered digital assistant that understands natural language</a> within the previous three months in the UK. Meanwhile, 56% had used AI that creates human-like text or speech in response to queries.</p><p>That matters because once people become comfortable saying, “Can you find me a cheaper train tomorrow?” or “Remind me what I need to take on holiday,” it becomes harder to convince them that they should go back to navigating a traditional interface just to achieve the same thing.</p><p>So, what does that mean for the apps we build today?</p><p>The short answer is that the next generation of apps probably won’t look like apps in the way we’re used to thinking about them.</p><p>And that doesn’t mean the traditional mobile app is disappearing tomorrow, far from it. It means we’re entering a world where the app becomes part of a much bigger product experience, one that can move between conversation, voice, automation, wearable technology, contextual experiences and traditional screens depending on what the user needs at that particular moment.</p><p>Let’s explore what that could look like.</p><h3>The app is no longer necessarily the destination</h3><p>One of the biggest shifts we’re seeing is a move away from the idea that a user needs to open your app to access your product. For years, the goal for product teams has often been to get people into the app. We measure downloads, active users, sessions, retention and engagement because the assumption is that if people are opening the app, they’re using the product.</p><p>But what if the best experience doesn’t require them to open it at all? Imagine you are running late for a train. Today, you might open your rail app, search for your journey, check the platform, look at delays and perhaps buy a ticket. There are multiple interactions involved, even though your actual goal is relatively simple: <strong>get me where I’m going.</strong></p><p>Now imagine saying: “What’s the quickest way for me to get to London tomorrow morning?”</p><p>An assistant understands where you are, knows the time, checks available services, considers your preferences and presents the best options. You choose one, and the assistant handles the booking.</p><p>The underlying rail app may still exist. Its booking system, customer account, payment infrastructure and journey data are all still incredibly important. But the user might never have opened it. That’s a significant change in the role of an app.</p><p>We’re already seeing technology platforms move in this direction. In February 2026, Google described a new Android model where <a href="https://developer.android.com/blog/posts/the-intelligent-os-making-ai-agents-more-helpful-for-android-apps">users can delegate multi-step tasks to Gemini</a>, allowing the assistant to interact with supported apps on their behalf. The examples include ordering food, coordinating a multi-stop rideshare and reordering groceries.</p><p>Google describes the shift quite clearly: success is increasingly about <strong>fulfilling the user’s task</strong>, rather than simply getting them to open an app. That is a pretty fundamental change in product thinking. And it is something product owners should be paying attention to now.</p><h3>Conversational interfaces will become another front door</h3><p>We’ve spent decades designing graphical interfaces around menus, buttons, tabs, forms and navigation. They’re not going anywhere, but conversation gives us another way into a product. The difference is that conversation allows people to explain what they want rather than having to understand how the product works.</p><p>Think about the difference between these two experiences.</p><p><strong>Traditional:</strong></p><p>Open app → search → select category → apply filters → choose item → check availability → book.</p><p><strong>Conversational:</strong></p><p>“I need somewhere to stay in Manchester next Friday, close to the city centre, and I’d like somewhere with parking.”</p><p>The second interaction doesn’t require the user to know where the filters are, what terminology the product uses or which sequence of screens they need to follow. That’s incredibly powerful, but it also introduces a challenge. A conversational interface isn’t simply a chatbot bolted onto an existing app. If you approach it that way, you can very quickly end up with a chat window that technically works but doesn’t actually improve the experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*ecFOIvGB-iMOvzQr" /></figure><p>The interesting opportunity is to rethink <strong>how people achieve outcomes</strong>. A conversation can become the starting point, with traditional UI appearing when it is useful.</p><ul><li>Perhaps the user asks for a holiday… the assistant asks a couple of questions, searches options and then presents a visual selection of hotels.</li><li>Perhaps they want to make a payment… the conversation establishes what they want, but the final transaction is presented as a clear confirmation screen.</li><li>Perhaps they’re comparing insurance policies… the assistant explains the differences conversationally, but a structured comparison makes the final decision easier.</li></ul><p>This is where we think the next generation of interfaces becomes particularly interesting. <strong>The future isn’t necessarily chat instead of UI. It’s conversation and UI working together.</strong></p><p>OpenAI’s introduction of apps inside ChatGPT is an early example of this model. Apps can respond to natural language while also providing interactive interfaces such as maps, playlists and other visual components within the conversation. That gives us a useful glimpse into where things could be heading.</p><h3>AI agents will move from answering to doing</h3><p>There’s an important distinction between an AI assistant and an AI agent. An assistant might tell you what you should do. An agent can potentially <strong>do it for you</strong>. That difference is going to have a huge impact on digital products.</p><p>Imagine asking an assistant: “Can you find me the cheapest flight to Barcelona next month?” That’s useful.</p><p>Now imagine it can search flights, compare options against your preferences, check your calendar, identify suitable dates, make the booking, add it to your calendar and send you the confirmation. That’s a very different product experience. The interface has effectively moved from <strong>interaction</strong> to <strong>delegation</strong>.</p><p>Instead of giving someone a tool and asking them to complete a workflow, you’re giving them a system that can complete the workflow on their behalf. This is why the rise of agentic AI deserves attention from anyone building an app.</p><p>Gartner predicts that by 2028, <a href="https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027"><strong>33% of enterprise software applications will include agentic AI capabilities</strong></a>, compared with less than 1% in 2024. It also predicts that at least 15% of day-to-day work decisions will be made autonomously through agentic AI by 2028.</p><p>And Gartner has gone even further in its 2026 research, estimating that up to <a href="https://www.gartner.com/en/newsroom/press-releases/2026-07-01-gartner-says-us-dollars-234-billion-in-enterprise-application-software-spend-is-at-risk-from-agentic-artificial-intelligence"><strong>$234 billion of enterprise application spending could be exposed to agentic AI between now and 2030</strong></a>, because agents can complete tasks across multiple systems without users needing to interact with every individual application.</p><p>That’s not a prediction that every app is going to disappear. It’s a prediction that the relationship between the user and the app is going to change. For product owners, that raises a much more useful question than “Should we add AI?” The question becomes:</p><p><strong>Which parts of our product should a person continue doing themselves, and which parts could a trusted agent do for them?</strong></p><p>That’s a product strategy question, not a technology question.</p><h3>Your app might become something other products interact with</h3><p>This is one of the more subtle consequences of the agentic shift. Traditionally, you build an app for a person. Increasingly, you may need to build a product that can be used by both <strong>people and other software</strong>.</p><p>Imagine a hotel app. A person can open it and search for rooms, or an AI assistant could interact with the hotel’s booking capabilities directly. The same underlying system needs to support both. That means APIs, authentication, permissions, structured data and clearly defined actions become even more important.</p><p>Your product needs to be understandable not just to a human looking at a screen, but to systems trying to determine:</p><ul><li>What can this product do?</li><li>What information is available?</li><li>What actions can I take?</li><li>What requires permission?</li><li>What requires confirmation?</li><li>What happens if something goes wrong?</li></ul><p>We’re already seeing technology companies build the infrastructure for this. OpenAI’s agent tooling, for example, includes capabilities around tools, orchestration, handoffs, guardrails and observability.</p><p>Android is also exploring ways for apps to expose capabilities to AI assistants, allowing users to delegate tasks rather than manually navigate through the app themselves.</p><p>This suggests something important for product teams: <strong>Your backend and integrations may become just as important as your interface. </strong>The UI is still important, but it is no longer the whole product.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*_M2J9kJFciD0iHVS" /></figure><h3>Voice will become more natural</h3><p>Voice interfaces have been around for years. Siri, Alexa and Google Assistant have already taught people that they can speak to technology, but anyone who has used an early voice assistant knows the limitations.</p><p>You had to learn the right commands. You had to phrase things in a particular way. And when the system misunderstood you, you often ended up repeating yourself in increasingly robotic language. That isn’t how people naturally communicate. The next generation of voice interfaces is different because AI can understand context, intent and more natural language.</p><p>In the UK, around <a href="https://wearesocial.com/wp-content/uploads/2025/10/GDR-2026.pdf"><strong>26.7% of internet users aged 16 and over were using voice assistants each week in Q2 2025</strong></a>. YouGov also found in January 2025 that <a href="https://yougov.com/en-gb/articles/51221-30-of-brits-use-digital-assistants-daily-heres-what-theyre-doing"><strong>30% of British adults use digital assistants at least once a day</strong></a>.</p><p>So voice isn’t some futuristic interaction waiting to arrive. People are already using it. What’s changing is what they expect it to be capable of. Instead of: “Set a timer for ten minutes.” We’re moving towards: “I’ve got a meeting in ten minutes. Remind me to take the documents with me when I leave.” Or: “Find me a restaurant nearby that can fit six people at 7pm and has good vegetarian options.”</p><p>The technology has to understand intent rather than simply recognise words. For app designers, that means thinking about voice as more than an accessibility feature or an alternative input method. It can become an entirely different way of navigating a product. And voice is particularly interesting when it leaves the phone.</p><h3>The phone won’t always be where the experience happens</h3><p>The smartphone has been the centre of our digital lives for a long time. But we’re increasingly surrounded by devices that can provide parts of the experience without requiring us to pull out our phones, such as:</p><ul><li>Smartwatches</li><li>Wireless earbuds</li><li>Smart rings</li><li>Smart glasses</li><li>Cars</li><li>Home devices</li><li>Headsets</li><li>The growth of wearables is worth watching here</li></ul><p>IDC reported that <a href="https://www.idc.com/promo/wearablevendor/?source=content_type%3Areact%7Cfirst_level_url%3Aarticle%7Csection%3Amain_content%7Cbutton%3Abody_link"><strong>145.7 million wearable devices shipped globally in Q1 2026</strong></a>, up 4.3% year-on-year. It forecasts 2026 smart glasses shipments of 13.6 million, representing 41.4% growth, while smart rings are forecast to grow 12.8%.</p><p>Even more strikingly, IDC reported that display-less smart glasses shipments grew <strong>167% year-on-year in Q1 2026</strong>.</p><p>That doesn’t mean everyone will be wearing AI glasses next year. But it does tell us something important: <strong>the number of places where a digital experience can exist is expanding. </strong>And that creates a very different design challenge.</p><p>Instead of designing one interface for one screen, we’re designing an experience that might move between several devices.</p><h3>The best interface might depend on the situation</h3><p>Imagine you’re using a travel app. When you’re sitting at home planning a holiday, you might want a full-screen interface with photos, maps, prices and detailed information. When you’re walking through an airport, you might want a simple notification: “Your gate has changed to 24.”</p><p>When you’re carrying luggage through the terminal, you might want spoken directions through your earbuds. When you’re boarding the aircraft, you might want your boarding pass on your watch. And when you arrive, perhaps your smart glasses provide walking directions without requiring you to hold your phone up in front of you.</p><p>It’s the same product. It’s the same journey. But the interface changes depending on <strong>where you are, what you’re doing and what information you need at that moment.</strong></p><p>This is what we mean when we talk about contextual experiences. The technology doesn’t simply respond to what the user asks. It understands something about the situation around the request.</p><p>Apple is already building towards this type of experience across its ecosystem. Its current developer platform describes Apple Intelligence as being able to understand personal context, perform app actions and understand what is happening on screen across devices including iPhone, iPad, Mac, Apple Watch and Apple Vision Pro.</p><p>That’s a significant shift in how we think about interaction. The user doesn’t necessarily need to think: “I need to open the app.” The system can surface the right part of the experience when it becomes relevant.</p><h3>This is where wearable technology gets really interesting</h3><p>Wearables aren’t simply smaller phones. Trying to squeeze your existing mobile app onto a watch or pair of glasses usually misses the point. The opportunity is to ask: <strong>What is the smallest amount of information or interaction someone needs right now?</strong></p><p>A smartwatch might not need your entire banking app. It might just need to tell you that a payment has been received. Your fitness app might not need to show you every chart while you’re running. It might simply need to tell you: “You’re on track for your target pace.”</p><p>Your travel app might not need to show the whole airport map. It might need to say: “Turn left in 30 metres.”</p><p>That sounds simple, but designing these experiences well requires a deeper understanding of the user’s context. It’s not about putting more features onto more devices. It’s about deciding <strong>where each part of the experience belongs.</strong></p><h3>Spatial computing will change what an interface can be</h3><p>Then there is spatial computing. It’s still early, and we’re certainly not suggesting that every product owner should rush out and build a 3D version of their app. But the technology is opening up some fascinating possibilities.</p><p>Apple’s visionOS platform allows developers to combine traditional windows with 3D volumes and fully immersive spaces, while using technologies such as RealityKit and ARKit to understand the user’s physical surroundings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*2z76AwxHgqjGJA-t" /></figure><p>That changes the fundamental relationship between the interface and the physical world. Imagine:</p><ul><li>An interior design app that lets you place furniture in your actual room</li><li>A training application that puts a virtual instructor into your physical environment</li><li>A maintenance application that overlays instructions directly onto a piece of machinery</li><li>A property application that lets you explore a building before visiting it</li><li>A medical training platform that turns a three-dimensional model into something you can actually interact with</li></ul><p>These experiences aren’t simply “mobile apps with 3D graphics”. They are different ways of understanding information. And that’s the important distinction. New technology doesn’t automatically create a better product. It becomes valuable when it allows you to do something that was previously difficult, confusing or impossible.</p><h3>The next generation of apps will probably be multimodal</h3><p>If the first generation of digital interfaces was largely visual, and the second added touch, the next generation is going to be much more comfortable combining different types of interaction:</p><ol><li>You might speak to an app.</li><li>It might show you something.</li><li>You might point your camera at something.</li><li>It might understand what you’re looking at.</li><li>You might type a question.</li><li>It might search your data.</li><li>You might receive a notification.</li><li>You might respond by voice.</li><li>You might then complete the final action on a traditional screen.</li></ol><p>The boundaries between these interactions become much less important. Google’s Gemini experience already demonstrates some of this direction, including the ability to ask questions about what’s on your screen, understand images and take actions using voice.</p><p>This is why we’re increasingly thinking about <strong>experiences rather than interfaces</strong>. An interface is one way of interacting with a product, and an experience is everything that happens around it. That distinction is going to matter enormously over the next few years.</p><h3>Cross-platform will mean more than iOS and Android</h3><p>When we say “cross-platform” today, we often mean building an application that works across iOS and Android. That’s still important, but the definition is expanding. A genuinely cross-platform product of the future might include:</p><ul><li>A mobile application</li><li>A web application</li><li>A conversational interface</li><li>Voice interactions</li><li>AI agents</li><li>Wearable experiences</li><li>Notifications</li><li>Smart glasses</li><li>In-car experiences</li><li>Integrations with other platforms</li><li>APIs that other AI systems can interact with</li></ul><p>Suddenly, the question isn’t: “Should we build an iOS app or an Android app?” It’s: <strong>“Where should our product exist?” </strong>And the answer shouldn’t be “everywhere”. That’s an easy trap to fall into.</p><p>You don’t need to build for every new device simply because the technology exists. The right approach is to understand where your users are, what they’re trying to achieve and which interaction makes that journey easier. For some products, that will still be a brilliant mobile app. For others, the most valuable experience might be an AI agent. For some, it might be a combination of mobile, web and wearable.</p><p>And for a smaller number of products, spatial computing might genuinely unlock something that couldn’t be achieved before. The technology should follow the problem, not the other way around.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*KmiVqv2AFeLjXOJd" /></figure><h3>The interface might become invisible</h3><p>This is perhaps the most interesting possibility of all. What happens when technology becomes so good at anticipating and completing tasks that we stop thinking about the interface?</p><p>Consider a simple example…</p><p>You leave work every evening at roughly the same time. Your system knows you’re heading home, notices that traffic is heavier than usual and suggests an alternative route. You don’t open an app. You don’t search for directions. You don’t even necessarily ask for anything.</p><p>The technology simply provides the information when it is useful. That’s a very different relationship with software. And it’s why we’re starting to talk about ideas such as <a href="https://thedistance.co.uk/insights/whitepapers/invisible-ui"><strong>Invisible UI</strong></a> or <strong>Zero UI</strong>.</p><p>The interface hasn’t disappeared because the technology no longer needs one. It has disappeared because the technology has found a better way to fit into the user’s life. Of course, this creates a delicate balance. If technology becomes too proactive, it can become annoying. If it makes decisions without explaining itself, it can become frustrating. And if it starts taking actions that users didn’t expect, trust can disappear very quickly.</p><p>So invisible doesn’t mean unaccountable. In fact, the opposite is true. The less visible an interface becomes, the more important trust, transparency, permissions and control become.</p><h3>Privacy and security become part of the experience</h3><p>There’s another side to all of this that product owners can’t afford to overlook. The more context your product understands, the more sensitive that context can become. An app that knows what you bought is one thing. An assistant that knows where you are, what you’re saying, what’s on your screen, what’s in your calendar and what you’re trying to achieve is something else entirely. And an AI agent that can take action using that information introduces another layer of risk.</p><p>The industry is already seeing concerns emerge around this.</p><p>Gartner predicts that by 2028, <a href="https://www.gartner.com/en/newsroom/press-releases/2026-04-09-gartner-predicts-25-percent-of-all-enterprise-gen-ai-applications-will-experience-at-least-five-minor-security-incidents-per-year-by-2028"><strong>25% of enterprise generative AI applications will experience at least five minor security incidents per year</strong></a>, compared with 9% in 2025. It specifically highlights the new attack surface created by agentic applications and technologies such as MCP. That doesn’t mean AI agents are inherently unsafe.</p><p>It means we’re asking software to do more, which means our approach to security needs to evolve alongside it. A traditional app might need to protect a user’s account and data. An agentic product also needs to consider:</p><ul><li>What is the agent allowed to do?</li><li>What information can it access?</li><li>When should it ask for confirmation?</li><li>How does the user know what it has done?</li><li>What happens if it makes the wrong decision?</li><li>Can the user undo it?</li></ul><p>These aren’t purely technical questions… they’re UX questions, they’re product questions and increasingly, they’re business questions.</p><h3>Trust will become one of the most important features</h3><p>When a user taps a button, they generally understand what they’re doing. When an AI makes a decision for them, the relationship is different. That’s why the next generation of products will need to be particularly good at communicating confidence, uncertainty and control.</p><p>Imagine an AI travel agent saying: “I’ve found three hotels that match your preferences. The first is £40 cheaper, but it’s 20 minutes further from the city centre.”</p><p>That’s useful. Compare it with: “I’ve booked the cheapest hotel.”</p><p>The second might be technically efficient, but it’s not necessarily what the user wanted. The best agentic experiences will understand when to act autonomously and when to involve the person. Sometimes the user should say yes, sometimes they should be able to review, sometimes they should be able to set rules in advance, and sometimes the system should simply provide information and leave the decision to them.</p><p>The technology might be capable of doing more, but good product design means knowing <strong>when it should</strong>.</p><h3>So, what does this mean if you’re building an app today?</h3><p>This is probably the <strong>most important</strong> question. Because it’s very easy to read about AI agents, smart glasses, spatial computing and voice interfaces and come away thinking: “Should we be rebuilding our entire product?”</p><p>And the answer is, probably not.</p><p>The biggest mistake product owners can make is trying to predict the future by adding every new technology to their roadmap. Instead, start with the experience. Ask yourself what your customers are actually trying to achieve:</p><ul><li>Where are the points of friction?</li><li>Which tasks are repetitive?</li><li>Which interactions require too much navigation?</li><li>Where are people already using voice or AI to work around your product?</li><li>Which information would be useful to surface proactively?</li><li>Which decisions could be supported by better context?</li><li>And which parts of the experience genuinely benefit from being automated?</li></ul><p>Those questions will tell you much more than simply asking whether your product needs an AI chatbot.</p><h3>Start designing the product, not just the app</h3><p>This is where our thinking around product development becomes particularly important. When we work on an app, we’re not just thinking about what screens need to be designed or what features need to be developed. We’re looking at the wider journey…</p><ul><li>What problem are we solving?</li><li>Who are we solving it for?</li><li>What does the user need to accomplish?</li><li>What happens before they use the product?</li><li>What happens afterwards?</li><li>What systems does the product need to connect to?</li><li>What data does it need?</li></ul><p>And, increasingly, <strong>what is the best way for someone to interact with it? </strong>Sometimes the answer will still be a mobile app. Sometimes it’ll be a web application, sometimes it’ll be an AI-powered feature within the existing experience and increasingly, it may be a combination of all of them.</p><p>This is why product strategy matters so much. You don’t want to build something that looks impressive today but forces you into a complete rebuild every time the way people interact with technology changes. You want to create a product with a strong enough foundation that you can evolve the experience as technology and user behaviour evolve.</p><h3>Build the foundations before chasing the future</h3><p>There’s a temptation with emerging technology to jump straight into the exciting part:</p><ul><li>Let’s build an agent.</li><li>Let’s add voice.</li><li>Let’s support smart glasses.</li><li>Let’s create a conversational interface.</li></ul><p>But before any of that, you need to know whether your underlying product can support it. That means thinking carefully about your architecture, APIs, data, authentication, integrations and permissions.</p><p>If your systems are fragmented, your data is inaccessible or your key business logic only exists inside a particular interface, creating an AI agent isn’t going to magically solve the problem.</p><p>In fact, it can make it worse. The future-facing product is often built on fairly unglamorous foundations, with things such as good APIs, clear data structures, well-defined business rules, robust authentication, reliable integrations, strong observability, thoughtful permissions, good testing and a scalable architecture.</p><p>None of these things makes for particularly flashy product demos, but they’re what allow you to build the flashy product experiences on top.</p><h3>The next generation won’t replace everything that came before</h3><p>There’s a tendency to talk about new technology as if it completely replaces the old. Web replaced desktop, mobile replaced web, AI will replace apps. We don’t think that’s how it will play out, the reality is usually much more interesting.</p><p>New interfaces are added to the ecosystem, and people use whichever one makes sense in the moment. There are still websites, there are still desktop applications, there are still mobile apps. And there will still be buttons, menus, forms and screens for a very long time.</p><p>The difference is that they’ll exist alongside conversation, voice, agents, wearables and contextual experiences. The winning products won’t necessarily be the ones with the most futuristic technology. They’ll be the ones that <strong>use the right technology at the right moment.</strong></p><h3>So, what will the next generation of apps actually look like?</h3><p>If we had to put it simply, we’d say they will be <strong>less about the app and more about the experience</strong>. They’ll:</p><ul><li>be conversational when conversation is easier</li><li>use voice when speaking makes more sense than typing</li><li>use AI agents when delegation is more useful than manual interaction</li><li>appear on watches, glasses, cars and other devices when the context calls for it</li><li>understand more about what users are trying to achieve</li><li>adapt to the situation rather than expecting users to adapt to the interface.</li></ul><p>And, in some cases, they’ll become almost invisible. But underneath all of that, the fundamentals won’t change. The product still needs to solve a real problem. The experience still needs to make sense. The technology still needs to be reliable. And people still need to trust it.</p><p>That’s perhaps the most important thing to remember when thinking about the future of apps. <strong>The next generation of apps won’t be defined by the technology they use. They’ll be defined by how naturally they fit into people’s lives.</strong></p><p>And for product owners, that creates a really exciting opportunity. You don’t need to predict exactly what technology will exist five years from now. You need to build a product that is capable of evolving with it. Because the future of apps isn’t about choosing between mobile, web, AI, voice or wearables. It’s about creating an experience that can move between them. And that’s where the next chapter of digital product development gets really interesting.</p><h3>Want to build what’s next?</h3><p>The technology landscape is changing quickly, but building a future-ready product isn’t about chasing every new trend. It’s about understanding your users, identifying where technology can genuinely improve their experience and creating the right foundations to evolve as those expectations change.</p><p><strong>If you’ve got an idea for the next generation of digital product, we’d love to explore where it could go.</strong></p><p><a href="https://thedistance.co.uk/contact-us">Start your product journey</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c63614f0d40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How do I know if my app idea is worth investing in?]]></title>
            <link>https://medium.com/@TheDistance/how-do-i-know-if-my-app-idea-is-worth-investing-in-29b992cb8af7?source=rss-733ae949c85b------2</link>
            <guid isPermaLink="false">https://medium.com/p/29b992cb8af7</guid>
            <category><![CDATA[app-development-agency]]></category>
            <category><![CDATA[mobile-app-ideas]]></category>
            <category><![CDATA[app-idea]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[The Distance]]></dc:creator>
            <pubDate>Wed, 02 Sep 2026 08:52:32 GMT</pubDate>
            <atom:updated>2026-09-02T08:52:32.656Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Having an app idea is exciting. You can picture how it will work, imagine people using it, and start thinking about all the features you could include. Maybe you’ve spotted a problem in your own industry, found a gap in the market, or had one of those moments where you think, “Why doesn’t an app already do this?”</strong></p><p>The difficult part comes afterwards.</p><p>Before you invest thousands, tens of thousands, or potentially much more into turning that idea into a real product, how do you know whether it is actually worth pursuing?</p><p>There isn’t a single calculation that can tell you whether an app will succeed. No amount of market research can guarantee that people will download it, use it or pay for it. What you can do, however, is reduce the amount of uncertainty around the idea and build a much clearer picture of whether there is a genuine opportunity there.</p><p>That is something we spend a lot of time helping product owners work through. When someone comes to us with an app idea, our first conversation isn’t usually about which technology to use or how many screens the app needs. We want to understand the problem, the people experiencing it, the alternatives they have today and what success would actually look like for the business.</p><p>Because a good app idea is more than an interesting concept. It needs to solve a meaningful problem for a specific audience, have a reason to exist in a competitive market, be technically and commercially achievable, and ultimately create enough value to justify the investment required to build and grow it.</p><p>So, before you start thinking about development, here are the questions we’d encourage you to ask.</p><h3>Start with the problem, not the app</h3><p>One of the easiest traps to fall into is becoming attached to the solution before you have properly understood the problem. You might have a clear idea of what your app should do, but that doesn’t necessarily mean you have identified a problem people genuinely want solved.</p><p>Imagine you have an idea for an app that helps independent tradespeople manage their jobs, customers and invoices. At first glance, that sounds useful. But “an app for tradespeople” is a solution description, not a problem statement. The more important question is what is actually going wrong today.</p><p>Are tradespeople losing work because they struggle to respond to enquiries quickly? Are they spending hours every week organising appointments? Are invoices being forgotten? Are customers frustrated because they don’t know when someone is arriving? Are existing tools too complicated, too expensive or designed for larger businesses?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*psc-YCEOj5Pd50ao" /></figure><p>The answers lead you somewhere much more useful.</p><p>A strong product opportunity usually starts with a problem that is frequent enough, painful enough or valuable enough for someone to want to change the way they currently do things.</p><p>That distinction matters because the latest data from CB Insights reinforces just how important product-market fit is. Its 2026 analysis of 431 VC-backed companies that shut down found poor product-market fit was cited in 43% of failures. Interestingly, <a href="https://www.cbinsights.com/research/report/startup-failure-reasons-top/">running out of capital appeared in 70% of failures</a>, but CB Insights describes this as often being the final consequence rather than the underlying problem.</p><p>In other words, spending more money isn’t necessarily going to rescue an idea that people don’t actually need.</p><p><strong>Ask yourself:</strong></p><ul><li>What specific problem am I solving?</li><li>Who experiences that problem?</li><li>How often does it happen?</li><li>How frustrating, expensive or time-consuming is it?</li><li>What happens if the problem isn’t solved?</li><li>How are people dealing with it today?</li><li>Why would they change what they are currently doing?</li></ul><p>If you can answer those questions clearly, you’re already in a much stronger position than someone who has simply started with a list of features.</p><h3>Find out who actually needs it</h3><p>The next question is deceptively simple: who is this app for? “We’re targeting everyone” might sound like a great business opportunity, but it makes it incredibly difficult to build a product that genuinely works for anyone.</p><p>Different people have different needs, expectations and reasons for using an app. A product designed for a busy parent booking children’s activities will need to solve a very different problem from one designed for a logistics manager managing a fleet of vehicles, even if both involve booking and scheduling.</p><p>We often encourage product owners to think about their audience in terms of the people who experience the problem most frequently and most severely.</p><p>That group is usually much more valuable to understand than a huge theoretical audience. Start talking to them. Ask them things like:</p><ul><li>How they currently deal with the problem</li><li>What they find frustrating</li><li>What they have already tried</li><li>What they pay for today</li><li>What would make them switch</li></ul><p>Most importantly, listen to what they actually do rather than simply asking whether they like your idea.</p><p>There is a big difference between someone saying, “That sounds like a great idea,” and someone saying, “I have this problem every week, I currently spend £200 a month trying to solve it, and I would switch if you could do this.” The second conversation gives you something you can work with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*P6XdHX7k6B3hvXJg" /></figure><h3>Look for evidence of demand</h3><p>Once you understand the problem and the audience, you need to establish whether there is enough demand to make the opportunity worthwhile. This doesn’t necessarily mean you need a huge market. A niche product can be an excellent business if the problem is valuable and the economics work.</p><p>What you need is evidence that the problem exists beyond your own experience or a handful of people you know. There are several ways to look for that evidence.</p><p>Search for conversations around the problem. Look at Reddit discussions, industry forums, social media, reviews of competing products and customer complaints. Speak to potential users directly. Look at search behaviour where relevant. Investigate industry reports and market data. If it is a B2B product, speak to people who actually make purchasing decisions.</p><p>You are looking for patterns.</p><p>If ten people independently describe the same frustration, that’s interesting. If fifty people describe it and are already paying for an imperfect solution, that’s considerably more interesting.</p><p>Existing behaviour is particularly useful here. People already spending time or money trying to solve a problem are giving you a signal that the problem has some value.</p><p>And remember that the app market itself is enormous, but that doesn’t mean every idea has an easy route to users. Apple’s latest App Store Transparency Report lists <a href="https://www.apple.com/legal/app-store/transparency/2025/">more than 2.17 million apps on the App Store</a>, alongside an average of more than 929 million weekly app downloads.</p><p>There is clearly an enormous appetite for apps. There is also an enormous amount of competition for people’s attention. That is why “there is a market for apps” isn’t enough evidence. You need to understand whether there is a market for <em>your particular product</em>.</p><h3>Research the competition properly</h3><p>Finding competitors can feel like bad news when you’ve spent months developing an idea. In reality, competition can be one of the most useful signals you have. If someone has already built something similar, it proves that other people have recognised the problem too.</p><p>The question is whether there is room for another solution. Start by identifying your direct competitors, but don’t stop there. Your biggest competitor might not be another app, it could be:</p><ul><li>a spreadsheet</li><li>an email</li><li>a WhatsApp</li><li>a paper form sitting on someone’s desk</li><li>a process involving three different systems and a member of staff spending half a day putting information together manually</li></ul><p>These alternatives tell you a lot about what your product needs to replace or improve. Then look at what existing products do well and where they fall short. Read their reviews. Look at complaints. Understand their pricing. Try the products yourself if you can. Pay attention to the moments where users seem to struggle.</p><p>You aren’t looking for a reason to say, “Our app will have more features.” You are looking for a reason for someone to choose you.</p><p>Perhaps existing products are too expensive for smaller businesses. Perhaps they’re difficult to use. Perhaps they were designed for desktop rather than mobile. Perhaps they solve 20 different problems when your audience only needs three solved exceptionally well. That is where your opportunity might sit.</p><h3>Work out what makes your idea different</h3><p>Once you’ve mapped the competition, you should be able to answer a fairly uncomfortable question:</p><p><strong>Why would someone choose this app instead of what they already use?</strong></p><p>“It’s easier to use” is a start, but you’ll want to understand exactly why. Maybe your app saves a particular group 30 minutes every day. Maybe it removes a frustrating manual process. Maybe it brings several disconnected services together. Maybe it gives customers something they currently can’t do. Maybe your advantage comes from your existing industry knowledge, relationships, data or distribution.</p><p>Your differentiator doesn’t have to be a revolutionary piece of technology. Sometimes the best products win because they understand a particular audience better than anyone else.</p><p>That is especially important when you’re entering a crowded category. With more than two million apps already available on Apple’s App Store, simply being another app that performs an existing function isn’t much of a strategy. Your idea needs a clear reason to exist.</p><h3>Think about the business model early</h3><p>An app can have thousands of users and still be a poor investment. That might sound surprising, but downloads aren’t the same thing as business value. Before development begins, think about how the product is going to make money, save money or create another measurable benefit for the organisation behind it.</p><p>For a consumer app, that could mean subscriptions, purchases, advertising, transaction fees or another revenue model. For a B2B product, it might be a monthly licence, implementation fee, transaction charge or a reduction in operational costs.</p><p>For an internal business app, the value might come from reducing administration, improving productivity, reducing errors or helping employees complete work more quickly. The important thing is being able to connect the product to a business outcome.</p><p>For example, imagine an app costs £100,000 to develop and maintain. If the product is expected to generate £10,000 a year, you have a very different investment proposition from an app that could generate £500,000 a year or save the organisation £250,000 through operational efficiencies.</p><p>You don’t need to know the exact numbers on day one, but you do need to start thinking about them.</p><p><strong>Consider:</strong></p><ul><li>How will the product generate revenue?</li><li>Who is paying?</li><li>What are they paying for?</li><li>How much could a customer be worth?</li><li>How much will it cost to acquire that customer?</li><li>What will it cost to operate the product?</li><li>How much will ongoing development and support cost?</li><li>How long might it take to reach profitability?</li><li>What would make the investment worthwhile?</li></ul><p>These questions also help you avoid a common mistake: deciding that the app is worth building because the development cost seems affordable, rather than because the underlying business case makes sense.</p><h3>Consider whether people will actually use it</h3><p>Getting someone to download an app is one thing. Giving them a reason to come back is another. This is where you need to think carefully about the behaviour your product is trying to create.</p><p>Some apps naturally have frequent use. A banking app, messaging app or travel app might be opened regularly because the underlying need keeps returning.</p><p>Others solve occasional problems. An app for booking a holiday might only be used heavily at certain points in the year, but that doesn’t make it unsuccessful. Its value might come from helping someone complete an important task particularly well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*X-e_lVamClEZlYqN" /></figure><p>So don’t automatically assume that daily active users are the only measure of a successful app. Instead, ask what successful usage looks like for your particular product. What action demonstrates that someone has received value?</p><p>Is it completing a booking? Sending an invoice? Checking a journey? Uploading a document? Making a purchase? Returning to compare information? That action should influence how you design the product and what you measure after launch.</p><p>The platforms themselves recognise that engagement and retention matter. Google Play, for example, evaluates app quality using signals including user loss rate, daily active users and monthly active users, alongside factors such as usability, performance and content depth.</p><p>And retention can be a harsh reality check. AppsFlyer’s 2025 uninstall benchmark, based on 1.3 billion installs across 2,200 apps, found that<a href="https://www.appsflyer.com/resources/reports/app-uninstall-benchmarks-report/"> more than half of installed apps were uninstalled within 30 days</a>.</p><p>That doesn’t mean your app needs to be opened every day. It means the experience needs to deliver the value users expected when they installed it.</p><h3>Think about feasibility before you commit</h3><p>This is the point where the conversation needs to move from “Would people want this?” to “Can we realistically build and operate it?”</p><p>A product can be commercially attractive but technically difficult. It can also be technically straightforward but commercially weak. Both sides matter.</p><p>You need to consider things like integrations, APIs, data, security, authentication, payments, third-party services, infrastructure, regulatory requirements and the platforms you need to support.</p><p>For example, an app that simply displays information from your own database is a very different technical proposition from one that needs to connect with several external systems in real time.</p><p>An app involving financial transactions will have very different security and compliance considerations from an app for sharing recipes. An app used by employees in warehouses, hospitals or transport operations might need to work in areas with poor connectivity, support unusual hardware or handle complex permissions.</p><p>These details can significantly affect cost and timescales.</p><p>This is one reason we don’t recommend treating development as the first step. Before you commit to a build, you want enough technical understanding to know what you’re actually committing to.</p><p>A technical discovery can uncover risks early, identify opportunities to simplify the product and help you understand where the real complexity sits. Sometimes the result is reassuring: the idea is very achievable. Sometimes you discover that a particular feature will cost far more than expected. And sometimes the best outcome is finding a different way to achieve the same user outcome without introducing unnecessary complexity.</p><h3>Don’t try to build everything at once</h3><p>This is where the idea of an MVP becomes important. An MVP isn’t simply the cheapest version of your app. It is the smallest version of the product that allows you to test the most important assumptions behind the business.</p><p>If your entire business depends on people being willing to pay for a particular service, your MVP should help you test that. If the biggest uncertainty is whether customers will change their existing behaviour, your MVP should help you test that. If the biggest risk is a complicated technical integration, you may need to prove that integration before investing in the rest of the product.</p><p>This is why we prefer to think about product development as a journey of reducing uncertainty rather than simply moving through a list of features. You start with what you know. You identify what you don’t know. You work out which unknowns could seriously affect the business. Then you test those assumptions before spending heavily on the parts that depend on them. That approach can save an enormous amount of time and money.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*ZOolldLwUPQakkcx" /></figure><h3>Look at the cost of getting it wrong</h3><p>When you’re deciding whether to invest in an app, it’s easy to focus entirely on the cost of building it. But there are really two costs to consider: the cost of building the wrong thing and the cost of finding out what works. Those aren’t the same.</p><p>Investing in discovery, research, prototyping and technical planning might add cost at the beginning, but it can also prevent you from committing a much larger budget to an idea that hasn’t been properly tested.</p><p>This is something we see repeatedly with product owners. The temptation is understandable: you’ve got an idea, you want to see it become real, and development feels like the exciting part. But the most valuable work can happen before a single line of production code is written.</p><p>That is why our own process puts significant effort into understanding the product before development begins. We want to understand the users, the problem, the opportunity, the experience and the technology so that when development starts, we’re making informed decisions rather than expensive guesses.</p><h3>Define what success actually looks like</h3><p>Before deciding whether your idea is worth investing in, decide what would make you call it successful. This sounds obvious, but it is surprisingly easy to build an app without agreeing what success means, such as:</p><ul><li>Is the goal to reach 10,000 users?</li><li>Generate £500,000 in annual revenue?</li><li>Replace an existing system?</li><li>Reduce customer support calls?</li><li>Increase conversion?</li><li>Improve employee productivity?</li><li>Create a new revenue stream?</li><li>Enter a new market?</li></ul><p>The answer will influence almost every product decision you make. A product designed to generate revenue needs a different strategy from an internal app designed to reduce operational costs. A product intended to support an existing customer base needs a different acquisition strategy from a new consumer marketplace starting from zero.</p><p>The clearer you are about the outcome, the easier it becomes to decide what belongs in the product and what doesn’t.</p><h3>So, is your app idea worth investing in?</h3><p>By this point, you might have realised that there isn’t a simple “yes” or “no” test. A worthwhile app idea usually sits at the intersection of several things. There is a real problem. A clearly defined group of people experiences that problem.</p><p>Those people care enough about it to change their behaviour. There is evidence that demand exists. The competitive landscape leaves room for your product. You have a credible way to reach your audience. The product can create enough commercial or operational value to justify the investment. The technology is achievable within sensible constraints.</p><p>And, perhaps most importantly, you have a way to test the riskiest assumptions before committing to the full product. If several of those pieces are missing, that doesn’t automatically mean you should abandon the idea. It might mean the idea needs changing.</p><p>Perhaps your audience is too broad. Perhaps the problem is real but not painful enough. Perhaps your business model needs work. Perhaps there is a much smaller first version that would let you test the opportunity. Perhaps your original idea isn’t quite right, but the research uncovers a much stronger opportunity sitting next to it.</p><p>That’s why validation shouldn’t be treated as a pass-or-fail exercise. The goal is to learn enough to make a confident decision.</p><h3>What we would do before building your app</h3><p>If you came to us with an app idea tomorrow, we wouldn’t want to rush straight into development. We’d want to understand what you’re trying to achieve, who you’re trying to help and why you believe the opportunity exists. We’d look at the problem, the audience, competitors, business model and user journey, before getting into the technical considerations that could affect the product.</p><p>From there, we could start separating assumptions from evidence. Some ideas will become stronger as you investigate them. Others will need refining. Occasionally, research will tell you that the original idea isn’t worth the investment at all.</p><p>And although that can be difficult to hear, discovering it before you’ve spent a significant amount of money is a much better outcome than discovering it six months after launch.</p><p>The best product decisions aren’t always the ones that get you into development fastest. They’re the ones that give you enough confidence to know what you’re building, who you’re building it for and why it deserves to exist.</p><p>So, if you’ve got an app idea sitting in the back of your mind, don’t start by asking, <strong>“How much will it cost to build?” </strong>Start with a more useful question:</p><p><strong>“What would I need to know to be confident that this is worth building?”</strong></p><p>That’s where the real product journey begins.</p><p><strong>Ready to explore your app idea?</strong></p><p>If you’ve got an idea you’re considering investing in, we can help you work through the opportunity before you commit to a full build. From understanding the problem and validating the concept to defining the product, exploring the technology and creating a clear route towards development, our team can help turn an early idea into something you can make informed decisions about.</p><p><a href="https://thedistance.co.uk/contact-us">Explore your idea</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29b992cb8af7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>