Clarity
The game should be the interesting part, not working out the interface. Hierarchy, states, and controls are made legible first, so attention can go to the actual problem.
Approach
Designed to be finished.
A Lambquil game gives you one thing to do, makes it plain how it works, and lets you stop once it is done. Four principles decide what goes in and what stays out.
Small is not the same as slow.
The reset comes from the size of the problem, not the speed of it.
One Lambquil game may run on a timer while another has none at all. What they share is scale: for a few minutes the world narrows to one activity with a clear edge around it, and that is where the appeal is.
Difficulty and time pressure are fair when they belong to the game. A countdown that makes a round tense is part of the design. A countdown that exists to make you come back tomorrow is not.
Four principles
What the design is measured against.
Self-contained design
Each game is one bounded activity with a beginning and an end. Scope is decided early and held to, because the boundary is the point rather than a limitation.
Purposeful interaction
Animation, sound, colour, and feedback each need a reason to be there: to explain, confirm, or guide. Anything that only decorates gets cut.
Respect for time and attention
The reason to keep playing should be the game. No streak to protect, no timer running while you are away, nothing built to make stopping feel like a loss.
In practice
Accessibility and polish are engineering.
They are decided while a game is being built, not added once it works. The list is unglamorous, and it is most of the difference between a game that is pleasant to use and one that is not.
- Readable type and unambiguous visual states
- Controls that behave the same way on every device
- Feedback that confirms an action without demanding attention
- Colour that still works for low vision and colour blindness
- Adjustable text size, motion, and sound
- Rules taught by playing rather than by reading
Next
About the company