Merging macOS and iOS at the app level
Sal Soghoian, former Automation lead at Apple, writing for MacStories:
This, based on my understanding, is exactly what's been happening in the software engineering division recently. The thinking behind it, though, is nothing new. For a long time Apple's had a CoreOS group, among others, that worked on the underlying technologies central to both iOS and macOS. They're built on the same foundation, after all, so continuing to build out that foundation in as unified a way as possible simply makes sense.
Likewise, new technologies have been designed for both from the start. Swift, the programming language Apple debuted a few years ago, is one example. It's how developers will code for macOS and iOS in the future. Apple File System (APFS), announced last year, is the same. It'll eventually run everything from Watch to Mac.
Now, the same is true at the built-in app level. Getting the original iPhone and iPad to ship required enormous efforts, dedicated teams, and a ton of resource reallocation. Over the years, that resulted in some disparities. A few years ago Apple brought all if it back together under Craig Federighi, and now that same strategy is being applied to apps. Safari will be Safari at the code level. Mail will be Mail, Messages will be Messages, Calendar to be Calendar... you get the idea.
Having different code bases behind apps with the same name was never meant to be what differentiated iPhone and iPad from Mac. Having interfaces that best served the interaction models of each platform was. That's what end-users experience — the interface and interaction model. Everything else is pipes and plumbing hidden away beneath. The more of that stuff that's the same, the better. It improves compatibility and efficiency.
The iPhone and iPad remain multitouch devices optimized for direct manipulation, a hyper-accessible and mobile reimagining of the computer for the modern, mainstream world. Mac remains a mouse and pointer system — okay, now with Touch Bar! — and a traditional computer for those tasks that still require one.
Ideally, iOS will continue to benefit from the deep foundations of macOS, and macOS will continue to benefit from the innovations of iOS. Unfortunately, we don't always get ideals. Sometimes, short term, we'll get subsets that'll work on both. Long term, we'll get whatever, philosophically, Apple chooses to add back in and evolve further.
I'll spare you another regurgitation of iWork here.
I continue to believe that extensibility, introduced in iOS 8, is one of the most important developments in the history of the platform. It enables interoperability while maintaining privacy and security. Through Share Sheet and other manifestations, extensibility greatly accelerates the perceptive speed of the system and makes everything far more convenient. But extensibility is not automation.
Workflow (opens in new tab) is an iOS app that shows just how powerful "real" automation can be on iOS. It can also be accessed via extensibility. But that doesn't make extensibility itself a automator.
As much as I'd hate to see Workflow "Sherlocked" — copied at the system-level — by Apple, I'd love a base form of built-in automation on iOS. On the surface it's an incredibly niche feature but iOS has a way of making the niche more accessible to the mainstream.
I sometimes think Apple is worried about making iOS too complex — making it too much like macOS — and so they take a long time figuring out features like copy and paste or drag and drop. I understand the concern but, in my mind, iPad and iPhone should be allowed to evolve as though the Mac didn't exist. (And vice-versa.) The only goal should be to be the best. Like Phil Schiller has said (paraphrase) — iPad should be so good it puts pressure on the Mac and Mac should be so good it puts pressure back on iPad.
Having one team responsible for Safari, Mail, Messages, etc. on both platforms is great and hopefully means that, going forward, "Sent with Fireworks" is something I'll never have to see on my Mac again. But it's also something I hope, eventually, elevates the built-in apps on both platforms in a way disparate teams never could.
Check out the rest of Sal's article and let me know what you think.
Update: I clarified some of the language above so my rapid change of topic wouldn't cause so much whiplash.
Get the best of iMore in your inbox, every day!
Rene Ritchie is one of the most respected Apple analysts in the business, reaching a combined audience of over 40 million readers a month. His YouTube channel, Vector, has over 90 thousand subscribers and 14 million views and his podcasts, including Debug, have been downloaded over 20 million times. He also regularly co-hosts MacBreak Weekly for the TWiT network and co-hosted CES Live! and Talk Mobile. Based in Montreal, Rene is a former director of product marketing, web developer, and graphic designer. He's authored several books and appeared on numerous television and radio segments to discuss Apple and the technology industry. When not working, he likes to cook, grapple, and spend time with his friends and family.
iPad / iPhone => multi-touch / Pencil
Watch => Crown / Force Touch
ATV => Siri Remote Of course, it won't happen in the near future but 5 years? 10 years? I can see it. Apple can even unify the branding of its OS; maybe call it appleOS
Imagine a world where Apple is f'n consistent accross their user interface; cancel buttons are always on the left of my iPhone; keyboard shortcuts are THE SAME from macOS to iOS, and the F'N WORK in every application (opt+delete only works 50% of apps in iOS).
Imagine a world where my overpriced communication devices would properly notify me of incoming communications!
Imagine a world where my iPhone's battery shaming tabulation actually showed everything that was draining my battery - apps used in the "Past 24 hours" only adds up to 2 hours of use, but my battery charge is at 20%, claiming at the bottom of the page that I've used it for 6 hours, 8-10 hours standby.
Imagine a world where we can actually dig in and diagnose and fix the problems with our computers, rather than only told we have to restore from scratch and start all over again, only to find the same problems a month down the road.
Imagine a world where I can scroll a way-too-long forum post window in a web-page without the entire page scrolling.
Imagine a world where they don't take away a useful function in trade for an unintuitive, hardly useful gimmick. Why the F did they have to remove the function keys to add the Mystically Magical Fantasticalicious TouchWizzery Bar? There's plenty of room on all of those laptops to have both. ****, they could have put the touch strip at the BOTTOM OF THE SCREEN. That would make more sense to me, since it's a screen, I'd rather it face me.
Imagine a world where Apple didn't do the crap their customers don't want them to do.
Imagine a world where I don't ramble on and on and on about pointless stuff.
Apple follows Microsoft
• Adapts to the user's needs
• Provides the requisite level of security/privacy for the work being performed
• Is able to exploit the capabilities of the device(s)
• An iPad Pro [separate] kb with a trackpad and cursor on the display
• CLI and OAS Scripting for the OS and Apps on the Macs and, where appropriate, on iDevices
• A Mac App (like FCPX) with an iPad Pro directly connected (high speed) as a separate Display, Graphics Tablet, Touch I/O Controls for the Mac App