AI Companion PWA vs Native App: Run a Device-Route Test

Start with the distribution route, not the icon

Distribution route determines every downstream boundary. A native app ships as a compiled binary through Apple App Store or Google Play, subject to store review, binary size limits, and platform-specific signing. A PWA begins at a URL, serves a web app manifest declaring name, icons, start_url, display mode (“standalone”), and scope. web.dev documents that PWA installation uses a web app manifest and browser/platform criteria; no separate executable package is required, install behavior varies, and an installed PWA can open in a standalone window. On iOS, browser and platform limitations change the route.

Home-screen appearance alone never proves native packaging. An installed PWA can open in a standalone window while content still comes from a web origin. Removing its icon does not prove that browser storage or the service account was deleted. The supported distinction is distribution control: web content can change without shipping a new native package. That says nothing by itself about battery use, privacy, speed or store policy. Next action: open the target URL on the device you will actually use and record whether the browser offers installation.

Compare who controls install, updates and permissions

Control sits with three owners: browser, platform store or site publisher. For a PWA, the browser and operating system apply their current installation criteria to the supplied manifest and site. Updates can come from server-delivered files and service-worker logic, but activation depends on the implementation and browser lifecycle. Permissions remain separate capabilities: an install prompt does not prove notifications, camera access or offline operation. Record a permission only when the device actually requests it.

A native app routes its package through a platform distribution system and uses operating-system permission controls. For AISoul, the marketing site www.aisoul.work is not itself evidence of an installable PWA. Publisher code for mobile.aisoul.work includes a manifest and service-worker registration, but that inspection does not establish offline chat, notification delivery or installability on every device. If “install without visiting an app store” is mandatory, test the browser route. If a background or hardware feature is mandatory, require explicit documentation and a device test instead of assuming every native app supplies it.

Run an Installability Receipt on each device

A Device Route Receipt records observable facts per surface. Build one before committing credentials or payment. The receipt forces separation between surface, storage, and account.

Worked example (hypothetical observation, not an AISoul test): suppose Browser A offers “Install” and the launched surface has no ordinary address bar, while Browser B offers only a bookmark. The supported conclusion is limited: Browser A provided an installed web-app experience on that device; Browser B did not expose the same route. It does not prove offline queuing, notification delivery, update timing, privacy or account deletion. The next action is to repeat the receipt on the exact phone and browser intended for daily use, then test each required capability separately.

Trace the billing and refund owner before paying

Billing owner is the entity named by the checkout, receipt and governing refund terms. AISoul facts checked 2026-09-07 list one-time, non-renewing Passes: 7-Day $4.99, 30-Day $8.99, 90-Day $19.99, Annual $49.99. Payment method, FX, tax and bank approval vary. Because the Pass does not auto-renew, there is no recurring Pass to cancel, but the user should still retain the receipt and identify the named merchant and refund route. A home-screen icon does not answer any of those billing questions.

Contrast with a hypothetical native app using IAP: the platform would own the refund window. For adult companions, store billing can also trigger content restrictions that web billing avoids. Decision implication: trace the merchant name at checkout. If the merchant is the publisher and the terms list no recurring clause, the stop condition for billing comfort is met. Unsupported inference: web billing is automatically more private; the publisher still processes the card or processor token. Next action: review the exact confirmation email domain and linked terms before entering payment details. See refund mechanics in /research/ai-companion-app-refund-policy.html.

Audit notifications, cache and local traces separately

Notifications, cache and local traces must be audited separately because installation does not settle any of them. Web notifications depend on implementation, permission and platform support. A service worker may use browser storage, but registration alone does not disclose what is cached. A user may also save media outside the browser. Removing a home-screen icon therefore answers only whether the launcher remains; it does not answer what remains locally or with the service.

For AISoul, the free allowance resets by Beijing calendar day—50 messages and 5 gallery photos daily, plus 2 clear clips lifetime—but those quotas do not disclose storage location or retention. Audit steps: list the exact origins shown in browser storage controls, note whether a notification prompt appears, record downloaded files separately, remove the launcher, then inspect the same controls again. Treat local clearing, Pass expiry and an account-deletion request as different events. This page has not verified the server-side result of deletion. See browser-only considerations at /research/ai-girlfriend-no-download-browser-only.html.

