Finish the Module Before Inventing the Home
On September 14, 2026, I questioned whether an application's central home screen should be designed before its individual sections were useful and coherent.
September 14, 2026 · Product design note
I wasn't in a rush to design the application's main home screen. We already had modules to finish: Mail, Cloud, Projects, and others. Each would need its own workspace, actions, and eventually its own useful overview. Adding a grand Home on top could have meant designing cards for things we hadn't properly defined yet.
On September 14, I asked a simpler question: Why not leave Home for later and finish what we've started?
I considered a straightforward first screen where users could add the services they wanted to access. Then I narrowed the sequence again: get Mail right first, move to Cloud, and deal with the other modules when their turn comes. I didn't need another elaborate dashboard to tell me what an unfinished feature might someday do.
What kind of mail experience were we building?
That question changed the design. I wasn't asking for a traditional mail client that stored people's account settings and configured SMTP connections. I wanted easier access to services people already used, through their existing browser sessions. More like well-organized entry points than a second inbox trying to own their credentials.
That distinction affects navigation, expectations, and the information the application should avoid retaining. A polished screen is no excuse to collect data the product doesn't need.
We continued from an earlier design version, revised the plan, and I approved parts of the direction. That wasn't proof that every module had been implemented. The sequencing decision was clear enough, though: finish the spaces people will actually work in before designing the impressive hallway connecting them.