Inside the
implementation.

• Structured events carry flow step, chapter, level, session timing and access context.
• A bounded startup queue retains events while Firebase initialises; local counters remain available if the SDK is unavailable.
• Background/resume events and a saved last-step checkpoint help investigate where a session stopped.

I use last-step checkpoints alongside event timing to investigate the player journey, and keep device-side validation separate from cloud reporting.

• Google Mobile Ads rewarded-ad lifecycle, readiness, retry handling and reward callbacks.
• Unity IAP integration with store-localised prices, purchase restoration and repeat-purchase guards.
• Premium entitlement checks before ad startup, so full-access users bypass the advertising path.
• Parental purchase entry and privacy-options UI.

I keep ad requests, impressions, earned rewards and purchase restoration distinct in analytics, so each stage of the monetisation flow can be investigated separately.

• Completed-level IDs, chapter progression, collections and sticker rewards.
• Persistent tutorial, character, language, audio and premium state.
• First-session detection that accounts for existing saved player data.
• Editor-only free-user simulation without deleting saved purchases or progress.

• Tutorial voice-over sequencing, music ducking and animated guidance.
• Idle hints and timers owned by the relevant gameplay flow.
• CSV-based localisation and runtime text updates.
• Settings, reward screens, chapter transitions and UI animation.

• Grid shuffling, piece swapping, connected-piece groups and hint operations in a pure C# board model.
• Drag-and-drop input connected to the puzzle activity.
• A level-flow coordinator for introduction, puzzle, question, mini-game and reward steps.
• ScriptableObject definitions for chapters, levels, difficulty and songs.
• Chapter progress, stars, badges and song unlocking in versioned save data.
• A service bridge for Firebase Analytics, rewarded ads and full-game purchases.

These notes describe the current development project; the store release can be an earlier version.

• Difference-level building and extraction tools for puzzle content.
• Scene builders, content validators and custom editor windows in ongoing prototypes.
• Edit Mode and Play Mode test suites around state, navigation, saves and gameplay rules.
• Inspector diagnostics and development-only controls for reproducing player states.

• Application state machines, scoped composition and screen navigation.
• Coordinated run checkpoints, atomic file replacement and previous-save recovery.
• Data-driven dialogue, conditional hotspots and interaction workflows.
• Inventory, puzzle-state changes and input locks during interaction sequences.

I am developing these foundations alongside the playable experiences, with ongoing work on state transitions, recovery and content workflows.

• MediSim: my Unity VR master’s project exploring ECG interpretation and clinical skill training on Meta Quest 2.
• CyberQuest: game design and supporting software development, including selected code, screens, mechanics, 3D models and environment work.
• Paper Basket: Java/JBox2D projectile interaction, collisions, obstacles and scoring.