Choose native integration or browser reach by a stop condition

Define an explicit stop condition before testing. Example: “If documented background audio is required, reject any product that does not publish and pass that exact device test; otherwise continue with the browser route when installation and checkout are usable.” This does not assume that a native product has the feature or that a PWA lacks it. It makes the required capability—not the icon—the decision owner.

AISoul’s product is a chat-first, user-initiated adults-only browser companion with one active fictional companion. Registration uses email/password or supported sign-in, with no visible DOB or identity-document field. It supplies text, eligible gallery-photo/short-clip retrieval, and no live calls or fresh prompt-to-video. One possible stop condition is “does my device offer a usable browser route and checkout?” If yes, the web route fits that requirement. If a hardware feature is essential, require evidence for that feature. Native is not automatically faster; this page did not run a matched latency test. Further detail appears in AI girlfriend browser vs app.

PWA-versus-app questions that change the route

Does adding a PWA to the home screen make it a native app?

No. The resulting icon launches a web view or standalone browser context. It never gains the compiled binary, sandbox, or entitlement set of a native app. On Android it may use Trusted Web Activity, but the code remains HTML, CSS, and JavaScript served from the origin. This changes the route for users who assumed icon equals native permissions. The observable mechanism is still web-origin delivery; the decision boundary remains browser-controlled updates and storage model.

Can I delete an AI companion account by simply removing the app icon?

No. Removing an icon establishes only that the local launcher is gone. It does not demonstrate what browser storage remains, whether downloaded files remain, or what the service retains. Consult current account controls and the privacy policy for a separate deletion-request route, and retain any confirmation supplied. This page did not test AISoul deletion outcomes, so it does not promise when or whether every retained copy disappears.

Will an AI companion PWA receive push notifications like a native app?

It depends on platform. Android Chrome supports web push for PWAs when the service worker is active. iOS Safari limits background push for installed PWAs. Even when technically possible, the companion must implement the Push API and the user must not have disabled notifications for the origin. Test by requesting permission and sending a manual trigger; absence of delivery is the stop condition for notification-dependent use. The boundary is platform policy, not publisher intent.

Is web billing always safer than App Store billing for adult companions?

Web billing gives the publisher direct merchant relationship and avoids store content review, but it also removes Apple’s refund infrastructure and subscription visibility. Safety is not binary; it equals “can I locate the exact cancellation path before entering payment details?” For the listed AISoul passes, the path is the account dashboard. Verify the terms linked at checkout. The numeric boundary is the listed one-time prices; the failure route is assuming automatic renewal where none is stated.

What happens to local media or chat history when I clear browser storage on a PWA?

Clearing browser storage for the origin deletes IndexedDB, Cache API entries, and LocalStorage that the PWA used. Server-side history tied to the AISoul account survives. If you had downloaded gallery photos to the device photo library, those files remain in Photos or Files app. The distinction prevents assuming automatic data removal. AISoul makes no end-to-end-encryption claim and external providers may process content. Chats are not public to other users.

Installation evidence and functions we did not test

Installation evidence here is limited to manifest presence and service-worker registration in publisher code; no install event was tested. web.dev states that an installed PWA can open in a standalone window, while browser and platform rules still change the route. AISoul's marketing site is not itself evidence of an installable PWA. The mobile chat code inspection does not establish offline chat, notification delivery or installability on every device.

We did not test offline chat or inspect a production cache inventory. We also did not test push delivery, background behavior, battery impact, camera or microphone permission persistence, or cross-device synchronization. Those unknowns must be resolved on the reader's actual device if they are purchase requirements. This product is not therapy, crisis care, dating, or a human relationship.

Official direct sources: https://web.dev/learn/pwa/installation, https://web.dev/learn/pwa/progressive-web-apps, https://www.aisoul.work/pricing.html, https://www.aisoul.work/about.html, https://www.aisoul.work/privacy.html, https://www.aisoul.work/terms.html. Untested boundaries include offline message queuing, iOS 18.1+ push reliability, and any future manifest changes after 2026-09-07. All facts current as of 2026-09-07.