You’re absolutely right that anything even adjacent to adult themes gets extra scrutiny from Apple and Google, and that relying on those ecosystems alone would be risky.Moving from one locked garden to two others (App Store and Google Play) doesn't feel like a move towards progress. Shouldn't this just be a website instead so it can truly remain independent? Apple will try to get rid of it as soon as it gets any attention, regardless if it's OK in the current App Store guidelines. It doesn't seem like Google is as puritan as Apple yet, but not exactly a solid foundation if you wanna build something resilient.
That’s why the current plan isn’t to make Ember Games exclusive to the app stores, it’s designed as a hybrid approach:
- The core app (on iOS/Android) is a directory, launcher, and companion hub, completely clean, compliant, and free of user-generated or explicit content. It’s essentially a discovery tool with optional account sync.
- The actual adult or age-restricted content (like NSFW game builds, Patreon links, etc.) is web-hosted externally, just like how Reddit, Twitter, or OnlyFans link out to restricted content without hosting it directly.
That means:
- There’s no user-generated content moderation overhead within the app.
- We don’t store or serve adult assets, bypassing the legal minefield.
- The same app build can run on Android, iOS, or as a PWA (Progressive Web App) in any browser — giving us full independence and resilience.
So yes — the Ember Hub is effectively a website too, but packaged as a native app for discoverability and mobile usability. The goal is accessibility, not dependency.
Long term, the ecosystem would prioritize:
- Direct browser access (via a PWA or web viewer)
- Optional Android sideloading
- Optional desktop launcher
- App store presence purely as a discovery funnel, not as a choke point
In short, the app is the entry point, not the fortress.