What are the must‑have Mac apps for modern developers?

Mac
1

I just switched my main dev machine to a Mac and I’m overwhelmed by the number of tools out there. I’m looking for must‑have macOS apps for developers: code editors, terminal tools, database clients, API testers, productivity utilities, and anything that really improves daily coding work. What are your essential Mac development apps and why do you recommend them?

2

Favorite Mac Apps For Developers (That I Actually Use)

I’ve bounced between Windows, Linux, and macOS for years, and I always end up back on the Mac when I want to just sit down and build stuff instead of fighting my setup. Here’s a mix of tools I keep installed on my dev machine, including one a lot of people sleep on: Commander One.

File Management & General Workflow

Commander One

If you grew up on Total Commander, Midnight Commander, or any of those old school dual-pane file managers, you’ll probably get why I like this one –Commander One.

What I use it for:

  • Dual-pane layout for quick drag & drop between folders
  • Browsing remote servers without opening a full-blown IDE
  • Quickly digging through build artifacts, logs, and random junk that piles up in ~/Library
  • Keyboard-heavy navigation so I’m not constantly reaching for the mouse

Finder is fine for normal people. For dev work, especially when I’m shuffling project folders, unpacking archives, and cleaning up temp files, Commander One just feels faster.

Terminals & Shell Tools

  • iTerm2
    Way more customizable than the stock Terminal. Split panes, profiles per project, and great search. I keep one window per repo, each with multiple splits for tests, logs, and the app process.

  • Warp (if you like more modern stuff)
    Command history with a nice UI, workflows for common commands, and sharing terminal sessions. Honestly, I was skeptical at first, but hotkeys + AI suggestions are surprisingly useful for obscure CLI flags.

  • Homebrew
    I basically treat this as my “App Store for dev stuff”:

    • brew install node git wget gh
    • brew install --cask iterm2 visual-studio-code docker
      You can set up a new Mac in under an hour if you script your brew installs.

Editors & IDEs

  • Visual Studio Code
    Great for web, scripts, and random experiments. Tons of extensions, including:

    • GitLens
    • Prettier / ESLint
    • Docker / Remote Containers

  • JetBrains IDEs (IntelliJ, WebStorm, PyCharm, etc.)
    If you’re in a heavy codebase or working with Java/Kotlin/TypeScript/Python, these are still hard to beat for refactoring, navigation, and debugging.

  • Xcode
    Kind of unavoidable if you’re doing any iOS/macOS work. I’d never install it unless I had to, but if you do Apple platforms, you have to.

Databases & Backend Stuff

  • Postico / TablePlus / DataGrip
    For database-heavy projects, having one good SQL client is essential. I keep at least one of these around to:

    • Inspect schema changes quickly
    • Run ad-hoc queries without pulling in the full backend
    • Compare staging vs prod data visually

  • Docker Desktop
    Not my favorite app resource-wise, but containers make local dev setups so much cleaner than installing everything bare on macOS.

Git & Collaboration

  • Fork or Sourcetree
    I still do most of my Git work in the terminal, but having a GUI is nice for:

    • Reviewing big diffs
    • Handling nasty merges
    • Visualizing branches

  • GitHub Desktop
    Good enough for simple workflows, especially if you’re living in the GitHub ecosystem.

Productivity & “Glue” Apps

  • Raycast or Alfred
    You can think of these like Spotlight on steroids:

    • Launch apps
    • Trigger scripts
    • Search docs / bookmarks
    • Custom workflows for dev tasks (run tests, open specific projects, etc.)

  • Rectangle
    Window snapping with keyboard shortcuts. For multi-monitor setups, this is mandatory unless you enjoy dragging windows around all day.

  • Dropover / Yoink
    Temporary “shelves” for files. Super helpful when you’re uploading logs, screenshots, or test builds to different sites or chat apps.

Browsers & Dev Tools

  • Safari + Chrome/Chromium + Firefox

    • Safari for battery and real-world Mac users
    • Chrome/Chromium for devtools and extensions
    • Firefox to see what breaks in a different engine

  • Browser devtools are still underrated. Network tab + performance tab will instantly tell you what’s wrong with half of “slow” web apps.

Random But Surprisingly Useful

  • Kaleidoscope / Beyond Compare
    For visual diffing: images, text, folders. Super useful for config changes, Info.plist diffs, or checking generated files.

  • CleanShot X / Shottr
    Screenshot tools with annotations, scrolling capture, and quick sharing. Great for bug reports and documenting weird UI behavior.

If you’re setting up a new Mac for development, I’d honestly start with:

  1. Homebrew
  2. iTerm2 (or Warp)
  3. VS Code or a JetBrains IDE
  4. Docker Desktop
  5. Commander One for file management
  6. A window manager like Rectangle
  7. One solid DB client

You can build out the rest as your projects demand it, but that stack covers about 90% of what I end up doing on a daily basis.

2 Likes
3

You’re not alone, macOS dev setup feels like walking into Costco without a list.

I mostly agree with @mikeappsreviewer, but here’s a slightly different, opinionated stack, trying not to repeat the same stuff.

1. Code editors & IDEs

