Skip to content
WalkRPG Wiki

Stack + audience + monetization

D-008: Stack + audience + monetization

Round 2 of /research full-app-scope:

  1. Backend stack = GCP-native. Cloud SQL (Postgres), Cloud Run (NestJS), Firebase Auth, Firebase App Check (attestation), Memorystore (Redis for streaks/presence), Cloud Run-based WebSocket or GKE Autopilot once realtime ramps. Cost-disciplined at start, scaling vertically. EU residency enabled at project init (see D-009).
  2. Mobile stack = native dual. Swift iOS + Kotlin Android. Sibling repo walkrpg-mobile. Best integration for HealthKit / Health Connect, Apple DeviceCheck / Play Integrity. WatchOS + Wear OS native trivial (deferred to Phase 13 per D-009). Supersedes D-005 — Phase 4 (bootstrap) is done at commit 968865a, the D-005 re-open condition is met. Roadmap phase 10 collapses into D-008.
  3. Monetization = hybrid premium + sub. Upfront $9.99-$14.99 (final pricing TBD) + optional $2.99/mo guild master subscription unlocking custom emblems, larger guild member cap, regional event hosting. Apple App Store 3.1.2 compliant: sub delivers ongoing server-side value (guild infrastructure). Google Play has no equivalent restriction. Core gameplay is NOT behind sub.
  4. Audience + launch geography = hardcore RPG / PoE-inspired, global, EN+PL day 1. Marketing in PoE community channels, walking-RPG niche, gaming press. Tonal expectation per D-006 (Pratchett warmth + epic stakes) coexists with hardcore mechanics — depth + intelligence in lore, never casual fluff. narrative-designer must hold the line on tone in rounds 3+.

Reasoning: Restrictive anti-cheat (D-007) requires platform attestation APIs — native dual is the cleanest integration. GCP-native chosen for cost discipline + EU residency support (per D-009). Hybrid monetization sustains 24-36 month dev cycle without compromising hardcore audience trust.