Why Every Developer Should Organize Their Dock with Otterdock
Developers juggle IDEs, terminals, browsers, Git clients, and database tools daily. Otterdock groups them by project context so you stop hunting and start shipping.
You already know the feeling: a dozen icons on the Dock, three more in the menu bar, Spotlight for the rest, and you still spend ten seconds hunting for the right terminal window or the database client you had open “just a minute ago.” Development work is not one app—it is a stack. Otterdock sits on top of Apple’s Dock (it does not replace it), groups apps together with files, folders, and links, and keeps your layout local on disk. On macOS 14 and later, you get click-to-expand with no extra permissions, or hover-to-expand after granting Accessibility.
Your real daily pain
You switch between VS Code or Cursor, Xcode for native work, iTerm2 or Terminal for shells, a Git GUI like SourceTree when you want a visual graph, TablePlus or another client for databases, and one or more browsers for debugging and docs. Each tool is legitimate; together they crowd the same strip of icons. Native Dock folders help with files, but they do not mix apps and bookmarks the way a single mental “frontend” or “debug” cluster does.
What changes with groups: You name stacks after what you are doing, not what the app is called. When you open a group, everything for that mode is there—no tab archaeology, no “where did I put that compose file?”
Group: Frontend
Put your primary editor (VS Code, Cursor, WebStorm), the browser profiles you use for local dev, handoff folders, and links to staging or preview URLs. If you use design tools for UI polish, add them here so “shipping the interface” is one gesture. Otterdock supports custom icon skins so this stack can look distinct from your backend pile at a glance.
Group: Backend
Drop in terminals (iTerm2 is a common pick), API testing tools, service repos or docker-compose locations, and environment notes. Keep database GUIs like TablePlus in this cluster so you are not opening the wrong DB when you context-switch from API work.
Group: DevOps
Infrastructure folders, tunnel or VPN utilities, kubectl cheat-sheets as Markdown files, and bookmarks to dashboards belong together—not mixed with application code. When something breaks in production, you want one expandable group that says “ops,” not a Dock that looks like a junk drawer.
Group: Debug
Reserve a cluster for browsers with devtools front and center, Proxyman or Charles if you use them, log tailing terminals, and any crash or symbolication utilities you touch during investigations. Separating debug from everyday coding reduces the chance you leave half a dozen one-off windows open across sessions.
| Group | Example contents |
|---|---|
| Frontend | VS Code / Cursor, Safari or Chrome dev profile, design exports, staging link |
| Backend | Terminal, API client, TablePlus, service repo folder |
| DevOps | IaC folders, VPN, runbooks, status page bookmarks |
| Debug | Browser, proxy tool, log terminal, crash utilities |
Pricing and privacy (accurate)
The free tier includes two groups—enough to trial a split like “code” vs “ops” or “work” vs “personal tools.” Pro removes the cap for unlimited groups. Direct purchase is $6.99 one-time; a Mac App Store release is planned at $2.99 (coming soon). Configuration lives under your user Library; Otterdock does not require a cloud account for basic operation as described here.
If your Dock is a single flat row of every tool you might need this week, you are paying a small tax on every context switch. Otterdock does not write code for you—it just keeps the right stack visible when you need it. For a complete walkthrough, see our developer Mac workflow setup guide and tips on how to launch apps faster on Mac.