Federico is the founder and Editor-in-Chief of MacStories, where he writes about Apple with a focus on apps, developers, iPad, and iOS productivity. He founded MacStories in April 2009 and has been writing about Apple since. Federico is also the co-host of AppStories, a weekly podcast exploring the world of apps, Unwind, a fun exploration of media and more, and NPC: Next Portable Console, a show about portable gaming and the handheld revolution.
During its WWDC 2024 keynote earlier today, Apple announced that the Vision Pro will be launching in more countries and regions later this month.
Specifically, the Vision Pro will become available for pre-order in China mainland, Hong Kong, Japan, and Singapore on June 13, with availability starting on Friday, June 28. On the same day, pre-orders will go live for customers in Australia, Canada, France, Germany, and the United Kingdom, with availability starting on Friday, July 12.
“The enthusiasm for Apple Vision Pro has been extraordinary, and we are thrilled to introduce the magic of spatial computing to more customers around the world,” said Tim Cook, Apple’s CEO. “We can’t wait for more people to see the impossible become possible, whether working and collaborating with an infinite canvas for apps, reliving treasured memories in three dimensions, watching TV shows and movies in a one-of-a-kind personal cinema, or enjoying brand-new spatial experiences that defy imagination.”
In addition to announcing availability in more countries and regions, Apple also showcased visionOS 2, the next major update to the Vision Pro’s operating system. Highlights from visionOS 2 include new gestures to invoke the Home Screen and Control Center, train Travel Mode, mouse support, and more. We’ll cover all the changes in visionOS 2 in a more detailed overview later today.
I love this story that I first saw mentioned on Brendon’s blog a few weeks ago about a Redditor who designed the iPhone game controller of my (our?) dreams.
Picture this: it’s a PSP Go/Xperia Play-styled, slide-out controller that attaches via MagSafe to any iPhone, has Bluetooth, a USB-C port for charging, and therefore works with any modern iOS game or emulator regardless of whether the iPhone is mounted on it or not. The controller has a built-in kickstand that supports landscape and portrait gaming (the latter is essential for DS emulation in Delta) and is much more portable than other snap-on solutions available for iOS devices.
The best part: the creator of this controller, called the M-Con, has announced plans to make this a real product that you can buy in the future. You can watch the announcement video below:
As Jonathan’s story in last Saturday’s issue of MacStories Weekly showed, the dream for many of us right now is a compact, MagSafe-enabled game controller for iPhone that doesn’t use USB-C and allows the iPhone to be rotated. No official product that is not a 3D-printed adapter or DIY hack that does all that exists right now.
NPC and Comfort Zone join the MacStories family of podcasts.
I’m incredibly excited to introduce two brand new shows joining the MacStories family of podcasts today: Next Portable Console (or NPC), hosted by me, Brendon Bigley, and John Voorhees, and Comfort Zone, hosted by Niléane Dorffer, Chris Lawley, and Matt Birchler. You can find both shows, along with links to subscribe, on MacStories’ Podcasts hub.
Before I hand it over to Brendon and Niléane to provide more context around NPC and Comfort Zone, allow me to say a few words since this launch marks an important milestone in MacStories’ growth for the next 15 years of the website.
As I hinted in my story on the issues of iPadOS last week, I upgraded from an 11” iPad Pro to a 13” iPad Pro (1 TB, Wi-Fi-only model). While I was very happy with the 11” form factor, I decided to return to the larger model for two reasons:
I wanted to have maximum thinness with the ultimate iPad Pro model Apple makes.
I sacrificed the physical comfort of the 11” iPad Pro to get a larger display for my MacPad as well as portable gaming.
Today, I will explain how I was able to immediately turn the brand-new 13” iPad Pro into a convertible MacPad using a combination of accessories and some new techniques I’ve been exploring. I’ll also share my experience with using the iPad’s glorious Tandem OLED display in a variety of gaming setups ranging from streaming to emulators.
I’ve published my fair share of criticism regarding the iPadOS version of Stage Manager over the years. I wrote about it again last week, but most of its underlying issues date back to the original release in late 2022, which I documented here.
But let’s say you don’t want to read my articles and would prefer to have a more practical example of the issues I described. In that case, go check out this three-minute video by Quinn Nelson, in which he tries to have a Freeform window on the iPad and another Freeform window on an external display:
It shows the confusing lack of Mission Control/Exposé to see all active windows for an app in Stage Manager.
It highlights the lack of a window picker in Stage Manager. Quinn points out that he can see a window picker on the iPad’s display, but that’s because the iPad is running in traditional Split View mode, which does come with the shelf.
Quinn is (rightfully) perplexed by what ‘Add Another Window’ means.
The video shows the inconsistencies of Spotlight as an app launcher.
It also showcases the inconsistent implementation of keyboard shortcuts for multitasking.
The video shows how downright unintuitive the solution is. An alternative solution mentioned in Quinn’s replies is equally non-discoverable.
I’m sure someone at Apple may argue that this is the kind of feature people buy another computer for. But it’s always the same story: if Stage Manager for iPad exists, what’s the point of leaving it in this state for two years?
There are so many parts of Steve’s iPad Pro manifesto I would quote here on MacStories, but I’m going to limit myself to just a couple of excerpts.
What I like about this story is that it’s a balanced take on the limitations of iPadOS from the perspective of a developer, laid out in a comprehensive roundup. It serves as a great companion piece to my story, but from a more technical angle.
Here, for instance, is a well-reasoned assessment of why Stage Manager isn’t ideal for developers of iPad apps:
Stage Manager was such a missed opportunity: it tried to bolt-on a windowing model onto iPadOS without providing developers any way to optimize for it, and has had virtually no meaningful improvements in two years. What I really want to see are APIs. APIs to know when an app is running in Stage Manager and give it an opportunity to enable extra functionality to accommodate that — like having an ‘open in New Window’ context menu option that it would otherwise hide. APIs to set window size/shape, minimum and maximum size. APIs to open a window in split view if possible, with a preferred screen side. APIs to drag a window on mouse-down. Auxiliary views or inspector panels that can be floated on/near a primary window, like visionOS’ ornaments.
Many of these features are available as APIs to apps using the iOS SDK… on macOS and visionOS. Which is why it boggles the mind that iPad’s own Stage Manager spec completely shunned them, and ignored the explicit intent provided by developers as to how they want their apps to work. Stage Manager wasn’t provided as an opportunity to make our apps better, it was inflicted on developers in a way that harmed the developer, and user, experience. Which is why today you can very quickly stumble upon apps that don’t quite resize correctly, or have important parts of the UI covered by the virtual keyboard, or toolbars floating in strange places.
To this day, developers have no way to fine-tune their apps so that they behave differently (and better!) when Stage Manager is active. This part about JIT is also worth calling out:
Just-in-time compilation is essential to power things like web browsers, console and PC emulators, and language-based virtual machines. It is used by Apple’s own apps, like Playgrounds, to empower key functionality that no third party app can match. And it is provided in a very limited way (with a ton of asterisks) to Alternative Web Browsers in the EU under the DMA, so they can implement their own JavaScript engines. The DolphiniOS project, which emulates Nintendo’s GameCube, recently posted a video that perfectly encapsulates the problem and demonstrates why emulators for newer consoles just can’t come to iPadOS. Other app stores, like Microsoft’s Windows Store, offer a JIT entitlement as standard, and I think Apple should, too.
It’s not like JIT cannot exist on iPadOS; it’s that Apple has chosen not to offer it as an entitlement for third-party developers.
I also want to point out two more aspects of Steve’s manifesto. It’s almost a 1:1 match of a story he wrote for us in 2019, which is quite sad as it tells you a lot about iPadOS’ state of affairs. Five years later, and we’re still asking for the same changes. Additionally, it should be noted that Steve is not asking for Apple to call it a day and put macOS on iPad. Claiming that someone who criticizes iPadOS does so because “they just want the iPad to turn into a Mac” has become the de rigueur dismissal for some reply guys these days, and it completely misses the point.
Let me cut to the chase: sadly, I don’t have a new iPad Pro to review today on MacStories.
I was able to try one in London last week, and, as I wrote, I came away impressed with the hardware. However, I didn’t get a chance to use a new iPad Pro over the past six days ahead of today’s review embargo.
I know that many of you were expecting a deeper look at the iPad Pro on MacStories this week, but that will have to come later. I still plan on upgrading to a 13” iPad Pro myself; I’ve decided I want to return to the larger size after a few months with the 11” iPad Pro. If you’re interested in checking out reviews of the new iPad Pros from heavy iPad users like yours truly right now, I highly recommend reading and watching what my friends Jason Snell and Chris Lawley have prepared.
Still, as I was thinking about my usage of the iPad and why I enjoy using the device so much despite its limitations, I realized that I have never actually written about all of those “limitations” in a single, comprehensive article. In our community, we often hear about the issues of iPadOS and the obstacles people like me run into when working on the platform, but I’ve been guilty in the past of taking context for granted and assuming that you, dear reader, also know precisely what I’m talking about.
Today, I will rectify that. Instead of reviewing the new iPad Pro, I took the time to put together a list of all the common problems I’ve run into over the past…checks notes…12 years of working on the iPad, before its operating system was even called iPadOS.
My goal with this story was threefold. First, as I’ve said multiple times, I love my iPad and want the platform to get better. If you care about something or someone, sometimes you have to tell them what’s wrong in order to improve and find a new path forward. I hope this story can serve as a reference for those with the power to steer iPadOS in a different direction in the future.
Second, lately I’ve seen some people argue on Mastodon and Threads that folks who criticize iPadOS do so because their ultimate goal is to have macOS on iPads, and I wanted to clarify this misunderstanding. While I’m on the record as thinking that a hybrid macOS/iPadOS environment would be terrific (I know, because I use it), that is not the point. The reality is that, regardless of whether macOS runs on iPads or not, iPadOS is the ideal OS for touch interactions. But it still gets many basic computing features wrong, and there is plenty of low-hanging fruit for Apple to pick. We don’t need to talk about macOS to cover these issues.
Lastly, I wanted to provide readers with the necessary context to understand what I mean when I mention the limitations of iPadOS. My iPad setup and workflow have changed enough times over the years that I think some of you may have lost track of the issues I (and others) have been experiencing. This article is a chance to collect them all in one place.
I just came back to my hotel from the media event Apple held earlier today in London at their Battersea Power Station headquarters. I had high expectations for the new generation of iPad Pros that Apple unveiled today – some of which were exceeded by reality (hardware), and others that were, regrettably but unsurprisingly, faced with the reality of the iPad platform (software).
What follows is a loose collection of notes and impressions from the event, where I was able to try both iPad Pro models multiple times and spend some quality time with their accessories.
So where do we go from here? While Apple’s acceptance of emulators in the App Store is groundbreaking, and should delight many fans of retro gaming consoles, it’s an extremely limited change. Nobody really knows how Apple defines any of the words in that phrase. How old is retro? Is an old computer on which you can play games a console?
I grew up playing games on early computers, including the Apple IIe. Does the ability to open a spreadsheet in AppleWorks disqualify an Apple II emulator that would otherwise let me play Lode Runner and Choplifter? And if so, why?
I continue to be perplexed by Apple’s (intentionally?) vague designation of “retro” consoles for emulators. Perhaps the company is waiting for the market to figure itself out without having to intervene by selectively banning certain types of emulators? Perhaps rejecting requests to use JIT recompilers is Apple’s way of implicitly drawing the “retro” line?
Jason mentions another interesting point: what about emulating old computers that also happened to have games on them, or emulating old iOS games that are no longer compatible with modern iPhones? There are some precedents for old computers on the App Store: a Sinclair ZX80 emulator was recently updated with the ability to load external ROMs, and there appear or be some Commodore 64 emulators too (some of them with… questionable features). In the age of entire vintage OSes running inside a web browser, I think it’d only make sense for Apple to approve them on the App Store too.
