Real web development on iPad
As a web designer-developer, I’ve been doing all my work from a MacBook Pro since the beginning. But as a student carrying & using my iPad Pro for 95% of my work, I wanted a portable coding setup I could use from my iPad.
(If you’re getting started with development, I absolutely recommend a Mac instead of a more complicated setup like the one I’m about to describe. Focus on learning the tools, not your setup for using them.)
Though in the past I’ve heavily used Glitch for coding on iPad, I’ve begun to reach its limitations. My Notebook site is big enough (!) that developing it maxes out the memory limits of Glitch, which forces the app to hang, restart, rebuild, and generally slows my development workflow down enormously. I love Glitch, but as of right now it’s just not well-suited enough for serious web development. Perhaps that will change soon.
There’s also hardware solutions like @jxnblk’s, but when the entire premise of coding on iPad is portability, they don’t fit the bill for me.
Online-hosted VSCode is another exciting new option opening up, which is being officially embraced by Microsoft with this week’s launch of Visual Studio Online. I haven’t tried either yet, but Tierney Cyren has some details on Twitter.
I’ve now set up a VPS on DigitalOcean for running my coding setup from. While there are many similar services (Linode, AWS, etc), I’ve been really happy with DigitalOcean’s service.
Here’s a referral link, if you’re interested: (I’ll get credit too!)
Get $50 on DigitalOcean
(Huge shoutout also the GitHub Student Developer Pack, which provides discounts on tons of great developer services, including DigitalOcean!)
For getting started, I set up a minimum droplet on Ubuntu (with backups enabled) in NYC. Nothing special here.
Big thanks to Theo Bleier for helping me out here—servers are not at all my forté & he walked me through setting up a user, Linux basics, Tmux, etc. I couldn’t have done it without the assistance :)
(Termius Pro is also available through the Student Developer Pack, so make sure to enable that, so you use their longer background sessions.)
Using a command-line editor is the biggest change from Glitch/VSCode. I’m already well-versed in Vim, and use it inside VSCode normally, but it’s an adjustment nonetheless.
If you’re looking to start learning it, Adam Morse provided my original inspiration & learning resources. Here
Setting up Vim
On my Mac I have an incredibly long
.vimrc, but I wanted to start out fresh on the server. You too will probably want to change a bunch of defaults (such as to show line numbers, set your indentation preference, etc), so here are some Vim setups to check out:
I’ve heard about Tmux for awhile but had never used it, so I took the plunge. It’s basically a glorified command-line version of using multiple terminal tabs, except you can hide tabs, close & re-open windows, and do other fancy things.
The lack of devtools in iOS Safari has long frustrated me. I’ve tried a number of apps in the past and made my own failed attempts to bundle Chrome’s devtools, but I’ve finally found a solution: Inspect. While not being quite as sophisticated as Safari or Chrome’s desktop devtools, it has the vast majority of what I need, such as tap to inspect, style editing, responsive design testing, viewing source & network requests, etc. I’ve never seen another iOS solution nearly as good—if you’re a frontend web developer with an iPad, you should check it out.
Here’s what my setup looks like with Vim inside Termius in Split View with Inspect:
Because your code isn’t running on the device directly,
localhost isn’t how you’ll access it. While each DigitalOcean droplet comes with a publicly-accessible IP address, it’s ugly & the default setup only allows using one port at a time.
While ngrok is well-known & works great, using anything but its random subdomains requires a costly subscription. While I’m not at all against paying for great tools, it seemed unnecessary for getting started.
I found serveo.net, which offers nearly the same functionality. You can super easily set your own subdomain (like your username or the project name), run it in the background via Tmux, and it worked pretty flawlessly for me.
Although at first I tried setting up SMB filesharing on my server to use the new Connect to Server feature in iPadOS’ Files, it didn’t work for me, probably due to my complete lack of understanding of such backend topics.
I only then noticed that Termius has an integration with iOS Files by default! In fact, Termius’ integration is pretty solid, allowing you to browse, edit, and open files in place. If you’re looking to just have access on iOS Files, Termius’ built-in capabilities should suffice.
While the file provider works great as it is, it offers no automation features. I installed the Secure ShellFish app (by the developer of the unparalleled iOS Git client Working Copy, and it’s free!). It facilitates a similar iOS File Provider:
But Secure ShellFish opens up lots more possibilities of automation…
Going from server to iOS Shortcuts was inevitable here, no?
Though Termius’ file provider works nicely, the app provides only a single shortcut for automation on iOS, ”Connect to,” and has no filesystem shortcuts (uploading or querying files, namely).
In the past, I published on this site by making a new file on Glitch, pasting in the text, confirming the page rendered correctly, & exporting to GitHub. (Netlify automatically deploys the site based on GitHub.) Without Glitch, I have more flexibility, but need to set up my own system.
For now, I’m using a very simple workflow: write in Drafts, save the post to a new file in Working Copy, commit, push. Though I can write in any text editor & save to Working Copy, this workflow doesn’t allow me to preview or develop anything custom before the post goes live.
Considering the new automation features of Drafts 15, I may also consider a publishing workflow directly from Drafts using Shortcuts and/or Secure ShellFish/Scriptable.
Shortcuts also supports running Bash scripts over SSH. A more complex, but more flexible, publishing shortcut could upload via ShellFish and run a script over SSH: Secure ShellFish’s upload shortcuts would allow saving the MDX file at the correct path, then I could use Shortcuts’ Bash scripting to either enable Serveo and open Inspect (which does not support Shortcuts, unfortunately) or just directly
git commit && git push.
These automated directions are to explore over upcoming days/weeks, so for now I’m publishing via Working Copy without previewing or using Vim over SSH (like an animal).
Full-stack web development on iPad comes with many constraints, but it enables creating all kinds of custom workflows fairly simply. If you embark on this journey and discover improvements to the workflow I’ve outlined here, please let me know on Twitter. Until then, happy coding!