The Best iPad for Indie Developers & Solopreneurs in 2025 (Real Workflows, Not Spec Sheets)
Every iPad buying guide ranks models by price tier and camera specs. None of them tell you which one actually survives a solo-dev workday. Here's the real answer, with the exact setup that ships product.
LevelIntermediate
Tools
github-codespaces
G
ssh
S
working-copy
W
blink-shell
B
revyl
R
I bought a 13-inch iPad Pro M4 in April 2025 and spent three months trying to ship a SaaS product from it. Not as a productivity experiment – as a real constraint. My MacBook Pro died, the replacement was backordered, and I had a paying beta waiting. What I found surprised me: the hardware was never the problem. It never has been. The M4 chip in that iPad is faster than the MacBook Air I shipped my first two products on. The problem was always iPadOS, and in 2025, that problem is finally – finally – getting smaller. This guide is for solo developers and solopreneurs who want a straight answer: which iPad should you actually buy if your goal is to ship product, not watch YouTube reviews about it.
The honest state of iPadOS in 2025
Let me say the thing every iPad review dances around: iPadOS is still not macOS. Stage Manager improved multitasking. The M4 chip benchmarks faster than a 2021 MacBook Pro. But until mid-2025, you still couldn't reliably run two windows of the same app side-by-side, browser devtools were crippled, and Xcode was a remote dream.
iPadOS 26, announced at WWDC 2025 and shipping this fall, changes the calculation in two concrete ways. First, true overlapping windows – not Stage Manager's tile-and-pray approach, but actual desktop-style window management with free resize. Second, a Safari that finally exposes full devtools comparable to what desktop Chrome has shipped for a decade. These aren't incremental improvements; they remove the two friction points that made iPadOS feel like a tourist visa in developer territory.
The third shift is infrastructure, not OS. GitHub Codespaces, JetBrains Gateway, Revyl, and a maturing SSH ecosystem mean a capable iPad is now a thin client for a cloud-hosted dev environment that doesn't know or care what opened the connection. You can run a full Node.js project, a Rust service, or a Rails app in Codespaces and push from Working Copy without your iPad ever running a compiler. The "iPad can't run Xcode" complaint is real but narrowing: if your stack is web, API, or cross-platform mobile, the iPad Pro is already a complete machine with the right setup.
That's the context. Here's the verdict on hardware.
The three iPads worth considering
There are six iPad models in Apple's lineup. Three of them are distractions for a developer audience. The iPad mini 7 is lovely but the 8.3-inch screen kills productivity at anything resembling a real IDE session. The base iPad 10th gen is fine for note-taking and light writing; the A14 chip starts to stutter when you have Codespaces open in Safari, Working Copy running a rebase, and Blink Shell SSHing into your VPS simultaneously. The iPad Air M1 is a fine machine that was replaced by something better.
That leaves three:
iPad Air M2 (11-inch or 13-inch) – €699 / $599 for the 11-inch, €899 / $799 for the 13-inch as of mid-2025. The M2 chip is fast enough that you will never feel it as a bottleneck. Liquid Retina display is excellent. No promotion (adaptive 120Hz) is the honest compromise you make, and after two weeks you stop noticing. This is the correct answer for anyone who wants to keep a budget and do real work.
iPad Pro M4 (11-inch or 13-inch) – starts at €1,099 / $999 for the 11-inch. ProMotion 120Hz display, the thin chassis, the OLED on the 13-inch, and the M4 chip which is meaningfully faster than M2 for any AI inference you want to run locally. The Tandem OLED on the 13-inch Pro is genuinely the best screen I've ever worked on for six-hour writing and coding sessions. If you're billing $8k/month or more, this is not an extravagant purchase.
iPad Pro M2 (refurbished) – Apple's refurbished store regularly lists these at €749–€899. M2 chip, ProMotion, Liquid Retina XDR on the 12.9-inch. Excellent value if you want Pro hardware without the Pro price. The trade-off is last-gen chip and the older design, neither of which matters for our use case.
Which one to actually buy
The answer depends on one question: do you need the screen to be the primary reason you reach for it?
If you're pairing the iPad with an external monitor at a desk – which I'll get to in the setup section – the 11-inch Air M2 is the right answer. $599, M2 chip, light enough to carry everywhere, and when docked it drives a 4K external display while your keyboard and trackpad sit in front. The portability premium is real: I've shipped hotfixes from a coffee shop with the 11-inch Air on my lap in a way I wouldn't with a 13-inch anything.
If the iPad is your primary screen, buy the 13-inch. The real estate difference between 11 and 13 inches is dramatic in Stage Manager and will be even more so with iPadOS 26's free-form windowing. You can realistically have your IDE session on the left, a terminal on the right, and a browser preview at the bottom without everything feeling like a compromise. On the 11-inch you're constantly shuffling windows.
My personal ranking for a solo developer in 2025: 13-inch iPad Air M2 first, 11-inch iPad Air M2 second if portability matters more than screen space, 13-inch iPad Pro M4 third if you're treating it as a primary machine and billing enough to justify it.
I'd skip the 11-inch iPad Pro entirely. The price premium over the Air M2 is €300–400, and the M4 performance gain isn't visible in web-based dev workflows. You're paying for ProMotion and a slightly thinner chassis. Both are genuinely nice. Neither ships more product.
The setup that makes any of these viable
Hardware is 30% of the answer. Setup is 70%. Here's exactly how I run a solo dev workflow on iPad.
SSH and terminal: Blink Shell. This is the only terminal app worth using on iPad. $19.99/year, but it gives you mosh support (stateful connections that survive going off WiFi), tmux built in, and a keyboard shortcut model that doesn't conflict with iPadOS. I keep a persistent tmux session on my Hetzner VPS and drop back into it from anywhere. The Blink team also ships a local SSH client that talks to your Mac if you want a hybrid setup.
Git and code editing: Working Copy + Runestone. Working Copy ($19.99) is a full Git client with SSH key management, branch management, and file editing. For pure markdown, config files, and small code edits it's sufficient. For anything heavier I open files in Runestone (free, $10 tip), which is a native iOS text editor with syntax highlighting for 50+ languages, find-replace with regex, and a fast keyboard experience. Together they cover 80% of what I used VS Code for on desktop.
Full IDE: GitHub Codespaces in Safari. This is the core insight of the whole setup. Codespaces runs VS Code in a browser, with your full dev container, all your extensions, and your dotfiles. On the iPad Pro M4, Safari renders it at the full 2420×1668 resolution. You get IntelliSense, the integrated terminal, multi-file editing – everything. The only missing piece is the keyboard shortcut layer: Cmd+Shift+P works but some VS Code shortcuts conflict with iPadOS. I spent one afternoon remapping the conflicts in VS Code settings and haven't thought about it since.
External display: any 4K USB-C monitor works. The iPad Pro M4 and Air M2 both support Stage Manager across two screens – iPad display + external – which gives you roughly the same real estate as a 13-inch laptop with an external monitor. I use a LG 27UP850-W (27-inch, 4K, USB-C, $350) and the experience is indistinguishable from working on a Mac with a second screen for anything web-based.
Keyboard and trackpad: Apple Magic Keyboard for iPad is the canonical answer but it's $299 for the 13-inch and adds significant weight. I use the Logitech MX Keys Mini ($99) via Bluetooth and a Magic Trackpad. More portable, better typing feel, and the function row actually works with iPadOS's media controls.
1
Set up your cloud dev environment
Create a GitHub Codespaces devcontainer with your language and tools. If you're on a project without one, copy the universal devcontainer template from the GitHub docs – it includes Node.js, Python, and a decent set of VS Code extensions. Set your dotfiles repository in Codespaces settings so every new environment pulls your aliases, vim config, and git settings automatically.
Install Blink Shell from the App Store. In Settings → Keys, generate a new ED25519 key pair and add the public key to your VPS's ~/.ssh/authorized_keys and to GitHub's SSH keys. Create a Blink host entry for your VPS with your username and key. Test the connection with mosh username@your-vps-ip – you should land in a shell that survives WiFi drops.
bash
1
#OnyourVPS:installmosh
2
aptinstallmosh
3
4
#Openportrangeformosh(UDP)
5
ufwallow60000:61000/udp
3
Configure Working Copy for your repositories
Open Working Copy, connect it to your GitHub account via OAuth, and clone your active repositories. Set up SSH signing if you use signed commits – Working Copy uses your Blink-managed keys or its own key store. Enable the Working Copy file provider in iPadOS Settings so Runestone and other apps can open files directly from your repos without copying them.
4
Tune Safari for Codespaces
In Safari Settings, enable "Request Desktop Website" for github.dev and *.github.dev globally. Install the 1Blocker or Wipr content blocker and add a rule to disable it for github.dev – ad blockers interfere with Codespaces WebSocket connections. Add github.dev to your home screen as a web app so it opens in its own window without browser chrome eating vertical space.
5
Set your Stage Manager layout
Enable Stage Manager in Control Center. Set it to use the external display when connected. Create two recurring layouts: a coding layout (Codespaces full-screen on external, Blink Shell in the lower-right of the iPad display, Working Copy in the upper-right), and a writing layout (Craft or iA Writer full-screen on iPad, browser research on external). iPadOS 26 will let you save these as named layouts – start building the habit now.
The workflows that actually work
Shipping a web app from an iPad is table-stakes now. Open Codespaces, push via Working Copy, deploy via GitHub Actions – the full loop runs without touching a desktop machine. I shipped twelve updates to a production app in six weeks from an iPad, including two database migrations and an authentication refactor.
What's less obvious is where the iPad is better than a laptop for solo dev work, not just adequate.
Client calls while coding is the first one. The iPad's front-facing camera in landscape mode is better than any laptop webcam at this price point, and because Stage Manager separates windows cleanly, I can have a Zoom call in a small window while keeping my Codespaces session visible and legible. On a 13-inch MacBook I'm constantly resizing windows. On the 13-inch iPad with an external display, the call lives in a corner and I keep coding.
Markdown-first documentation is the second. Working Copy + Craft (or Obsidian) creates a writing experience that's faster than any desktop setup I've had. The Apple Pencil on a handwritten architecture diagram, exported as a PNG, dropped into Working Copy, committed to the repo's /docs folder – that loop is thirty seconds. On a laptop it's "open tablet software, export, drag to Finder, drag to IDE." On iPad it's one Share Sheet action.
Async design review is the third. I use Pixelmator Photo to review design exports from Figma, annotate with Apple Pencil, and send back to the designer via Slack. The Apple Pencil on an OLED screen is a better review tool than a laptop trackpad with no stylus equivalent.
What Revyl changes for the solo developer
Revyl deserves its own paragraph because it's the most interesting new entry in the iPad dev stack for 2025. It's a visual debugging and preview tool that connects to your running web app – whether in Codespaces, on a local VPS, or in production – and lets you visually inspect elements, edit CSS properties, and see changes in real time on the iPad's display. It's the missing DevTools layer that Safari's in-page inspector doesn't fully cover.
The practical value: I open Revyl alongside Codespaces in Stage Manager. I make a CSS change in the Codespaces terminal, it hot-reloads in Revyl, I can tap any element and see the computed styles. It's not perfect – complex React component state inspection is still better in Chrome on a desktop – but for layout and visual iteration it removes the "I need to switch to my laptop to see this properly" moment that used to break my iPad-first flow every thirty minutes.
The actual buying decision
If you leave this guide with one number: the 13-inch iPad Air M2 at $799 is the right iPad for a solo developer in 2025. It's fast enough that you'll never blame the chip. The screen is large enough for real multi-window work. It pairs with any external display over USB-C. And at $799 it's not a bet-the-farm purchase – it's roughly the same as one month's Hetzner dedicated server for a side project that's scaling.
The iPad Pro M4 is the right answer if you're treating your iPad as a primary machine and you're already making money on what you ship. The OLED screen on the 13-inch model reduces eye strain in a way that's hard to quantify until you've worked on it for three months. It's real. If you're billing consistently and your iPad is open eight hours a day, $1,299 amortizes fast.
The 11-inch Air M2 is the right answer if you travel more than you sit at a desk. It's the most portable real-work device Apple makes. Twelve hours of battery life is accurate. It fits in a backpack sleeve without compromising anything else. The screen is enough when you're in a cafe without an external display, and it's enough when you're presenting to a client.
Whatever model you choose, the setup section above is the same. The hardware just determines how comfortable the cockpit is. The tooling determines whether you ship.