Case study
A production mobile product ecosystem for tabletop RPG players.
RPG Companion and 5e Companion combine 1M+ downloads on 5e Companion with offline-first architecture, custom data systems, subscriptions, cloud sync, sharing, migrations, app store releases, and ongoing maintenance.
Overview
The useful lesson for agencies is not that these are RPG apps. It is that they are real software products with user accounts, structured data, offline behavior, monetization, releases, support, and long-term change.
Offline-first mobile architecture
Large structured content database
Custom schema and tooling
Cloud backup and sync
User authentication
Premium gating and subscriptions
App Store / Google Play release management
Sharing links and user-generated content
Performance optimization
Migration tooling
Product complexity
RPG Companion and 5e Companion are not static content apps. They manage large structured datasets, custom user content, offline access, sharing, premium content, and workflows that players rely on during live sessions.
Monetization and platform work
The apps include premium gating, subscriptions, store releases, platform-specific behavior, privacy requirements, and the product operations needed to keep mobile software healthy after launch.
Reliability and maintenance
Long-running mobile products need migrations, support, performance work, release discipline, and careful handling of user data. That ongoing work is where production experience matters.
Why it matters for agency partners
Agency client projects often look simple in the first demo and become hard when data, auth, payments, sync, edge cases, and maintenance arrive. This product work is proof that I can handle those parts deliberately.