The Architect of
Playful Systems
Games are not entertainment—they are interactive art systems. Each mechanic is a brushstroke, each constraint a creative catalyst. My work bridges computer science precision with fine arts intuition to build experiences that feel inevitable.
From the weight of a puzzle piece to the velocity of a perfect jump, we design emotional physics—mechanics that evoke specific feelings. The goal isn't just to occupy time, but to create a space for discovery.
Start a Conversation
Typical response within 24h • No spam, just clarity
SYSTEM_NODES: 3 // CONNECTIONS: 8
From Concept to Code:
The Development Ethos
Every game begins as a hypothesis. We build the test environment. This is the pipeline that turns a whiteboard sketch into a running APK, where technical discipline meets creative intuition at every gate.
Primary Constraint
Mid-Tier Android Focus
All systems validated on Snapdragon 665 (2019) before targeting flagship performance.
Ideation & Prototyping
One-week sprint in Unity or Godot. The "fun" question is answered before code is written.
Engine Lock
Decision point: Custom rendering or off-the-shelf? Based on art style and performance budget.
Iterative Polish
Juice passes, touch feel refinement, and battery optimization cycles.
Quality Gate
Final pass: "Is it fun?" meets "Does it survive 90 minutes on a mid-range device?"
The Failure Modes: What Derails Mobile Game Projects
Nine years in Android development has taught me to spot these patterns early. Here’s the autopsy report.
Pitfall #1
Designing for Your Own Device
Using a flagship as your test bench. Avoid it: Mandate daily testing on a 3-year-old, 720p device.
Pitfall #2
Feature Creep Without a North Star
Adding mechanics that don't serve the core emotional hook. Avoid it: Write the one-sentence "feeling" on the prototype folder.
Pitfall #3
Ignoring Touch Latency
A 100ms delay feels like a broken button. Avoid it: Use input callbacks, not polling; optimize render thread.
The Necessary Trade-offs
Visual Fidelity
The choice isn't poly count. It's texture resolution vs. shader complexity on battery life.
Feature Richness
A seamless UI animation might take 3 days. Is it worth 3% of total dev budget?
Micro-Scenario: The Portrait Puzzle
Client: A solo dev with a vertical slice for a portrait-mode puzzle game.
Constraint: Must run on a Galaxy J7 Prime (2016, 2GB RAM).
Reality Check: The physics engine was too heavy. Instead of cutting features, we pre-baked the puzzle solutions into static nodes, turning a physics problem into a lookup table. The "juice" came from screen-space distortions, not real-time simulation.
Outcome: 60 FPS stable. Download size under 40MB. The core loop remained intact.
The Brandixo Pro
Visual Language
Not a style guide—a visual grammar. Every element serves a functional or emotional purpose. Here’s the palette, the type, and the motion principles.
Crimson Accent
#e94560 — Used for critical paths & emotional beats.
Aa
Space Grotesk
Icon: Hand-Drawn
2px stroke, imperfect, not stock.
Surface Texture
CSS grain, 2% opacity.
The Glossary: Terms & Intention
Emergent Gameplay
Not just random events. It's designing rules that allow players to create their own stories within the system.
"The story is in the player's head, not the script."
Juice
The feedback layer. Screen shake, particle sparks, sound effects, haptics. The polish that makes interaction feel delightful, not just functional.
"If the mechanic is a 'click,' juice is the 'satisfaction.'"
The 90-Second Rule
If a player isn't engaged in the core loop within 90 seconds, the onboarding has failed. We teach by doing, not by text.
"The best tutorial is an invisible one."
Ready to Build Your
Playful System?
If you have a concept, a constraint, or a frustrating problem, let's talk. I don't take on every project, but I give every serious inquiry the attention it deserves.
Brandixo • Istiklal Caddesi No: 123, Beyoğlu, Istanbul