Core design · all games
MDA framework
A way of breaking a game into mechanics (the rules), dynamics (what happens when people play by them) and aesthetics (how playing feels).
Also called: mechanics dynamics aesthetics, mechanics, dynamics, aesthetics
MDA stands for mechanics, dynamics and aesthetics. It was set out by Robin Hunicke, Marc LeBlanc and Robert Zubek in a 2004 paper that grew out of workshops at the Game Developers Conference. It is one of the most cited frameworks in game design teaching.
Mechanics are the rules and parts the designer builds: a timer, a grid, a price. Dynamics are the behaviour that comes out of those rules once real players use them: rushing, hoarding, trading. Aesthetics are the emotional result: challenge, discovery, fellowship, expression and so on. The paper lists eight kinds of fun as a starting vocabulary.
The key idea is perspective. A designer works from mechanics toward feelings, while a player meets the feelings first and may never think about the rules. Starting from the feeling you want, then asking which dynamics would produce it and which mechanics would produce those, is a practical way to plan a feature.
In mobile games
MDA is a good lens for monetization and retention features. A countdown timer is a mechanic; the dynamic is players returning or paying to skip; the aesthetic might be anticipation, or it might be pressure. The same mechanic can feel generous or pushy depending on the dynamics it creates.
What to watch for
- Treating it as a checklist. MDA is a way to ask questions, not a formula that produces a design.
- Skipping the dynamics layer. Most surprises in playtests happen there, between the rules you wrote and the feelings you expected.