I split by use case:

  • VS Code
    Great for JS/TS, Go, Rust, and “I just cloned this random repo and need to poke around.”
    Must-have extensions:

    • Error Lens
    • GitHub Copilot or Codeium (if you like AI help)
    • REST Client (so you can hit APIs from inside the editor)

  • JetBrains Fleet
    If you like the JetBrains brains but want something lighter than IntelliJ / WebStorm, Fleet is actually decent now. I use it when VS Code starts to feel like a Chrome tab hoarder.

Tiny disagreement with @mikeappsreviewer: if you are in one main ecosystem (say all-in on TypeScript or Python), I prefer a single tuned IDE rather than juggling multiple JetBrains products.

2. Terminal & shell

Everyone says iTerm2 or Warp, so to avoid repeating:

  • Kitty
    GPU-accelerated terminal, fast, very configurable. Great font rendering, ligatures, and plays nice with multiplexers.
  • Alacritty
    Even more minimal. No tabs, no fluff. Pair it with tmux and you’re done.

I actually prefer Kitty + tmux over fancy “smart terminals.” Less magic, more predictable, survives SSH and long running sessions better (for me, at least).

CLI essentials via Homebrew, but here are a few that people skip:

  • eza or lsd instead of ls
  • bat instead of cat
  • fd instead of find
  • rg (ripgrep) for fast search inside code
  • zoxide or autojump for jumping between directories

These four alone save stupid amounts of time.

3. File management

Finder is… fine, until it’s not.

  • Commander One
    If you’re doing serious dev on macOS and juggling local + remote files, a dual pane file manager is a huge quality of life upgrade.
    Commander One is especially nice for:
    • Dual-pane layout with keyboard shortcuts
    • Mounting FTP / SFTP / WebDAV like normal folders
    • Quickly navigating ~/Library, logs, build dirs without grinding through Finder’s UI

It’s honestly one of those “you don’t know you needed it” tools until you start moving project assets around all day.

I disagree a bit with the “Finder is fine for normal people” take: Finder becomes painful as soon as you’re diffing folder trees, copying builds, and cleaning temporary junk daily.

4. Database clients

Try to pick just one good cross-DB client at first:

  • TablePlus
    Fast, not bloated, supports Postgres, MySQL, SQLite, Redis, etc.
    Nice for: quick schema inspect, manual migrations, data peeking in staging.

If you are doing “serious” DB work or lots of different engines:

  • DataGrip
    Heavier, but fantastic autocomplete, introspection, and refactoring. Treats DBs a bit like code.

If you only care about Postgres, Postico is fine, but I’d start with TablePlus so you do not box yourself in.

5. API testing & backend debugging

Surprised this is still not a default for folks new to Mac:

  • Insomnia
    Cleaner than Postman in my opinion, great for REST / GraphQL.
    Features I lean on:

    • Environment variables per env (local / staging / prod)
    • Request chaining
    • Code generation for different languages

  • HTTPie Desktop
    If you like CLI-first tools, HTTPie has a GUI that stays close to the terminal experience.

Postman is fine, but I find it bloated and slow on some Macs. Insomnia hits the sweet spot.

6. Containers & services

Docker Desktop is common, but I’ll suggest:

  • OrbStack or Colima
    If your machine is not a beast, Docker Desktop can be a resource hog. OrbStack and Colima use less RAM/CPU and feel more “Mac native.”
    OrbStack also makes Linux VMs painless.

I actually disagree with installing Docker Desktop by default now. Try a lighter alternative first, especially on an M chip with 16 GB or less.

7. Browsers & front end tooling

You do not need every browser open all the time, but:

  • Arc Browser
    Great for dev workspaces, split views, and isolating environments per space. I use it for “project dashboards” with logs, docs, and the running app grouped.

Also:

  • Safari Technology Preview
    If you do front end, this gives you the latest WebKit behavior on macOS without messing with your default Safari.

8. Productivity & OS-level helpers

Some things people skip but pay off daily:

  • Hammerspoon
    Super powerful automation tool. Script macOS behavior with Lua.
    I use it to:

    • Map hotkeys to opening specific project workspaces
    • Auto arrange windows per monitor layout
    • Bind “launch terminal in this folder” globally

  • Keyboard Maestro
    For less code-heavy automation. If you’re doing repetitive testing or report generation, it saves a lot of clicks.

  • Rectangle or Magnet
    Fully agree with using a window manager, but any of these is fine. Just get one and stick to the keybindings.

9. Misc dev helpers

  • Kaleidoscope
    For visual diffing of images, folders, and text.
    If you ever diff JSON config, design assets, or build artifacts, it’s worth it.

  • Shottr
    Super light screenshot tool with OCR and annotation. Great for bug reports.

  • Parallels Desktop (if you need Windows testing)
    Good enough for running Windows-only tools or IE/Edge testing. On M chips, it’s surprisingly usable.

Suggested “v1” setup for you

If I were you, fresh on a Mac and overwhelmed, I’d start with:

  1. Homebrew + core CLI tools (rg, fd, bat, eza, zoxide)
  2. One editor: VS Code
  3. One terminal: Kitty
  4. Commander One for file management
  5. One DB client: TablePlus
  6. One API tool: Insomnia
  7. Rectangle for window management
  8. Docker alternative: OrbStack or Colima

