WarStrike

WarStrike is a mobile FPS engineered to reach 10M+ downloads while holding a 4.4-star average rating at scale. Mobile shooters live or die on two things: frame rate and content cadence. Players forgive simple graphics, but not a gunfight that stutters, and they churn the moment the content well runs dry. WarStrike was built full-cycle to win on both, and is still in active LiveOps.

The brief was to build an FPS that felt responsive on the hardware most of the world actually owns, budget Android devices in the 2-3GB RAM class, while supporting a content pipeline that could ship new weapons, missions, and events on a regular cadence without engineering involvement each time.

KEY REQUIREMENTS

• Performance floor: console-style shooter feel, weapon feedback, particle-heavy combat, and multiple AI enemies on screen, inside a low-end Android frame budget.
• Content scalability: missions, weapons, and progression had to be data-driven so designers could ship content without code changes or store releases.
• Monetization without rage: a shooter economy that earns through progression and cosmetics rather than pay-to-win mechanics that tank the store rating.

• Set a hard 60 FPS budget for the minimum-spec device and profiled against it continuously, not at the end of the project.
• Draw-call discipline: aggressive batching and atlasing across weapons, environment sets, and VFX to keep the render thread inside budget on entry-level GPUs.
• Object pooling everywhere it matters, projectiles, muzzle flashes, impact effects, and enemies are all pooled, eliminating the garbage-collection spikes that are the number-one cause of mid-combat stutter in Unity shooters.
• LOD and culling tuned per level with shader variants stripped for low-end tiers, plus automatic quality tiering that detects device class at first launch and sets resolution scale, shadows, and particle density with no settings menu required.
• A content pipeline designers can run: missions, weapon stats, enemy waves, and event configs live in ScriptableObject-driven data with remote-config hooks, so the live team ships events and rebalances the economy without touching code or waiting on a store release.
• Monetization tuned with data, not guesses: full-funnel analytics from day one, rewarded and interstitial ads placed at natural session breaks rather than mid-action, and IAP centered on progression accelerators and cosmetics, with rating protection treated as a monetization feature.