Work / DDrovrCase study 01

Product / UX / Native app / Brand / Web

DDrovr

Product

Native macOS app for DDEV

Role

Concept, UX, interface, development, brand, website

Year

2026

DDrover Project Overview Screen
DDrover Project Overview Screen
01 / Problem

DDEV is powerful.
It also lives in the terminal.

Everything DDEV knows about a project — status, URL, PHP version, database, web server — is available from the command line, but not in a shape people can scan at a glance. [EXPAND — who this was for and what got in their way.]

02 / ConceptData becomes objects

Same DDEV.
Better view.

Status becomes an indicator. Project becomes a row. URL becomes an action. Runtime information becomes structured UI. Commands become controls.

zsh — ddev$ ddev listPROJECTSTATUSURLPHPDBWEBproject-arunninga.ddev.site8.3mdbnginxproject-bstoppedb.ddev.site8.2mysqlapacheproject-crunningc.ddev.site8.3pgnginxproject-dpausedd.ddev.site8.1mdbnginx$ ddev start project-bSTATUS → INDICATORPROJECT → ROWURL → ACTIONRUNTIME → STRUCTURED UICOMMANDS → CONTROLSDDrovrAPP SHELLPROJECT LISTCONTROLS
03 / UX + Application
DDrovr - Project Log View
DDrovr - Project Settings View
DDrovr - New Project View
DDrovr - No Selection
04 / Brand + WebsiteExploded

Then we branded it,
and built the site.

[DDROVR MARK]01 IDENTITYAPP ICON02 ICONAaTYPE SYSTEM03 TYPOGRAPHY04 SCREENSHOTSSAME DDEV.BETTER VIEW.05 MESSAGING06 WEB COMPONENTS07 DDROVR.COM
DDrover website
05 / Launch

We designed the product. Built the product. Branded the product. Built the site.

[LAUNCH — where it shipped, how it's distributed, what's next.]

Have an idea
that needs building?