App Distribution Disclosure
Effective Date: 2026-05-23 Last Updated: 2026-05-23
This page documents how the ConKarma mobile app is distributed to users via the Apple App Store + Google Play Store + Microsoft Store + web, including how the app's Bundles architecture (see /features/bundles) interacts with each store's on-demand delivery mechanisms.
1. Distribution channels
- Apple App Store — iOS + iPadOS + Apple Watch + Apple TV + visionOS.
- Google Play Store — Android phone + tablet + Wear OS.
- Microsoft Store — Windows 11.
- Web — limited surface set (Hestia at web.conkarma.app).
The Minerva marketing site at conkarma.app is not the app distribution channel; it is the public marketing + auth + support surface for the apps.
2. Bundles — what gets delivered when
ConKarma's app is shipped as a lean core install (<30MB on each platform) plus on-demand modules delivered as the user opens specific surfaces. The architecture is:
- Asset Bundle Architecture — pillar assets, animations, curated content, locale resources, and AI feature dependencies are not all included in the base install. They download when the user navigates to the surface that needs them.
- Locale Bundle — the cell's chosen locale's full translation bundle downloads on first locale switch; English ships in the base install.
- Per-pillar deferred components (Android) — using Play Feature Delivery, individual pillar modules (Workshop, Spotlights, Hearths, etc.) are downloadable Android feature modules. The base install carries the core navigation + Cell + most-used pillars; optional pillars install on first use.
- On-Demand Resources (iOS) — using Apple's standard NSBundleResourceRequest API, large pillar assets (e.g. The Hearths render textures, Joysticks catalog imagery) load on first pillar use.
- Quarterly Content Bundle — Vibes catalog refresh, Echoes drop, Brewing pillar updates ship as quarterly content bundles pulled in the background.
- Module Manifest API — the cell's app loads the module manifest from the server on launch; modules the cell isn't using are not downloaded.
- Background Module Update — modules update in the background when the device is on Wi-Fi + charging. The user can disable background updates per Settings → App → Background module updates.
3. Apple App Store — section 2.5.2 compliance
Per Apple App Store Review Guideline 2.5.2 — "Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps":
- ConKarma does not download or execute code outside the App Store binary. All executable code ships with the App Store binary.
- All on-demand downloads are asset / content / resource bundles only — images, audio, JSON content, localized strings, curated UGC catalogs, AI prompt templates. None of these contain executable code.
- Apple On-Demand Resources (NSBundleResourceRequest) is the sanctioned mechanism for the asset bundles described above; we use it exactly as specified.
- The Quarterly Content Bundle contains only the editorial-curated content (Vibes catalog, Echoes catalog, Brewing roster, etc.) — data, not code.
4. Google Play — Play Feature Delivery + Play Asset Delivery
Per Google Play Console policies:
- ConKarma uses Play Feature Delivery for optional pillar feature modules (Workshop, Spotlights, etc.). Each module is a signed module within the same App Bundle; no side-loaded code.
- ConKarma uses Play Asset Delivery for large content bundles (Hearths textures, Joysticks catalog imagery, locale resources).
- Background module updates use the standard Play API; user can disable via Settings → App → Background module updates.
5. Microsoft Store
Microsoft Store distribution uses the MSIX package format. Large asset bundles are delivered via Microsoft's Asset Delivery mechanism; no side-loaded code per Microsoft Store policies.
6. Module telemetry — cohort-aggregate only
Per Promise #5 (no cross-cell data sharing):
We collect cohort-aggregate telemetry on module download behavior: which modules are downloaded most often, how long they take to download, which modules are uninstalled when storage is constrained. This signal informs which pillars to prioritize for base-install inclusion in future releases.
We do not collect per-user module preferences for any purpose — never for advertising, never for cross-cell sharing, never for retention scoring. The cohort signal is anonymized at the source.
7. Anti-tracking commitment
The Bundles architecture deliberately avoids creating new tracking vectors. Specifically:
- No "module download" events are tagged with user identifier in analytics.
- No "pillar uninstalled" events are stored against a user account.
- Module preferences (which pillars a cell uses most) never leave the cell-side device cache.
8. Questions
For questions about app distribution specifically, write to legal@conkarma.app with subject "App distribution". For general privacy questions, see the Privacy Policy §1.