Earlier this year I wrote about the iPad Pro, and how I had furiously returned it after being disappointed in the device's promise and limitations. Now, just a few months later, I have a confession to make: I went out and purchased another one—and I was wrong the first time around.
It would mean using a terminal-based editor. It’s not for everybody, but even though I tend to use Visual Studio Code these days, I would have zero problems with using Vim for this purpose. (Hello Vim, my old friend, I’ve come to type with you again.) This caveat aside, I really don’t see a downside to this workflow.
For the second kick of the tires, I picked the smaller 11-inch model with LTE. Unlike it's big brother, it's much smaller for carting around, and slips into your bag undetected—great for quick work on the train or before your meeting at the cafe.
What I've discovered this time around is a sense of delight from the iPad that I hadn't really seen in technology for a while. Essentially, I liked the iPad because, despite its restrictions and rigidity, it actually helps me get more work done.
One thing at a time
- Developer community 2. Search Search Microsoft.com.
- This is a quick tutorial of how to setup a Google cloud VM, with Ubuntu and VS Code on board, using just your iPad. The result is a fully functioning linux d.
There are two things that the iPad excels at: battery life—despite a constant 4G connection—and the ways it forces you to multitask: slowly, with intent.
I've tested a lot of computers for getting work done, but the majority of my day job involves writing words—not code—which is a perfect fit for the iPad Pro. It feels backwards to say it, but because the iPad doesn't have multiple floating windows, and no mouse, I'm able to focus on on thing at a time.
If it's time to write, I'll fire up iAWriter and get a post done without flipping between windows or browsing the internet—a thing that's much more tempting to do when I've got a big desktop screen and Twitter open in the background, a click away.
The iPad's multi-tasking experience is better in this way as well; split-screening apps isn't new, but because iOS allows you to 'dock' an app to the side and summon it, quickly check for updates, and throw it away, it doesn't break me out of the mental model of what I should be doing—writing—because the main task remains there, full-screen, in the background.
Because iOS is so rigid, this can feel uncomfortable sometimes—Safari remains a total mess on the iPad—but what I've come to love the iPad for in my workflow is single-threaded tasks I need to complete, one at a time.
Because it has 4G, I can cycle through these tasks regardless of location, whenever I get the chance, and unlike every Intel-based laptop I've ever used, the iPad actually gets well beyond a full day's use on a charge, stretching into the next without breaking a sweat.
That's how the iPad Pro has now become an important part of my routine: I check my email on the iPad at the start of the day, reply and clear as much as I can, briefly browse Twitter, and plan my day in Todoist.
Anything light-touch is done on the iPad, and I use it to escape the shackles of my desk, better keeping on top of my freelance business during the day. I take notes on calls with the pencil, too, which are easier to cross-reference later than using paper, and instantly accessible by tapping the lock screen with the pencil.
Once I'm ready to start working, I jump to my desktop—where I no longer check email frequently, but prefer to use my coding tools or jump into the deep-end of writing a piece that involves a bit more work.
But, when I've done the serious work and need a moment away from the big screen, the iPad is my escape: I can slam through emails from the couch or dining room table, and it doesn't really feel like work. I find using a desktop computer really distracting, so using the iPad as a way to carve off some tasks away from my workstation has helped my work day become more structured, and less stressful.
The simplicity, and stability of the iPad is something I've come to count on—it's a tool that helps me do one thing at a time, without distractions. It just wasn't really obvious at first.
Keyboards, screens and dongles
I initially grabbed the smaller iPad without the keyboard case, but in doing so, I realized Apple actually made a mistake: the iPad Pro needs it to really make the most of the device. If you want to really use it in your workflow, the iPad is unusable in any other way.
I had assumed that I could use the onscreen keyboard in split mode fairly comfortably, but what you won't find out until after you buy an iPad Pro is that Apple inexplicably blocked split keyboard on these two models. Sorry, it doesn't work—and there's no real hope for this to change anytime soon
So, I ordered the keyboard case, and despite my reservations from the previous experience with it, it's much better with a keyboard attached to the back, than without. The smaller iPad Pro's keyboard case is less unwieldy, while no less terrible in the way it's made—but it does the job better than any other janky case or external keyboard ever will.
Without a keyboard, typing on the iPad's screen just gets tiresome, and I'd argue is why they tend to end up being turned into dedicated Netflix machines instead. Adding the keyboard case transforms the experience entirely: you can do actual stuff on this thing.
For most of us, we need to type words into forms, emails, or content management systems—and doing this on a touchscreen would be abysmal. The keyboard case helps, more than I expected, make the iPad feel magic.
And, thanks to that USB-C port, I can plug in my mechanical keyboard to write a post—like this one—anytime I please, and it just works. Color me surprised, but it's a delightful change from the lightning-port hellscape of the past.
That's what made this generation of iPad Pro hardware appealing: carrying a Apple USB-C dongle around meant you could plug one into a TV to watch a movie, or use a keyboard whenever you want to—and it feels incredibly capable as a result.
The disappointing bits
The hardware is beautiful, and I keep finding myself wishing I could do basic coding work on the iPad.
I'm not asking for the ability to run a full LAMP stack—though I wouldn't say no—but something in the middle, like Visual Studio Code, connected to a remote development machine with all my dependencies in Azure, so I can fix a CSS bug or deploy a hotfix without hauling my laptop with me.
That doesn't seem that infeasible, but I'm baffled by the lack of support for it. There are a few horrible, hacky ways to do this kicking around, but nothing as elegant as I've seen with Visual Studio Code's existing 'remote' development tools—it's just that we can't use them on iOS.
I'm hopeful this will change with time, but until then, I won't be trying to move this part of my workflow over. If Visual Studio Code were to build an iOS-based editor with the ability to use its remote tools, I'd just start using a containerized workspace in Amazon Web Services full-time.
I'm already doing this on Windows anyway to keep things portable, so connecting to a remote environment on the the iPad seems like such an obvious easy win. Especially given it would pair perfectly with long battery life and always-on 4G for this exact use case:
There are a few other niggles that still bum me out, like just how poorly the Apple Pencil is supported for any sort of writing task—even OneNote, which is famous for transcribing handwriting, doesn't support it on iPad.
Visual Studio Code Ipad Os
This is bizarre, along with the apparent lack of developer interest in doing much with it. I've been hoping that tools like Notion, which I use to organize my digital life, would support handwriting and transcription, but I'm yet to see any meaningful bits from apps worth using.
iOS remains as frustrating as it is beautiful, too, and it feels like I'm falling over myself sometimes to get something simple done. Things like flinging a photo between apps, or keeping two Safari tabs open on the screen at the same time, are non-trivial (if you do this, a fun Safari bug will lose the text cursor on any forms you have open until Safari is killed).
But, as always, rumors seem to say that iOS 13 will fix many of these niggles—though I doubt it'll reduce the amount of time I spend trying to get iCloud to stop harassing me about drive space.
Despite these problems, the iPad shines because of iOS' quirks, and it's a sacrifice I'm finding myself increasingly willing to make in exchange for how it helps me get things done.
If you're considering getting an iPad, it's exponentially improved by adding 4G to it—don't cheap out and skimp on it, figuring you'll use a hotspot instead. There's something magic about pulling it out of your bag and being online instantly that's worth the slight price hike, and totally changes the experience.
The iPad changed my mind
![Xamarin Xamarin](/uploads/1/1/9/5/119569353/823550428.png)
In the past, I've written about how devices like Surface Go are the perfect venn diagram of productivity and portability—and remain convinced that Microsoft's approach is the right one, allowing a tiny tablet to do run full desktop apps.
But, what Microsoft still doesn't have is a good enough dedicated tablet software story yet: Surface Go is one of my favorite devices in years, but its problem is a lack of tablet-mode apps worth using. If it had better battery life, that might be worth the compromise in the opposite direction, but that'll need to be addressed in future revisions.
That's where the iPad shines. It nails the tablet side of things, even though it can't run a single desktop app—so it doesn't matter at all. It's fast, light, and lasts all day, while being able to pull off the things that make me money, or push my business forward.
For me, it took thinking about how the iPad could fit into my workflow better, and resisting imposing my existing habits on it, to realize that sometimes simplicity is everything, and that's where the iPad Pro slotted in perfectly.
? iPad Pro 11' with LTE
A month ago, I wrote a list of gadgets I love. In it, I mentioned that I gave my old iPad to my wife. I didn’t use it enough to justify keeping it for myself. Yet, I conceded the appeal of the newer iPads:
I’m not saying never again to owning an iPad. The newer, fancy models with the pencil cast a certain spell on me.
Still, I reached a point where gadgets are only added to my collection if they get used. So I’ll only get an iPad if I can find a workflow that makes it a necessity.
Still, I reached a point where gadgets are only added to my collection if they get used. So I’ll only get an iPad if I can find a workflow that makes it a necessity.
In doing so, I fear a seed was planted. I started asking myself what said workflow might look like.
What is an iPad useful for?
iPads tend to be great consumption devices. They are lightweight and easy to transport. Fast, thanks to great specs and tight integration with the operating system. Their battery life lasts for most of the day. If you are watching videos, casual browsing, or playing games they are quite convenient.
I don’t hate consumption, but I’m trying to focus more on production than consumption in my life. So the iPad doesn’t hold great appeal when solely considered as a consumption device.
![Visual studio code for beginners Visual studio code for beginners](/uploads/1/1/9/5/119569353/137793414.png)
In recent times, I have seen people use them to be more productive, however. Doctors and medical students appear to be quite fond of domain-specific apps as well as its note-taking capabilities. Digital artists create great paintings and drawings on them. Musicians and even photographers/videographers are increasingly using the iPad, particularly the Pro line, on the go.
Could the iPad be a great option for programming as well?
My ideal use case
Before we discuss how one might configure an iPad for programming, I’d like to point out that my primary use would be reading technical PDFs, annotating them, and taking notes. If you are only interested in programming, laptops are a superior choice.
Still, you are there sitting at the library or a coffee shop. You’re reading a programming book, jotting down notes. It’s only natural to want to write code to validate and experiment with what you’re learning.
We know from neuroscience studies that the act of taking notes by hand is superior to typing them when it comes to retaining the information. For programming related material, however, I’d say that writing actual code is just as important.
You could bring both a laptop and an iPad but it becomes quite inconvenient at that point.
So for me, the ideal scenario would be an iPad that allows me to read technical books, annotate them/take notes, and program on it.
It already excels at the first two tasks, but can the iPad work for programming? The screen, in landscape mode, is certainly big enough. If you opt for the 12.9″ model, it’s essentially no different than my current MacBook Pro. Spec-wise, it might even be as fast, if not faster.
So it’s really a matter of software. These babies should be called iFortKnox. They are quite locked down.
A possible iPad setup for programming
If you search for them, you’ll find the occasional IDE for iOS. Pythonista for iOS, for example, will mostly work if you’re writing Python scripts.
Unfortunately, there isn’t an equivalent for Elixir and Phoenix, which I tend to favor these days. Plus, I like to use Git as a mechanism to share code between different laptops.
VNC is not a great option either, in my experience. You’ll face quite a bit of lag and the smaller screen of the iPad doesn’t lend itself too well to showing a whole computer desktop.
It seems to me that the best approach is to have the development environment on a remote machine and use the iPad as a client.
Amusingly, dedicated services like C9 by Amazon do not support mobile browsers that well. Though, with the upcoming iPad OS defaulting Safari to a full browser, it’s possible that these will become a viable option.
Flutter Ios Visual Studio Code
Based on my research, the most promising alternative is running a cheap remote box on DigitalOcean or similar provider, and connecting via a mosh-shell like Blink Shell. That appears to work really well even with spotty connections.
It would mean using a terminal-based editor. It’s not for everybody, but even though I tend to use Visual Studio Code these days, I would have zero problems with using Vim for this purpose. (Hello Vim, my old friend, I’ve come to type with you again.)
This caveat aside, I really don’t see a downside to this workflow. I get all the benefits the iPad brings plus the ability to actually do real programming (with a cover keyboard, of course).
The new iPad Pros are rumored to come out soon. They might be announced in less than two weeks. So I’m going to sit tight on this one but I’m eagerly waiting.
What about you? Do you have an iPad? Do you use it for programming? Is your workflow different than the one I propose here? Let me know in the comments below.
Get more stuff like this
Subscribe to my mailing list to receive similar updates about programming.
Thank you for subscribing. Please check your email to confirm your subscription.
Something went wrong.
Ipad Os 13 Visual Studio Code
I respect your privacy and take protecting it seriously. Feel free to review my privacy policy page for further details.