Mechanical thinking without slot-machine vocabulary
Mechanics are not “hooks.” They are agreements: if a player does A under condition B, the world responds in a way C that can be predicted after a few trials. The moment a game asks someone to play without a usable model, it asks for superstition. Superstition can be monetized, unfortunately, and that is why the industry conflates mystery with depth. Aperture North looks for depth that survives explanation. A child should be able to say how a run went wrong without needing a data export. A grown adult should be able to leave a game without feeling the rules were smuggled in through the carpet.
Inputs, surface, and the thumb economy
On a phone, the mechanical layer begins at the size of a gesture. A mechanic that needs three distinct simultaneous touches might be a fascinating experiment on a desk with a test harness; in a subway it is a quiet exclusion of anyone whose grip is not casual. A good mobile mechanic is honest about the surface it sits on, which is why the best work often reuses a small vocabulary of swipes, taps, and long presses until those gestures feel as distinct as words in a sentence. The player then reads complexity not from a crowded HUD, but from the sequence and timing of familiar verbs, the way a paragraph reads without redefining every word.
Resources, sinks, and the feeling of a fair sink
Resources—currency, energy, time-gated items—are not evil by nature. A sink is. A well-designed sink gives a player a reason to care about a number without shaming them for the moment they do not. The uncomfortable truth is that many sinks are tuned by comparing spreadsheets first and feelings second, which inverts a craft process. A fair sink explains itself in a single sentence, even if the sentence is a little sad. An unfair one hides in multi-step conversions and surprise conversions after an update, where even diligent players feel duped. If your mechanic depends on a sink that you cannot read aloud in a calm voice, that is a signal worth heeding, not a challenge to your cleverness.
Failure as information
When a run fails, the best games teach. They do not always teach through text; sometimes a subtle animation or a small audio dip explains what rule was tripped. The educational stance here is important: a failure you cannot attribute becomes luck, and luck without charm becomes irritation. A mobile session might be the last moment before sleep; irritation lands heavier there than at a PC desk. Mechanical designers on small screens often have to fight for one extra line of copy on a failure state because a producer assumes text slows things down. A precise line, however, is faster than a second confused attempt.
Depth through variation, not through opacity
We prize mechanics that can generate novel situations with a small ruleset, the way a good card game does. Opacity, by contrast, tempts a team with the illusion of depth because a player can spend a long time confused. The difference between variation and opacity is testable: in variation, a player can narrate a new situation back to a friend. In opacity, the friend nods absently. If your playtests produce stories, you are in healthier territory, even if the numbers are not yet where you want them. Stories are a lagging metric of legibility, but they are real.
Interlude: a note for educators
If you teach, ask students to write a two-paragraph “contract” between their game and a player, listing the verbs and what each verb never does. The exercise is simple and sometimes embarrassingly hard. The difficulty is the point. When the contract is shaky, the mechanic list is not ready for art yet, and that saves months of re-tracing. We share these exercises in the spirit of craft, not certification; there is no exam at the end, only a studio that will sleep a little better on shipping week.