> For the complete documentation index, see [llms.txt](https://docs.roomiekit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roomiekit.io/roomie-kit-cloud-and-hosted/web-vs-mobile.md).

# Web vs mobile hosted apps

Roomie Kit Hosted has two creation paths. Choose the simplest path that matches the first version you want to ship.

## Web App

Choose **Web app** when you want the fastest launch.

Web Hosted deploys:

* A Roomie Kit web app at `https://<app-slug>.roomiekit.io`.
* Supabase auth, database, migrations, and core Edge Functions.
* Agora room voice, video chat, and livestream token support.
* Managed starter assets.
* Post-deploy checks.

Payments and push are off by default. This keeps the first deployment focused on rooms, auth, and media. Web monetization can be added later.

## Mobile App Beta

Choose **Mobile app beta** when the first release needs iOS or Android.

Mobile Hosted creates the same web/backend foundation, then tracks a native setup checklist:

* Bundle ID and Android package name.
* Apple Developer account.
* Google Play account.
* App Store Connect IAP products.
* Google Play Billing products.
* RevenueCat project and app API keys.
* OneSignal app with APNs and FCM configured.

Native publishing is assisted during beta. Store accounts, certificates, app review, APNs, FCM, and billing products still require owner approval.

## Payments

Roomie Kit subscriptions are billed by Roomie through Stripe.

Your hosted app monetization is separate:

* Web apps can use Stripe Checkout or Billing when monetization is needed.
* Mobile apps should use RevenueCat for iOS and Android in-app purchases.
* Cross-platform entitlements can use RevenueCat later if the same customer account needs purchases across web and mobile.

Roomie does not act as merchant of record for your app users in v1.

## Push

Push is disabled by default.

For Mobile Hosted beta, OneSignal is the default push provider. Push is only enabled when the app requests it and the required OneSignal keys are configured.

## Recommended Path

Start with Web Hosted unless the first release must be in the App Store or Google Play. It proves the room, media, auth, and admin loop first. Move to Mobile Hosted once the product is stable and the native accounts are ready.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.roomiekit.io/roomie-kit-cloud-and-hosted/web-vs-mobile.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.