Skip to main contentSkip to navigationSkip to footer
    Web & Apps · Service

    An app.
    No app store.

    A progressive web app installs from the browser, opens without a connection and sends notifications. One codebase runs on every phone, tablet and desktop.

    See pricing
    At a glance
    ₹0,000 + GST per application
    Typical plan: 3–6 weeks
    0
    Codebase for every device
    iOS 0.0+
    Web push on iPhone
    PWA OR NATIVE

    Same phone.
    Three ways in.

    All three open on a phone. What differs is how a customer gets it, what it does without a connection, and what each release takes.

    How people get it
    Responsive website
    A link
    Progressive web app
    A link, then Add to Home Screen
    Native app
    App Store and Google Play
    On the home screen
    Responsive website
    A bookmark, at most
    Progressive web app
    Icon, splash screen, full screen
    Native app
    Icon, splash screen, full screen
    Without a connection
    Responsive website
    Does not open
    Progressive web app
    Opens, with the screens cached for it
    Native app
    Opens
    Push notifications
    Responsive website
    No
    Progressive web app
    Android and desktop. iPhone from iOS 16.4, once installed
    Native app
    Yes
    Releasing an update
    Responsive website
    A deploy
    Progressive web app
    A deploy, applied the next time the app opens
    Native app
    A store review for each release
    Codebase
    Responsive website
    One
    Progressive web app
    One
    Native app
    iOS and Android, or one in React Native
    Phone features
    Responsive website
    Camera and location
    Progressive web app
    Camera, location, share sheet, notifications
    Native app
    All of them, including Bluetooth, NFC and widgets
    Store accounts
    Responsive website
    None
    Progressive web app
    None
    Native app
    Apple: $99 a year. Google: $25 once
    Price
    Responsive website
    ₹10,000 single page, ₹50,000 up to 10 pages
    Progressive web app
    ₹35,000 per application
    Native app
    Expo (React Native) app from ₹1,00,000
    WHAT'S INCLUDED

    Every screen. Online or off.

    Screens, offline behaviour and notifications are listed in the written scope before a line of code is written.

    The app
    01
    React and TypeScript application, built with Vite
    02
    Up to 6 screens designed for a thumb first, then tablet and desktop, with two revision rounds
    03
    Navigation, gestures and transitions that behave like an app's
    04
    Opens in Chrome, Safari, Edge and Firefox
    05
    Loading, empty and offline states on every screen
    What makes it installable
    01
    Web app manifest: name, icons, splash screen and theme colour
    02
    Service worker written with Workbox, with a caching rule per kind of request
    03
    Offline support for the screens named in the scope
    04
    Web push notifications with one trigger, asked for after a person chooses them
    05
    Install prompt on Android and desktop, and an Add to Home Screen guide for iPhone
    06
    Updates applied the next time the app opens
    Handover
    01
    Repository in your GitHub, with a README a new developer can follow
    02
    Deployed to Cloudflare Pages or Vercel, with a preview URL for every change
    03
    Test report across iPhone, Android and desktop browsers, online and offline
    04
    A written list of what is cached, and for how long
    05
    A recorded walkthrough of the app and the codebase
    06
    A 30-day window after launch for fixes to anything delivered
    WHAT IT COSTS

    ₹35,000 per application.

    The price is per application: up to 6 screens, offline use for the core screens, one notification trigger and two rounds of design revisions. Anything beyond it is quoted in writing before work starts. A native app in Expo is a separate build, from ₹1,00,000.

    ₹0,000 + GST
    Per application: up to 6 screens
    Core screens offline, one notification trigger, two revision rounds. More is quoted in writing.
    0–6 wk
    Typical plan
    From signed scope to a link people can install. The scope sets the date.
    0 min
    First call
    What the app does, who opens it and where, then a written scope.
    HOW LONG

    Four phases. Tested offline.

    A typical plan. The number of screens and how much works offline move it. Work beyond the starting package is scoped and dated separately.

    01
    Week 1

    PWA architecture

    Offline screens, caching rules and notification triggers agreed in writing, screen by screen.

    02
    Weeks 1–2

    Design

    Every screen designed at phone width first, with its offline state, approved before the build.

    03
    Weeks 2–3

    Service worker and screens

    The interface and the caching built together, on preview URLs you can install on your own phone.

    04
    Week 3 onward

    Testing and launch

    iPhone, Android and desktop browsers, online and in aeroplane mode. Then production and handover.

    IF IT GOES WRONG

    An app. Still a website.

    If a phone will not install it, the browser still opens it.

    01

    It works without installing

    Every screen opens from a link in any modern browser. Installing adds to it and is never required.

    02

    Offline scope in writing

    The scope names which screens open without a connection and which need one.

    03

    A fix is a deploy

    No review queue sits between a fix and the people using the app. They get it the next time they open it.

    04

    Rollback in one step

    Every deploy is kept. The service worker picks up a rollback like any other update.

    05

    Code that outlives anyone

    Your repository, in React and TypeScript, documented. Any React developer can pick it up.

    06

    Bugs fixed

    Anything in the delivered scope that does not work as agreed is fixed as part of the build.

    WHO IT'S FOR

    Most app ideas. Not every one.

    If the second list sounds like you, the first call will say so.

    A PWA fits

    • 01
      A loyalty or rewards app

      Points, offers and a card that opens offline at the counter, with a notification when something changes.

    • 02
      An event or conference app

      Needed for a few days, shared as a link or a QR code, live without a store review.

    • 03
      A home-screen icon for the brand

      One codebase for iPhone, Android, tablet and desktop.

    • 04
      An existing React app

      Made installable: manifest, service worker, offline screens and push added to what is there.

    A different build fits better

    • 01
      Camera-heavy or graphics-heavy work

      A native app in Expo (React Native), from ₹1,00,000.

    • 02
      Bluetooth, NFC or home-screen widgets

      iPhones give these to native apps only. Native is the route.

    • 03
      Nobody needs it offline or installed

      A responsive website costs less: ₹10,000 for a single page, ₹50,000 for up to 10 pages.

    STANDARDS YOU CAN CHECK

    Tested on a phone. Then offline.

    Each one can be checked on your own phone, or in Chrome's developer tools.

    01

    Installable, and it shows

    The Application panel in Chrome's developer tools reads the manifest and the service worker without warnings.

    02

    Opens in aeroplane mode

    Switch the connection off and open the app. The screens named in the scope load.

    03

    HTTPS on every request

    Service workers run only on secure origins. Nothing loads over plain HTTP.

    04

    Lighthouse on a phone

    Performance and accessibility measured on the main screens. Targets agreed in the scope.

    05

    Permission asked, not demanded

    The notification prompt appears after a person chooses to be notified, never on first load.

    06

    Keyboard and screen reader

    Menus, dialogs and forms work without a mouse or a touch, with labels and visible focus.

    BEFORE YOU BRIEF

    What founders ask about PWAs.

    For most apps a brand needs, it does the same job: an icon on the home screen, full-screen screens, offline use and push notifications. A native app is the better choice for camera-heavy or graphics-heavy work, and for Bluetooth, NFC or home-screen widgets. The table above sets out the differences.
    Yes. In Safari, the Share menu has Add to Home Screen, and the app then opens full screen and works offline. Push notifications work from iOS 16.4, once the app is on the home screen. Safari does not show an automatic install prompt, so the app carries a short guide of its own.
    From a link. On Android and desktop, Chrome and Edge offer an install prompt, shown at a moment the scope names. On an iPhone it is two taps through the Share menu. Nobody has to install it to use it: the same link opens in any browser.
    A release is a deploy. The service worker fetches the new version in the background and applies it the next time the app opens. There is no store review and nothing for the user to tap.
    What the scope says. Each screen is marked as offline or online-only, and each kind of request gets a caching rule: the shell and images cached, prices and balances fetched fresh when a connection exists. Actions taken offline can be queued and sent on reconnect, where the scope includes it.
    Google Play accepts a PWA packaged as a Trusted Web Activity. Apple's App Store needs a native wrapper and goes through review, and Apple charges $99 a year for a developer account. Either is a separate piece of work, scoped on its own.
    Often, yes. A React app gains a manifest, a service worker, offline screens and push. A site built on older technology may need its front end rebuilt first. A read of the code comes before the scope.
    Hosting for the app's files sits on the smallest plans most hosts offer. Push notifications are sent from a small server-side function, such as a Cloudflare Worker, or from your existing backend. Providers bill you directly, and the scope states the expected cost.
    You own it: the repository is in your GitHub and the hosting account is in your name. Anything in the delivered scope that does not work as agreed is fixed as part of the build. After that, further features are quoted in writing, or your own developers take over.
    3 SERVICES · WEB & APPS

    More in Web & Apps.

    Their home screen.
    Your icon.

    A 30-minute call about the app. A written scope after it.

    See pricing