The Best PWA AI Girlfriend — Why Sloane Feels Like a Native Messenger

A Progressive Web App is a website that also acts like a native app. You visit the URL in your browser, tap "Add to Home Screen" (iOS Safari) or "Install" (Chrome/Android), and the site adds a full-screen icon to your device. Tap the icon and it opens without a browser toolbar — it launches, looks, and behaves like an app you installed from the App Store or Play Store.

Underneath, it's still a website — served from a server, updated on the server, rendered in a webview. But the reader-facing experience is native. Home-screen icon. Full-screen mode. Push notifications when a message arrives. Chat interface that scrolls like a messenger. Not a website in Safari — an app on your phone.

The reason this pattern has taken off in 2024-2026 for chat-first products specifically: the native-app experience matters (messenger UX, push notifications) but the native-app overhead (App Store review, download friction, per-platform builds, forced update cycles) doesn't. A PWA delivers the first without the second.

Three reasons PWA fits AI companion / chat products better than native app store distribution.

Updates ship instantly. When Sloane improves a persona's dialogue, tunes memory retention, or fixes a bug, the change is live the moment the deploy finishes. No App Store review cycle (3-7 days), no forcing users through an update to get the fix, no split userbase running old and new code. Everyone gets the improvement the next time they open the app.

No download friction to try. A native app requires the user to open the App Store, search, tap Install, wait for the download, then open. That's enough friction to lose meaningful percentages of curious users at every step. A PWA is: tap the URL, chat immediately, install to home screen only if you decide you want it. The trial happens before the install decision, not after.

Same app on every device. Sloane on your iPhone, your Android phone, your work laptop, your desktop at home — it's the same URL, the same product, the same account, the same conversation state. No app-per-platform, no Android-vs-iOS feature parity gaps, no "Windows version coming soon." One codebase, one product, every device you own.

The messenger-feel bar is set by iMessage, WhatsApp, and Instagram DMs. Users open Sloane and unconsciously benchmark it against those. Meeting that bar takes specific things:

Home-screen icon and full-screen launch. Once you install Sloane to your home screen, the icon looks and behaves like any other app icon. Tap it and it launches into full-screen mode — no browser toolbar, no URL bar, no "in a browser" visual cues. Just the app.

Push notifications for new messages. When Kaya sends you a message, your phone gets a push notification the same way iMessage does. Tap the notification and Sloane opens directly to her chat. This works on iOS (via the Web Push standard, added in iOS 16.4) and Android (Chrome web push has been solid for years). The notification lands like a message from a real person, not like a marketing email.

Chat UI that scrolls and feels correct. Message bubbles, timestamps, voice-note attachments, inline photos, typing indicators. Sloane's chat interface is built to the specific UX pattern the reader's brain expects from a modern messenger. When you receive a voice note it plays back tap-to-hear. When she sends a photo it's inline in the chat, tap to enlarge.

Persistent conversation state. Close the app in the middle of a conversation, come back three hours later, and the conversation is exactly where you left it. Same scroll position, same input draft if you had one, same everything. Same across devices too — start the conversation on your laptop, pick up on your phone.

Each of those individually is a small thing. Together they're what makes the difference between "chat app in a browser" and "app on my phone that happens to be built on web tech."

The specific install steps vary by device and browser but they're all under 30 seconds. Full walkthrough is in the install guide but the short version:

iPhone (Safari). Open sloane.world, tap the Share button (square with arrow), scroll to "Add to Home Screen," tap Add. Sloane icon appears on your home screen.

Android (Chrome). Open sloane.world, tap the three-dot menu, tap "Install app" or "Add to Home screen." Sloane icon appears.

Desktop (Chrome or Edge). Open sloane.world, look for the install icon in the address bar (small computer with a down arrow), click Install. Sloane opens in its own window when you launch it.

Once installed, Sloane runs in full-screen mode and pushes notifications for new messages. You can uninstall the same way you'd uninstall any app — long-press the icon on mobile, right-click on desktop.

Being a PWA has real advantages and a couple of honest costs. The costs:

Some device features aren't available. PWAs can't access things like the phone dialer, certain camera modes, or some deep OS integrations that native apps can. For an AI companion, none of these are things Sloane would use — chat, photos, voice notes, and push notifications all work in PWA. But if the product ever wanted native-app-only features, it'd need to ship a native app for those.

Some browsers handle PWAs worse than others. iOS Safari has good PWA support since iOS 16.4. Chrome and Edge on desktop and Android are solid. Firefox mobile is less complete. If you're on an unusual browser combination, the install experience may be lower-quality.

Meta's in-app browser (Facebook, Instagram) blocks PWA install and push notifications. This is a known Facebook/Instagram limitation — if you tap a Sloane link from inside the Instagram app, the in-app browser will let you use the site but won't let you install it or receive push notifications. The fix is to open the link in your real browser (Safari on iPhone, Chrome on Android) — Sloane shows a specific "Open in Safari" prompt when it detects this situation.

None of these outweigh the advantages for a chat-first product like Sloane, but they're worth knowing before you install.

The AI companion category is a specifically bad fit for the traditional native-app distribution model. Native app updates ship slowly through App Store review cycles that don't fit the iteration pace of AI product development. Native apps require per-platform builds (iOS + Android + web + desktop = four codebases). Native apps create download friction that costs curious users before they've had a chance to try the product.

A PWA solves all three: instant ship, one codebase across all platforms, and zero download friction from URL to first message. The user gets a native-quality experience without the native-distribution overhead the product doesn't benefit from.

Sloane runs as a PWA because it's the right architectural fit for a chat-first product that needs to iterate fast, run cross-platform, and let users try before they install. If you want to see what the experience feels like, no install is required to start — anon chat is available on every persona's page. If it feels right, the install-to-home-screen step takes about 20 seconds.