Installable web app
Add JATA AFTERCALL to your home screen.
The installable app is this same Next.js application — one backend, one database, one subscription system. Installation adds a full-screen shortcut and a small cache of public static assets; it does not create a second app to maintain.
Android (Chrome, Edge, Samsung Internet)
- Open https://jata-aftercall.vercel.app in Chrome over HTTPS.
- Tap the browser menu (three dots) and choose Install app or Add to Home screen. On supported browsers an in-app Install prompt also appears; Not now dismisses it without blocking a feature.
- Open the new icon. The app launches in standalone display mode with the JATA AFTERCALL name, icons and espresso theme colour, starting at the homepage.
- When a new version is published, a non-intrusive Refresh toast appears. Tap it to activate the waiting service worker and reload.
iPhone and iPad (Safari)
- Open the site in Safari (iOS only supports home-screen web apps through Safari).
- Tap Share, then Add to Home Screen, then Add.
- Launch from the home screen. The apple-touch-icon and standalone metadata are already configured.
- iOS does not fire Chrome's install prompt, so no install toast is shown. Safari fetches new assets on navigation; if the app shows an old version, close it from the app switcher and reopen.
Honest limitation: a PWA added to the home screen is not an App Store submission package. App Store distribution requires a separately built and signed iOS application; see the release report for its current status.
Connectivity and offline behaviour
The service worker caches only versioned public static assets (icons, images, JavaScript and CSS) and a short offline notice. It never caches HTML navigations, API responses, authenticated pages, draft previews, checkout pages, AI answers, payment responses or private business data.
- When you are offline, an indicator appears and a plain offline notice replaces an unreachable navigation.
- AI Front Desk answers, Website Studio generation, Paystack verification, media uploads, publishing and POS synchronisation require connectivity.
- Offline POS sales remain a separately scoped feature: the existing till queue records unconfirmed sales with idempotency keys and replays them only when the server accepts them. No offline payment is treated as money received.
Update detection runs when the tab becomes visible. Old static caches are deleted on activation, so a refresh cannot leave two versions of the app competing.