{"id":8104,"date":"2026-08-01T02:24:14","date_gmt":"2026-08-01T02:24:14","guid":{"rendered":"https:\/\/dextora.agency\/insights\/mobile-app-or-pwa-what-small-business-should-choose\/"},"modified":"2026-08-01T02:24:14","modified_gmt":"2026-08-01T02:24:14","slug":"mobile-app-or-pwa-what-small-business-should-choose","status":"publish","type":"insight","link":"https:\/\/dextora.agency\/en\/insights\/mobile-app-or-pwa-what-small-business-should-choose\/","title":{"rendered":"Mobile App or PWA: What Small Business Should Choose"},"content":{"rendered":"

“We need an app” comes up in roughly every third meeting. Ask why, and the answer is usually one of two: “our competitors have one” or “to be closer to our customers”. Neither survives contact with the numbers.<\/p>\n

Here is when an app is genuinely needed, how a PWA differs from one, and what each option costs to own.<\/p>\n

The question that comes first: why<\/h2>\n

An app is justified when people come back regularly. If a customer deals with you twice a year, they will not install anything, and if they do, they will delete it within a month.<\/p>\n

A simple check: look at how many times a month your average customer visits your website. Fewer than twice means you do not need an app, you need a convenient website.<\/p>\n

Three options<\/h2>\n\n\n\n\n\n\n\n
Option<\/th>\nWhat it is<\/th>\nCost<\/th>\nTimeline<\/th>\n<\/tr>\n<\/thead>\n
Native<\/td>\nBuilt separately for each platform<\/td>\nHighest<\/td>\n4-8 months<\/td>\n<\/tr>\n
Cross-platform<\/td>\nOne codebase for two platforms<\/td>\nRoughly half<\/td>\n3-5 months<\/td>\n<\/tr>\n
PWA<\/td>\nA website that behaves like an app<\/td>\nLowest<\/td>\n1-2 months<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

A PWA is an ordinary website with three additions: it can work without a connection, it can be added to the phone’s home screen, and it launches without an address bar. No app store installation is involved.<\/p>\n

What a PWA can do<\/h2>\n
    \n
  • An icon on the phone screen and full-screen launch.<\/li>\n
  • Working on a poor connection and offline for pages already loaded.<\/li>\n
  • Access to camera, location and files.<\/li>\n
  • Push notifications, including on recent mobile platform versions, provided the user added the site to their home screen.<\/li>\n
  • Updates without user involvement and without store review.<\/li>\n<\/ul>\n

    What a PWA cannot do, or does worse<\/h2>\n
      \n
    • Deep hardware work.<\/strong> Continuous background tracking, specialist sensors, Bluetooth devices.<\/li>\n
    • Presence in an app store.<\/strong> For part of the audience, searching the store is the primary way of finding services.<\/li>\n
    • Heavy graphics and computation.<\/strong> Games, video processing.<\/li>\n
    • In-app payments<\/strong> under store rules.<\/li>\n
    • Familiar installation.<\/strong> “Add to home screen” is an unfamiliar gesture for many people and has to be explained.<\/li>\n<\/ul>\n

      The real problem with apps is installation<\/h2>\n

      The technical part is rarely the bottleneck. The bottleneck is getting someone through the journey: find it in the store, agree to download, wait, open, register.<\/p>\n

      People drop off at every step. For a website that journey does not exist: you follow a link and you are using it. So an app makes sense where you already have a loyal audience to direct somewhere. For acquiring new customers it is almost always a worse instrument than a website.<\/p>\n

      Cost of ownership<\/h2>\n\n\n\n\n\n\n\n\n\n\n
      Item<\/th>\nApp<\/th>\nPWA<\/th>\n<\/tr>\n<\/thead>\n
      Development<\/td>\nHigh<\/td>\nPart of the website work<\/td>\n<\/tr>\n
      Developer accounts<\/td>\nAnnual fees<\/td>\nNone<\/td>\n<\/tr>\n
      Updates<\/td>\nThrough store review<\/td>\nImmediate<\/td>\n<\/tr>\n
      OS version support<\/td>\nContinuous and mandatory<\/td>\nHandled by the browser<\/td>\n<\/tr>\n
      Two codebases<\/td>\nYes, if native<\/td>\nOne<\/td>\n<\/tr>\n
      Promotion<\/td>\nA separate install budget<\/td>\nThe same traffic as the site<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      The OS support row is the most underestimated. An app left without updates for a year starts breaking by itself and eventually disappears from the store.<\/p>\n

      When you genuinely need an app<\/h2>\n
        \n
      • A service used daily or several times a week.<\/li>\n
      • Hardware access the browser cannot provide is required.<\/li>\n
      • Your audience looks for solutions in app stores.<\/li>\n
      • A loyalty programme where regular notifications matter.<\/li>\n
      • Fully offline operation with later synchronisation.<\/li>\n<\/ul>\n

        When a PWA is enough<\/h2>\n
          \n
        • A catalogue, service booking, a customer account, order tracking.<\/li>\n
        • Your audience arrives from search and advertising rather than stores.<\/li>\n
        • Budget is limited and the idea needs testing quickly.<\/li>\n
        • Content changes often and waiting for update review is inconvenient.<\/li>\n<\/ul>\n

          A sensible sequence<\/h2>\n

          First make the website genuinely good on a phone. That is not an interim step but a task in itself: most small-business apps duplicate what a proper mobile site could have handled.<\/p>\n

          Then add PWA capabilities, which sit on top of the existing site and cost little. Watch how many people add the icon to their screen and how often they return.<\/p>\n

          If after six months there is a stable core of regular visitors, you have an argument for an app backed by numbers rather than by comparison with competitors. If no such core exists, an app will not create one.<\/p>\n","protected":false},"excerpt":{"rendered":"

          Three options with timelines and costs, what a PWA can and cannot do, why installation is the real problem with apps, a cost-of-ownership comparison and a sensible sequence instead of guessing.<\/p>\n","protected":false},"author":5,"featured_media":8100,"template":"","insight_category":[156],"insight_tag":[178,160,162],"class_list":["post-8104","insight","type-insight","status-publish","has-post-thumbnail","hentry","insight_category-trends","insight_tag-performance","insight_tag-ui-ux-design","insight_tag-web-development"],"acf":[],"_links":{"self":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight\/8104","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight"}],"about":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/types\/insight"}],"author":[{"embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/users\/5"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/media\/8100"}],"wp:attachment":[{"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/media?parent=8104"}],"wp:term":[{"taxonomy":"insight_category","embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight_category?post=8104"},{"taxonomy":"insight_tag","embeddable":true,"href":"https:\/\/dextora.agency\/en\/wp-json\/wp\/v2\/insight_tag?post=8104"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}