App or Website? What Actually Differs in AI Companion Apps
Most companion platforms ship both a mobile app and a website, and people assume the two are the same product in two skins. They are not. Choosing the surface changes who bills you, what the app can do, what it is allowed to collect, and how fast you get fixes. None of these differences are about the chat itself, which is usually identical.
The billing difference is the big one
This is the only difference that can cost you real money, and it is decided the moment you subscribe.
| If you subscribe | Who is the merchant | How you cancel | Typical consequence |
|---|---|---|---|
| Inside the mobile app | The app store | The store's subscription settings | Deleting the app cancels nothing |
| On the website with a card | The platform itself | The platform's billing page or support | Usually the fastest route out |
| Through a processor link | The processor | The processor's portal | Depends on the processor's tooling |
Two practical consequences follow.
Prices can differ between surfaces. Stores take a commission on in-app purchases, and platforms choose different ways to absorb it: some charge the same, some charge more in-app, some restrict in-app purchase to a pricier tier. Never assume the app price and the web price match — check both before subscribing.
Cancellation friction is not symmetrical. A web subscription can be cancelled by one email. An app-store subscription lives in a settings menu that many users never find, which is why "I cancelled it and they kept charging me" is so common: the cancellation was never made where the charge came from. Our cancellation guide walks through the channels.
If you take one thing from this page: subscribe on the surface where you would rather cancel.
What the app can do that the browser cannot
Native apps are not a wrapper for no reason. They get access to things a web page mostly cannot:
- Push notifications. The character can message you. In a browser this needs a permission prompt most people never grant, and it works less reliably.
- Background audio. Voice conversations, and audio that continues when the screen locks.
- Microphone and camera handling. Voice input with tighter latency, and camera capture for image features. Browsers can request the microphone, but the experience is rougher and permission is per-session more often.
- Local storage and offline behaviour. Drafts, cached media and faster cold starts.
- Device-level integrations. Widgets, share sheets, and in some cases on-device speech recognition.
If voice is the main reason you use a companion product, the app is usually the better surface and the difference is not subtle.
What the browser can do that the app cannot
- Ad blockers and privacy extensions. Meaningful if you are uneasy about third-party trackers, and unavailable inside a native app.
- Multiple accounts without ceremony. Separate browser profiles isolate sessions in a way that is tedious on mobile.
- Text you can copy out. Some apps restrict selection and copying; a browser page rarely does.
- Instant updates. The platform ships a fix and you have it on reload. App store review can add days or weeks, and old app versions can linger on your device for a long time.
- Desktop-quality reading and writing. Which matters more than it sounds if you are doing long-form roleplay.
Permissions and data access
The app asks for permissions at the operating-system level, and those permissions are broad by nature. Notification access, microphone, camera and photo library are all disclosures you are making to the operating system, not just to one product.
A browser session asks for far less: microphone or notification access only if the page requests it, and nothing else. It also sits behind whatever content blocker you already run.
This does not make apps untrustworthy. It does mean the two surfaces have different default exposure, and it is worth knowing which one you are choosing. The privacy guide covers what these products tend to collect once they have access.
Features can arrive on one surface first
Platforms ship to the web first when a feature is experimental, because iteration is instant and there is nothing to review. They ship to the app first when a feature depends on device capability, such as voice or notifications.
The consequence is that "the app has it but the site does not" is normal, temporary, and worth checking before you conclude a feature does not exist. It also means screenshots in reviews can be misleading: a review written about the app may describe a build that is a month behind the site.
Is your account the same on both?
Usually, but not always in the way you would expect:
- Chat history is usually shared, because it lives server-side.
- Subscription entitlement usually is not identical, if the subscription was bought in a store. Some platforms honour an app-store subscription on the web and some do not, and the reverse is more common still.
- Credits and media balances sometimes differ, particularly if the two surfaces have separate purchase paths.
If you switch surfaces, open the billing page on the new surface and confirm the subscription is recognised before you rely on it. A silent fallback to the free tier is a common and annoying failure.
What to check before you commit
- Price on both surfaces. In-app pricing frequently differs.
- Where the subscription will be billed, and how you would cancel it.
- Whether entitlement carries across surfaces.
- Which surface has the features you actually want — voice and notifications push you to the app; long-form writing, extensions and exports push you to the web.
- Permissions you are granting. Review them in the OS settings, not when you are prompted mid-conversation.
A reasonable default for most people: browse and subscribe on the web, install the app only if you want voice or notifications, and cancel wherever the money came from. See the platform comparison for how the underlying product models differ — that choice matters more than the surface.
Key takeaways
- App and website are different surfaces with different merchants, features and permissions, not two skins on one product.
- The billing channel decided at signup determines how hard it will be to cancel; subscribing on the web is usually the easier route out.
- Prices can differ between surfaces because of store commissions.
- Native apps win on voice, push notifications, background audio and device integration; browsers win on updates, extensions, copyable text and multi-account isolation.
- Account entitlement does not always carry across surfaces — verify it before relying on it.
- Features often launch on one surface first, so reviews can describe a build you cannot see.
For what to check before paying rather than after, see the subscription traps entry and the terms checklist.