Working Copy

For a decade, Apple has insisted the iPad is a computer. The counterargument was always one word: Git. Version control is the circulatory system of software work, and iOS — sandboxed, terminal-hostile, allergic to background processes — seemed constitutionally incapable of hosting it. Working Copy is the app that ended that argument, and it did so without a venture round, a growth team, or a subscription treadmill. It is the work of one developer, Anders Borum, who has been shipping careful, frequent updates since its 2014 release with the cadence of a small studio and the taste of a much larger one.

What Borum built is not a “companion app” or a glorified GitHub viewer. It’s a full Git implementation living inside an iPhone or iPad: clone from GitHub, GitLab, Bitbucket, or any bare Git server, then branch, merge, rebase, cherry-pick, sign commits, wrangle submodules, and push — all from a device that fits in a jacket pocket. The free download covers browsing and editing; pushing to remotes sits behind a one-time in-app purchase, a pricing model so quaint in the subscription era it almost reads as protest art.

The market positioning is unusual because there effectively is no market. Competitors have come and gone; none matched Working Copy’s depth, and most didn’t survive. Its real competition isn’t another iOS Git client — it’s the MacBook you’d otherwise carry. That’s the honest frame for this review: not “is this the best Git app on iOS” (settled, yes) but “does this make the iPad a machine you can actually commit code from?” Mostly, remarkably, it does.

• Full Git operations, offline: Clone, branch, merge, rebase, and — critically — commit with no network at all. Commits queue locally and push when coverage returns. On a train or a plane, this is the difference between working and waiting.
• A genuinely good merge tool: Conflict resolution is visual, three-way, and touch-native. Resolving a merge conflict on a phone screen should be miserable; the design makes it merely fine, which is a quiet triumph.
• Files app, WebDAV, and x-callback-url exposure: Your repositories appear as ordinary folders to the rest of iOS, so external editors — Textastic, Runestone, whatever you prefer — read and write directly into the repo. Working Copy plays infrastructure, not gatekeeper.
• Shortcuts automation: Nearly every Git operation has a Shortcuts action. Pull-edit-commit-push pipelines can run from a home screen button or a scheduled automation. Nothing else on the platform comes close.
• The serious-user checklist: SSH keys, commit signing, submodules, and Git LFS. These are the features that separate a toy from a tool, and they’re all here.

The Core Loop

A Git client lives or dies on the commit loop: see what changed, stage what matters, write the message, ship it. Working Copy nails this loop with a clarity most desktop clients don’t. The status view shows changed files with inline diff previews; staging is per-file or per-hunk; the diff viewer renders side-by-side or unified with syntax coloring intact. The friction floor is low enough that reviewing a pull request’s changes on an iPhone during a commute is not a stunt — it’s Tuesday.

The built-in editor deserves more credit than “built-in” implies. Syntax highlighting spans a long list of languages, and the ancillary tooling — a color picker for design tokens, an image viewer for asset diffs — shows Borum thinking about what people actually keep in repositories, not just what a Git textbook says they do. Is it a replacement for a full IDE? No, and it doesn’t pretend to be. It’s a triage editor: fix the typo, patch the config, adjust the CSS value, commit. For that class of work, it’s faster than opening a laptop.

Where It Gets Clever

The strategic insight behind Working Copy is that it refuses to be an island. iOS apps traditionally hoard their documents inside their sandbox; Working Copy inverts this, projecting repositories out through the Files provider so the whole OS treats a Git repo as native storage. Pair it with an external editor and you’ve assembled a modular development environment out of App Store parts — Working Copy handles version control, something else handles editing, Shortcuts handles the glue. It’s the Unix philosophy smuggled onto a platform that was designed to prevent exactly that.

The Shortcuts support is the sleeper feature. Automating “pull this repo every morning,” “commit and push my notes vault nightly,” or “deploy this static site when I tap a widget” turns Git from a developer ritual into household plumbing. A meaningful chunk of Working Copy’s audience isn’t even writing software — they’re writers and researchers versioning Markdown, and the app serves them just as well.

Where It Strains

Honesty requires noting the ceiling. iOS itself imposes limits no app can fully engineer around: background execution is rationed, so long operations want the app foregrounded; enormous monorepos are more than an iPad is built to chew through comfortably; and there’s no local compiler or test runner waiting on the other side of your commit, so the edit-run-verify loop still ultimately lives elsewhere for most stacks. Working Copy pairs beautifully with remote workflows — SSH into a server, or push to CI and let the robots test — but that’s a workflow you assemble, not one the app hands you.

The free/paid split will also ambush newcomers. You can clone, browse, and edit for nothing, then discover that pushing — the entire point of the exercise — requires the pro unlock. The price is fair for what is plainly years of expert labor, and one-time purchases deserve applause in the subscription era. But the paywall’s placement guarantees a moment of friction at the exact instant a new user is most invested, and it’s easy to see why that placement stings.

The One-Developer Question

Single-developer apps carry a bus-factor risk that enterprises rightly weigh. The counterweight here is a decade-plus track record of same-week support for new iOS features — widgets, Shortcuts revisions, external displays — that most funded teams don’t match. It’s a risk, but it’s the best-managed version of that risk on the platform.

Working Copy’s design is native to a fault, and that’s meant as praise. No cross-platform framework, no brand-first reskinning of standard controls — it looks and moves like Apple’s own apps, adopts each year’s iOS design language quickly, and reserves its personality for where it counts: diff rendering, graph visualization of branch history, and that merge tool. Information density is well-judged; a repository’s state is legible at a glance without the screen turning into a cockpit.

On paper, the performance story is as good as iOS allows. A 2D, text-driven app of this scope is light on hardware, and the design leans on native rendering rather than fighting the platform. The realistic caveat is scale: a truly massive repository with deep history is where the edges of any iOS app show, and memory pressure on older iPhones is a genuine constraint — but for the repos most humans touch daily, there’s no reason to expect trouble.

This is an iOS and iPadOS exclusive, and the two experiences differ meaningfully. On iPhone, Working Copy is a superb reactive tool: review the diff, resolve the conflict, merge the hotfix from the grocery store. On iPad — especially with a keyboard, trackpad, and Stage Manager — it graduates into a primary tool, sitting split-screen beside an editor or an SSH client in a layout that resembles a workstation. Touch targets are generous, drag-and-drop between apps works as it should, and keyboard shortcuts cover the essentials.

There is no Android version, no desktop version, and — as the developer’s materials feel oddly compelled to clarify — no Steam or Nintendo release. Your Switch remains safe from interactive rebasing. If your life spans platforms, Working Copy can only cover the Apple half, and that’s the most legitimate reason to hesitate.

Some apps are good; a few are definitive. Working Copy is the definitive answer to a question Apple never quite answered itself — how serious work happens on iOS. It has essentially no competition because the bar it set is brutal: full Git fidelity, exemplary platform citizenship, a decade of relentless updates, all from one developer charging a fair one-time price. The complaints — the paywalled push, the Apple-only scope, the ceilings iOS itself imposes — are real, and none of them come close to disqualifying an app this essential. If you own an iPad and touch a Git repository, this is not a recommendation. It’s a prerequisite.