All your code projects, one window.

Context

When you juggle dozens of repositories, your day is spent shuttling between the file explorer, the terminal and the IDE. KodeDock starts from a simple observation: these repetitive actions (open, run, find, create) deserve a single entry point. The goal was to build a genuinely native launcher — not yet another web wrapper — aimed at developers and respectful of their reflexes: keyboard shortcuts, command palette, system terminal, Git integration.

The approach

I designed KodeDock as a calm, legible space where every project, every workspace and every action has its place without visual clutter. The challenge wasn't to stack up features, but to set a hierarchy: a sidebar as a permanent anchor, views that breathe, and micro-interactions (inline renaming, command palette, dark mode) that give the feel of a native tool — fast and carefully made.

1. Design the journeys, not just the screens

From the full-screen onboarding to the project creation wizard, every flow is designed to guide without friction. Scaffolding shows its progress live rather than an opaque spinner: making what's happening visible is reassuring and gives the flow a rhythm.

2. The details that make it feel native

Inline renaming (Enter / Escape), keyboard navigation, a ⌘K palette, carefully designed empty states: these reflexes borrowed from the best dev tools are what make an app feel as native as it is.

3. Consistency between design and code

On the technical side, I carried that same standard into the architecture: three cleanly separated Electron processes, a typed IPC contract as the backbone, and deliberately lightweight navigation (a state machine rather than a router). Visual rigour carried through into the rigour of the code.