iPadOS14 wish list for web devs
Historically, I’ve had a rotten track record for predicting future features. And everyone has their take for iPadOS14 — many focusing on the UI or fabled iPad Pro apps like Xcode or Logic Pro. As a web/data developer with iPads in the hands of various family members, I guess I have a slightly different list of wishes:
What would make iPadOS a good web dev platform
- Real multi-monitor support. With pointer now implemented in iPadOS, all the pieces are in place. We don’t need desktop spanning, just the ability to adjust where the cursor leaves one screen and appears on another, so we can drop apps across a wider canvas of screens. A 11" in my bag and a 27" on the desktop — but without the compromises that currently means.
- More classes of app that are allowed to run in the background. This is so very important for web dev — we desperately need web servers and compilers to run reliably in the background without requiring hacks like building location awareness into apps to fool the OS into allowing it.
- A first party sand-boxed (virtualised?) command line. Actually, it’s not as impossible as it sounds, ISH does this already, but wow, Node/NPM compatibility would be nice.
- Other web browser engines to be blessed for use in iOS (Chromium/Firefox), or alternatively Safari web inspector to make the jump to iPadOS. Top level devtools are desperately needed on iOS.
- An onscreen keyboard that was tailored to coding would be amazing. Tempted to create one myself.
- Microsoft to walk on stage at the keynote and announce VSCode for iPad (or Panic to announce Nova for iPad — either would do!)
- Slack to similarly come on stage and announce video conferencing and screen sharing is coming to iOS.
- Shipping with multi window & gestures off by default. 80% of the audience don’t care & don’t like it, but want the old, simple iPad experience. The remaining 20% of us want so much more from iPadOS. We can find the settings to turn on those super powers.
- Data back-up options (even if it’s limited to just time machine).
- Of course, tweaks for more coherent multi-tasking. There have been some amazing demos recently online tying to pull the concepts together and make them discoverable, and I’d take any of them.
- Multi user — a stretch I know and it would mean a very long beta. But really, not many in reality can afford a device per child.
- Recognising hardware keyboards and allowing different settings for them, or shortcuts access to swapping keyboard layouts (non-english typists would appreciate this).
- Having some control over audio — like being able choose the mic at OS level. Handy for these WFH times, and also podcasting.