Game UI/UX Designer

Context

I joined Modern Ops before launch, when the game was already well into production. At that point, the existing UI and UX had been shaped mostly by a 3D artist and a programmer, so my first task was to rethink the interface as a dedicated UI/UX designer.

My role

I was responsible for UI/UX across the product and gradually expanded beyond interface design into broader game and product decisions. I worked on visual direction, player flows, game systems, retention-focused features, research, balance, and ongoing live development.

Challenge

The main challenge was not simply to make the interface look better. The game already existed as a working product, so every change had to improve clarity and usability without breaking established mechanics, production constraints, or the pace of development.

What I changed

• Reworked the visual direction and information hierarchy of the interface.
• Improved player flows and mobile usability across core game systems.
• Proposed and helped shape new features and retention-focused mechanics.
• Worked across HUD, lobby, progression, weapons, shop, leaderboards, onboarding, combat UI, multiplayer flows, and meta systems.
• Continued supporting the product after launch and iterating on live features.

Systems & production

I worked closely with developers throughout implementation and used Unity directly to test, refine, and review UI in-engine. I prepared assets and states, considered responsive and adaptive layouts, and helped find practical solutions when design intent and technical constraints did not line up cleanly.

Result

Modern Ops became the studio’s most successful title and grew to 100M+ downloads. I continued contributing to its UI/UX, feature development, and live support as the product evolved.

Context

Fire Strike was a new mobile FPS where my role expanded far beyond a typical UI/UX scope. After working across existing products, I took on much broader ownership of a new game and became the primary design owner for the player experience.

What I owned

• End-to-end UI/UX across the game.
• Core and meta game systems, flows, and features.
• Progression and economy logic.
• Weapon balance and tuning.
• Store offers and monetization presentation.
• Naming and content planning.
• Ongoing product support after launch.

Challenge

The project required me to make decisions across multiple disciplines at once. Instead of receiving a defined feature and designing its interface, I often had to understand the problem first, shape how the system should work, and then turn it into something clear for the player and realistic for the team to build.

Production

I stayed hands-on throughout production, working directly in Unity, testing features, reviewing implementation, preparing assets and states, and collaborating with developers on technical and responsive UI solutions.

What I learned

Fire Strike strengthened how I think about UI as part of the game system itself — connected to mechanics, progression, economy, monetization, and production constraints.

Result

Fire Strike shipped and reached 10M+ downloads on Google Play.

My role

I was responsible for the UI/UX direction, interaction flows, visual exploration, and interactive prototyping.

Project status

Development stopped during the gameplay prototyping stage, so the work shown here represents the UI/UX direction developed for the project.

The problem

Static mockups hide the hard questions: states, transitions, edge cases, how a screen feels in motion. Getting a working prototype usually means waiting for a developer.

What I built

• A custom AI design agent, set up for specific tasks: UI concepts, asset generation, prototype building and design review.
• I work with agents like Claude and Codex to turn designs into working, code-based prototypes.
• Clear rules for the agents: my design system, references and quality bar, and every fact checked by me.

Proof

• This site: art direction, assets and code produced by agents I direct; every fact checked against my CV.

What it changes

Faster iteration, testing ideas in motion before production, and clearer handoff: the team sees a working prototype, not only static screens.