Use that for a couple weeks, then only add more stuff when you feel real pain. If every new tool has a job (“I need better API testing,” “I need visual diffs”), your setup stays sane instead of turning into a screenshot from /r/unixporn.

4

Since @mikeappsreviewer and @jeff already hit most of the “usual suspects,” here’s a different short list I actually keep on a fresh Mac, trying not to repeat their stuff.

1. File & project wrangling

  • Commander One
    If you work with lots of repos, build artifacts, logs, SFTP, etc, this is the one people sleep on. Dual‑pane, keyboard friendly, way nicer for serious dev work than Finder. Great for shoving build folders around, poking in ~/Library trash, and quick remote edits. For macOS development, Commander One is honestly a must‑have file manager.

2. Terminal & shell

  • Forget “one true terminal”; pick one that does not fight you. I actually disagree with going full GUI smart‑terminal: a fast terminal + good CLI tools scales better.
  • Install via Homebrew:
    rg (ripgrep) for search
    fd for find
    bat for file viewing
    zoxide for instant cd
    These change your daily speed more than a fancy terminal skin.

3. Editor / IDE setup

  • Pick one primary editor to start (VS Code or a JetBrains IDE). Constantly bouncing between 3 tools just burns mental bandwidth.
  • Add only what you need: formatter, linter, Git integration, maybe an AI assistant. Everything else can wait.

4. Databases

  • Start with TablePlus or Postico. You do not need five DB clients. One solid SQL GUI to inspect schemas, run quick queries, and compare staging vs prod is enough at first.

5. API & backend testing

  • I side with @jeff here: Insomnia over Postman. Lighter, fewer distractions, great for REST/GraphQL with envs for local / staging / prod.
  • If you like staying in the editor, use a REST client extension instead of yet another app.

6. Containers & services

  • I actually think people overinstall here. If you are not doing heavy container work yet, try OrbStack or Colima before Docker Desktop. Less fan noise, less RAM crying.

7. OS & workflow glue

  • A tiling / snapping tool like Rectangle is non‑negotiable once you have more than one monitor.
  • One launcher (Raycast or Alfred), not both. Script your “open dev workspace” flows there instead of hunting icons.

If you want a minimal starter kit that won’t melt your brain:

  • Homebrew + rg / fd / bat / zoxide
  • One terminal
  • One editor
  • Commander One for real file work
  • One DB client
  • One API tester
  • One window manager

Use that for a couple of weeks. Every time you feel real pain, then add a new app. Otherwise you end up benchmarking tools instead of shipping code, which I’ve absolutely not done for embarrassing amounts of time.

5

Since a lot of the “standard” stack is already covered by @jeff, @cazadordeestrellas and @mikeappsreviewer, here’s a tighter opinionated layer on top, focused on real tradeoffs.

1. File management: Commander One in real life

If you live in multiple repos, build folders and remote servers, Commander One is actually worth giving a shot instead of just forcing Finder.

Pros of Commander One

  • Dual pane is great for quickly restructuring projects or moving artifacts
  • Strong keyboard navigation feels way closer to a power‑user workflow
  • Handles remote connections without firing up a full IDE
  • Nice for digging in annoying places like ~/Library or build output trees

Cons of Commander One

  • UI feels “utility” level, not pretty, which might bug you if you like polished macOS apps
  • Another app to learn shortcuts for
  • Not as tightly integrated into macOS as Finder (Quick Look, tags, etc.)
  • Overkill if you mostly work inside a monorepo and rarely touch system folders

If you want a competitor angle: what @jeff leans on with native tools works fine if you are disciplined, while @mikeappsreviewer’s setup favors more GUI helpers. I think Commander One hits a nice middle ground: powerful but not bloated.

2. Terminals & shell

I slightly disagree with the idea that iTerm2 or Warp are “must‑have” in 2025. Stock Terminal plus a good shell setup (zsh or fish) and utilities like rg, fd, and fzf will speed you up more than a fancy terminal UI. Upgrade the shell ecosystem first, terminal app second.

3. Editor discipline

Everyone mentioned VS Code and JetBrains. I will add only this: pick one, and live in it for a month. Constantly context switching between VS Code, IntelliJ, and Xcode kills focus far more than using a “suboptimal” editor.

4. API & DB tools

Insomnia vs Postman vs HTTP clients inside the editor is personal taste. I prefer fewer standalone apps and more editor plugins, so your Mac stays lighter. Similar for DB: one client (TablePlus, Postico, DataGrip) is enough. Resist the urge to collect them.

5. System glue

Window managers like Rectangle are non negotiable once you try them. Here I fully agree with what others said. What I would skip initially: multiple launchers, multiple terminals, multiple screenshot tools. Start with one in each category and only add more when you actually feel friction.

If you want a lean starting kit: stock Terminal, one editor, Commander One for heavy file work, one DB GUI, one API client, Rectangle. That keeps you shipping instead of endlessly “tuning” your setup.