kitallis
commented
11 months ago Hi @jgwinner, thanks for the proposal.
You are absolutely right. There are definitely other stores than just those 2. And not just stores, SDKs for example, ship to different distribution environments, like maven.
We do support other distribution environments, like Firebase App Distribution and our interfaces are designed in a way that we can easily add new stores or store-like platforms.
In general, our distribution environments are classified as:
- Rolloutables (staged/phased rollouts on app store or play store supported)
- Depositories (just artifact shipping)
Since you took the time to write this out, I'm assuming you need this. Would love to talk to you about what you're building and if we can help add support. Feel free to book a call here.
...also curious, how did you discover us? :)
Proposal
Google and Apple aren't the only mobile dev platforms - any consideration for other stores, like Steam, the Meta/Quest stores, and the Vive store?
What this achieves / problem(s) it solves
Mobile Apps developers frequently work with Unity and other applications, and release their mobile apps (VR) on the Quest store, and PC apps on Steam, and both on the Vive Store; then do another mobile release on the traditional stores.
Building pipelines for these as well as the traditional Tramline would be useful. I do see frequent releases on both the App/Play stores, as well as the Quest store for a similar app (or a non VR build).
Steam isn't mobile, but again quite often it's the same Unity project, just different build options.
Alternatives
Custom CI/CD, or Unity paid services
Additional context
Not always mobile builds, but integrating into stores is still a bit of a mess.