The product problem
A lot of coding websites speak as if the user is already a developer. Others rely on streaks and competition to keep people moving. Both can make the first step harder than it needs to be.
I wanted to try a gentler starting point: small logic problems that children can understand quickly and solve at their own pace.
Designing for confidence
I kept the instructions short, made feedback immediate, and removed anything that competed with the puzzle. Progress comes from understanding the idea, not maintaining a streak.
- Use plain language before introducing technical vocabulary.
- Keep each challenge focused on one idea.
- Offer quick feedback without turning mistakes into failure states.
- Stay free and ad-free so attention remains on learning.
A focused product experiment
I came up with the concept, interaction model, visual language, and implementation. Keeping the scope small gives me room to test how tone and feedback change the way a learning product feels.
It also reminds me that software does not need more mechanics to become engaging. Sometimes leaving something out is the better product decision.