top of page

Your Business Doesn't Need an App

Shift Quality Editorial
Jul 2, 2025
4 min read

Updated: 5 days ago

Corrected, 4 October 2026. We re-checked this post's figures. The app-retention figure is now sourced and dated, and cost figures are labelled as estimates or illustrative ranges.

At some point, someone will suggest that your business needs a mobile app. A developer pitching their services. A competitor who launched one. A business advisor who read an article about "mobile-first strategy." The idea lands and suddenly you're looking at quotes for $30,000-$100,000 to build something your customers never asked for.


Most small businesses do not need a mobile app. The ones that built one anyway usually discover that nobody downloads it, nobody uses it, and the maintenance costs never stop.


This isn't a contrarian take. It's math.


The Numbers That Kill Most Business Apps


The average smartphone user has 80+ apps installed. They use about 9 daily. The odds of your business app being one of those 9 are essentially zero unless your product is the app (you're Uber, you're Instagram, you're a game).


App store discovery is brutal. Unless you have a significant marketing budget to drive downloads, your app will be invisible among the millions of others. And even if people download it, most won't stay: in 2015 data from Quettra covering more than 125 million Android phones, the average app lost 77% of its daily active users within three days of install.


Then there's the ongoing cost. An app isn't a one-time purchase — it's a living product that needs updates when iOS and Android release new versions (annually), security patches, bug fixes, and feature updates. A common industry rule of thumb puts annual maintenance at around 15-20% of the initial development cost; treat that as an estimate, not a measured figure. On that assumption, a $50,000 app costs $7,500-$10,000 a year just to keep functional.


When You Actually Need an App


Apps make sense in a few specific scenarios:


Your product IS the app. If the core experience is a mobile interaction — a fitness tracker, a food delivery service, a ride-sharing platform — an app is the product, not a marketing channel.


Offline functionality is critical. If your users need to access your product without internet — field workers, travelers, areas with poor connectivity — an app can cache data locally in ways a website can't easily match.


You need deep device integration. Push notifications (the real kind, not web notifications), camera access for scanning, GPS tracking, Bluetooth connectivity, health sensor data. If the core experience depends on hardware features, an app may be necessary.


Your users would genuinely use it multiple times per day. Not "might use it" or "would use it if they had it." Evidence — from customer behavior, not customer surveys — that frequent, repeated mobile interaction is a real pattern.


If none of these apply, a mobile-responsive website does everything you need, reaches all devices, costs a fraction of an app, and doesn't require anyone to download anything.


What a Good Website Gives You


A well-built, mobile-responsive website:


  • Works on every phone, tablet, laptop, and desktop without downloading anything

  • Is findable through Google (apps are not — they live in app stores)

  • Can be updated instantly without waiting for app store review

  • Usually costs far less to build than a comparable native app

  • Doesn't need annual updates for operating system compatibility

  • Can send notifications (via web push, if you need them)

  • Can work offline (via service workers, if you need that)

  • Can be "installed" on a home screen (via Progressive Web App technology)


A Progressive Web App (PWA) specifically bridges most of the gap between a website and a native app. It can work offline, send notifications, and feel like a native app — without the app store, without the download, and without the maintenance burden.


The "But Our Competitors Have an App" Argument


Having an app doesn't mean having a successful app. Check your competitor's app reviews and download count. If it has 200 downloads and 2.5 stars, they wasted money and your argument for building one just evaporated.


If your competitor's app has 50,000 downloads and 4.5 stars, and their app is central to their customer experience, then yes — consider whether an app makes strategic sense. But consider it because of the user behavior it enables, not because the competitor has one.


The Decision Framework


  1. Is your core product a mobile interaction? If no, stop. You need a website.

  2. Do you need offline functionality or deep device integration? If no, stop. A responsive website or PWA handles everything else.

  3. Do you have evidence of multiple-times-daily usage patterns? If no, stop. An app that's used weekly doesn't justify the investment.

  4. Do you have the budget for ongoing maintenance ($7,500-$15,000/year)? If no, stop. An unmaintained app is worse than no app — it reflects poorly on your brand.

  5. If you passed all four checks: Build an app. But start with one platform (iOS or Android, based on your user demographics), build the minimum viable version, and prove usage before investing in the second platform.


The Alternative Investment


Take the $50,000 you were going to spend on an app and instead:


  • Build an excellent mobile-responsive website ($3,000-$10,000)

  • Invest in SEO so customers find you through Google ($500-$2,000/month)

  • Set up proper email marketing to stay in touch with customers ($50-$300/month)

  • Create content that demonstrates your expertise (time investment)

  • Improve your Google Business Profile (free)


This investment reaches more customers, generates more leads, and costs a fraction of an app, with a far lighter maintenance burden. (The price ranges above are illustrative; real quotes vary widely by market and scope.)


Key Takeaway


Most small businesses don't need a mobile app. A mobile-responsive website or PWA serves the same purpose at a fraction of the cost without app store dependencies or ongoing maintenance. Build an app only when your product is the app, you need offline or deep device features, and you have evidence of frequent daily usage. Otherwise, invest in the web presence that actually drives your business.


Sources




Related reading


bottom of page