A native macOS command centre for your projects

Understand your code. Move faster.

DevMap helps you understand, review and manage the development projects on your Mac. It reads what is actually there, shows the evidence, and changes files only through a plan you approve.

macOS 13 or later · Apple silicon (arm64) · In development, not publicly available

Interactive product preview : captured screens, not the live app

DevMap Home: a greeting, quick actions, a Worth a look list of findings, seven workspaces with their project type and status, and recent activity.
DevMap project map: project and technology cards joined by arrows, with an inspector for the selected project in the wide layout.
DevMap Files for core-ui: a folder tree with actions to create, rename, move, duplicate or move an item to the Trash.
DevMap Review on core-ui: four findings, with the selected broken import shown with its evidence, location, a suggested next step and buttons to open the file.
DevMap Health: counts of files measured and projects scanned, severity filters, and per-project findings such as Branch has no upstream with the evidence git status shows no upstream for this branch.

Why DevMap

Your projects, understood in one place.

A development folder grows into dozens of repositories. Which have uncommitted work? What depends on what? What is taking up space? DevMap reads manifests, imports, git state and file contents to answer, and every statement comes with its evidence. Anything it cannot prove is labelled a candidate.

Beyond the basics

More of what DevMap does.

Workspaces

Every project, side by side.

One table of the projects DevMap finds, with git branch and changes, size and health, and a list of what needs attention beneath it.

Explore Workspaces
DevMap Workspaces: seven sample projects in a table with git branch, uncommitted changes, size, files and health, above a Needs attention list and a disk-use bar.

Mind Map

Read a workspace as a tree.

Fold, search and open any folder or file, with details and actions for whatever you select.

Explore the Mind Map
DevMap Mind Map of core-ui: a tree from the project root through the src folder to its files, with an inspector listing details, what the project depends on and what depends on it, and actions.

Optimize

Every suggestion shows its reasoning.

Each recommendation lists what was detected, the evidence, what could break and how it will be verified. Nothing changes until you approve a preview.

See how changes work
DevMap Optimize on core-ui: two recommendations, with the first expanded to show what was detected, the evidence, why it matters, the proposed change, what could break and how it will be verified.

History

See what changed, and when.

The latest git commit and the newest file change for each project, kept distinct. DevMap records nothing itself, and the page says so.

DevMap History: a list of last commits and file modifications across seven sample projects, each labelled Last commit or File modified with its age.

Captured from the current build on a disposable sample workspace.

Workspaces

Every project, side by side.

A single table of the projects DevMap finds, with git branch and changes, size, health and last activity, and a Needs attention list beneath.

  • Filter and sort across all projects
  • Running servers matched to their projects
Explore Workspaces
DevMap Workspaces: seven projects listed with git branch and changes, size, file count, health and last activity.

Map

See how projects depend on each other.

Select a project to see what it depends on and what depends on it, with a reason for each link. Weaker links are drawn dashed and called candidates.

Explore the Map
DevMap project map isolated on core-ui: arrows from storefront and analytics-kit point at it, and the inspector reads Depended on by 2.

Health

See what needs attention, and why.

Findings are graded and each one shows the evidence it is based on, so you can check it rather than trust it.

Explore Health
DevMap Health: counts of files measured and projects scanned, severity filters, and per-project findings such as Branch has no upstream.

Review

Findings come with evidence.

Review reads files locally and never runs your code. Confirmed findings, such as a broken import, are kept apart from candidates, such as an unused file.

Explore Review
DevMap Review on core-ui: four findings, with the selected broken import shown with its evidence and a suggested next step.

How changes work

Nothing changes until you approve it.

Every file change follows the same model. This is how the app is built, not a promise that nothing can go wrong.

  1. Plan

    Lists exactly what will be touched.

  2. Approve

    You see the preview before anything changes.

  3. Apply

    Item by item, and cancellable.

  4. Verify

    Checks the result on disk.

  5. Undo

    Supported while DevMap is open.

Read the full workflow

Explore

Go deeper into any part.

Availability

In development. Not yet publicly available.

The current build is signed with an Apple Development certificate and is not notarised, so it is not ready for other Macs. It needs macOS 13 or later on Apple silicon, and has only been tested on macOS 26.5 only. Pricing is proposed (Free, Pro and Enterprise) and nothing can be purchased.

View current progressDownload statusProposed pricing
Screenshot