From a K-drama questionnaire to a full game platform.

I started with Kotlin Multiplatform, Compose Multiplatform, an MVVM-style architecture and a PostgREST-backed questionnaire. Then the edges kept moving. Authentication led to profiles. Questions led to battles, scoring and progression. Progression needed stars, hearts, gold, gems and consumables. Before long there were actors, casting, a Saga map, multilingual content and administration tools.

The questionnaire didn’t disappear. It became one mechanic inside a much larger game.

Repository boundaries such as SagaRepository, EconomyRepository,VitalsRepository, ProfileRepository, AuthRepositoryand ActorRepository emerged as the project grew—not as a grand plan on day one, but as pressure from the game itself.

A bigger game needs much more than code: questions, translations, actors, poses, sprites, maps, backgrounds, minigame assets, metadata and progression configuration. A separate WebAdmin became a serious part of the workflow, combining React, Vite, Supabase JS, Framer Motion, Sharp, background-removal tools, Node scripts, Python utilities and AI-assisted generation and translation.

On February 1, the repository gained an Animation Viewer with drag-and-drop sprite-sheet inspection, pixel scanning, trimming and frame-consistency tools. It lived inside the KDrama Director WebAdmin at first. That was the beginning of what became Sprite Studio—and, eventually, CastStride.

Mobile gameplay should not freeze because a train enters a tunnel. I introduced SQLDelight for local persistence while Supabase remained the remote backend. That sounds simple until local progress, account linking and rewards meet: data needs reconciliation, assets need fallbacks, and offline rewards cannot be trusted blindly.

This period also brought an offline Saga map, authentication and account-linking work, Cloudflare Turnstile, server reconciliation, ad-verification planning and more Kotlin Multiplatform platform work.

I adopted clean-architecture principles without following a template blindly: keep the domain independent, define boundaries, make infrastructure replaceable and stop every feature from knowing about the entire application.

Gradle architecture checks now catch boundary drift. Fake repositories, deterministic time providers, ViewModel unit tests, UI regression tests and Compose UI tests make the modules safer to evolve. Play Asset Delivery joined the release pipeline as the game’s asset surface grew.

Once a game has currencies, progression and rewards, backend security becomes part of game design. I continued moving valuable operations behind RPC guardrails, stronger Row Level Security, validated rewards and controlled backend operations.

Supabase provides PostgreSQL, PostgREST, authentication, Realtime, Storage, database functions, Edge Functions and scheduled jobs. Schema compatibility checks and live-system protections help ensure that the convenient client experience does not become the source of truth for valuable persistent state.

A large part of game development happens outside the executable. The WebAdmin grew workflows for question QA, translations, map templates, nodes, minigames, item assets, actor poses, avatars, casting boards, publishing and Supabase synchronization.

Instead of treating every new piece of content as a code change, I started building systems that produce and validate the content the game needs.

Offline-first networking, local assets, background synchronization, concurrency testing and reusable content bundles became normal. Actor and avatar pipelines matured alongside unlock policies, Live Wave scheduling and promotional tooling.

By now KDrama Director contained drama progression, trivia battles, actor collection, casting and synergy, avatars, awards, fan systems, minigames, Live Wave, currencies, unlock systems and multilingual content. The questionnaire was still there—now surrounded by the world it had helped create.

The app stays local and offline-first where that creates resilience, while sensitive state increasingly flows through purpose-built authoritative server operations: profile preferences, owned actors, casting, progression, rewards, gameplay settlement and sessions.

Offline-first and server-authoritative don’t have to be opposites.

A responsive client can still let the backend own valuable persistent state. Production security rollout, staging validation, settlement, content synchronization, localization, release diagnostics, Google account handoff and Android release work are turning a working game into one prepared for real players.