I recently built Cadernos e Planner Digital Brasil
👉 https://cadernoseplannerdigitalbrasil.com
It’s a digital planner system for iPad and Android — focused on helping people organize goals, habits, and daily life in a structured way.
But honestly, this project taught me something bigger than “building a planner.”
It reminded me what actually makes a product usable.
It’s not a file. It’s a system.
Most digital planners fail because they’re just… PDFs with pages.
But people don’t need pages.
They need flow.
So I stopped thinking in terms of “designing pages” and started thinking in systems:
Year → Month → Week → Day structure
Clear separation between life areas (goals, habits, finance, health)
Predictable layout everywhere
No guessing, no learning curve
The goal was simple:
Open it and instantly know what to do.
Simplicity is the hardest part
The more I worked on it, the more I removed.
Not added.
Because complexity kills usage.
I focused on:
reducing visual noise
keeping everything consistent
making each section self-explanatory
avoiding “creative but confusing” layouts
If something needed explanation, it was wrong.
The real work is structure
Even though it looks like a “digital product,” most of the effort was actually structural:
organizing reusable planner modules
keeping consistency across all versions
designing content blocks that scale
making sure everything connects logically
It felt more like system design than design work.
Top comments (0)