Muhammad
Usama Abid

Problem: Build size and asset loading were killing first-session retention on low-end Android devices.

Approach: Reworked asset pipeline with Addressables, compressed texture formats per tier, and async scene loading.

Result: Load time dropped ~40%; first-day retention improved alongside better store-page conversion.

Problem: Every seasonal event required a one-off backend integration and duplicated client code.

Approach: Designed a config-driven event system with Firebase Remote Config + PlayFab, plus a single client-side manager.

Result: Events went from weeks to days; designers could tune live events without client builds.

Problem: Combat logic was scattered across MonoBehaviours, making iteration slow and bugs hard to reproduce.

Approach: Moved to a hierarchical state machine with clear input buffering, animation callbacks, and exposed tuning variables.

Result: Combat felt more responsive, tuning cycles shortened, and the team could add new moves without touching core systems.

Problem: A growing team was shipping with inconsistent code style, merge conflicts, and no profiling baseline.

Approach: Introduced GitFlow, code-review gates, Rider/VS settings, and automated profiling checkpoints in the build pipeline.

Result: Fewer regressions, faster onboarding, and predictable sprint velocity across 5–9 person squads.