ORIGINAL WORK
We show what we made, what inspired it, and where the boundary is.
Hadtoo's originality is in the games we design and implement: their rule combinations, interaction models, scoring, interfaces, pacing, visual systems, and the software that makes them playable. We do not treat broad genres or common mechanics as if we invented them.
WHAT IS FIRST-PARTY
Game systems
The specific rule loops, action timing, scoring, pressure systems, and table information used by each Hadtoo title.
Software
The playable browser implementation, responsive interfaces, state handling, round resolution, onboarding, and feedback are built as Hadtoo product work.
Design documentation
Rules pages, design explanations, development notes, and changelog entries describe the actual product decisions behind the games.
Presentation
Each game's visual hierarchy, board layout, decision surfaces, transitions, and same-room interaction flow are part of the product design.
WHAT WE DO NOT CLAIM
Genres and building blocks belong to a much larger history.
Property games, word games, hidden information, heists, betrayal, territory control, drafting, simultaneous choice, and push-your-luck all predate Hadtoo. We use those ideas the way game designers use established vocabulary: as ingredients. Our claim is about the specific systems and implementation built from them, not ownership of the ingredients themselves.
HOW TO REVIEW THE WORK
Start with a playable title, then read its guide.
The strongest evidence is the product itself. Each guide explains the current loop, identifies the Hadtoo-specific systems, and states the genre boundary so a reviewer does not have to infer originality from a full-screen game alone.
DEVELOPMENT HISTORY
The work changes in public.
Hadtoo keeps a development log tied to real product changes: portfolio consolidation, rule refinement, onboarding improvements, table layouts, new titles, and system tuning. That history documents an evolving first-party product rather than a static page assembled only for advertising review.
Read the development log →