Every feature should serve a purpose.
We start with what the developer is trying to improve, then build the logic and controls that meaningfully support that goal.
LizardHouse creates polished Unity tools that give developers more control over the product moments where timing, behaviour and implementation choices can influence results.
What we stand for
The developer outcome is the reason the tool exists. The player experience shapes how that outcome is pursued.
That means giving developers more control while accounting for timing, context and real player behaviour, so important interactions can work better without becoming careless, intrusive or arbitrary.
Our principles
Quality is not one headline feature. It is the sum of the decisions that make a system useful, understandable, dependable and effective in the product around it.
We start with what the developer is trying to improve, then build the logic and controls that meaningfully support that goal.
Developers should know what a tool will do, why it will do it and what needs their attention.
A system can work technically and still perform poorly if it appears at the wrong moment, ignores player behaviour or creates unnecessary friction.
Strong defaults, careful validation, predictable behaviour and honest limitations matter as much as the headline feature.
The long-term direction
Future LizardHouse products may solve very different jobs, but they should share the same approach: start from a meaningful developer outcome, account for real player and platform behaviour, and give developers clear control over the system behind it.
Growth should expand what LizardHouse can help developers achieve without turning the product family into a collection of disconnected features. Each tool should stay focused, complete and worth learning.
See our productsStart a conversation
Suggest a future Unity product, explore a collaboration or tell us about a workflow or player-facing system you think could work better.
Contact