I love my iPad Pro, but, as you know, lately I’ve been wondering about what comes after iPadOS 26. We have much better multitasking now, and key workflow limitations such as file management, audio recording, and long-running background tasks have been addressed by Apple this year. But now that the user-facing system’s foundation has been “fixed”, what about the app ecosystem?
Over at Snazzy Labs, Quinn Nelson has been wondering the same, and I highly recommend watching his video:
Quinn makes a series of strong, cogent arguments with factual evidence that show how, despite multitasking and other iPadOS 26 improvements, using apps on an iPad Pro often falls short of what can be achieved with the same apps on a Mac. There is so much I could quote from this video, but I think his final thought sums it up best:
There are still days that I reach for my $750 MacBook Air because my $2,000 iPad Pro can’t do what I need it to. Seldom is the reverse true.
I’m so happy that Apple seems to be taking iPadOS more seriously than ever this year. But now I can’t help but wonder if the iPad’s problems run deeper than windowing when it comes to getting serious work done on it.
Our desk setups. Federico (left) and John (right).
As we head into the final weeks of 2025, Federico and I figured it would be a good time to update the MacStories Setups page. There’s an ebb and flow to the gear and apps we test each year, and as the fall OS update season fades into the past, it’s not unusual for one or both of us to take stock of our setup and make changes. That’s been very true for both of us this year, but in different ways.
Federico has been focused on simplifying his hardware setup and testing a long list of apps and services. In contrast, I’ve made fewer gear cuts, focusing more on strategic changes to the gadgets I use and settling on a core set of work apps.
The result is that Federico’s hardware setup changes have primarily been updates to his Apple and portable gaming gear. He made the transition from the iPhone 16 Pro Max to the iPhone Air, and couldn’t be happier with the result. He also replaced the M4 iPad Pro with the latest M5 model and moved from the AirPods 4 to the AirPods Pro 3.
Both of us ditched our previous Apple Vision Pro head strap solutions for the Apple Dual Knit Band, which has been a big upgrade. It’s comfortable, and having one dial to adjust both bands is both clever and far simpler than other solutions I’ve tried.
Ayn Thor.
Federico also added the Ayn Thor to his handheld gaming lineup. The Thor, which I also bought this fall, is a dual-screen OLED gaming handheld that runs Android. It’s perfect for emulating dual-screen systems like the Nintendo DS and 3DS, but it has also been excellent for game streaming and testing the emerging world of emulating SteamOS on Android. If game tinkering is your thing and this sounds intriguing, we have two episodesof NPC: Next Portable Console that go in-depth on the Ayn Thor.
Following the comeback of Slide Over in iPadOS 26.1, Apple is continuing to iterate on iPadOS 26 multitasking by restoring functionalities that had been removed from the launch version of iPadOS 26.0 in September. Yesterday, in the third developer beta of iPadOS 26.2, the company brought back drag and drop gestures to put app windows directly in Split View and Slide Over without having to interact with additional menus. To understand how these old gestures work in the context of iPadOS 26, I recommend watching this video by Chris Lawley:
As you can see, the gestures are pretty much the same ones as iPadOS 18, but the interaction is slightly different insofar as the “pull indicator” for Slide Over (re-introduced in iPadOS 26.1) now serves two purposes. That indicator now acts both as a signal that you can drop a window to instantly tile it as one half of a Split View, and it’s also a drop target to enter Slide Over right away. The design is clever, if maybe a little too hard to discover…but that’s always been the case with multitasking gestures that aren’t exposed by a menu – which is exactly why Apple is now offering plenty of options in iPadOS 26 to discover different multitasking features in different menus.
I’m glad to see Apple quickly iterate on iPadOS 26 by finding ways to blend the old multitasking system with the platform’s new windowing engine. Based on the comments I received after publishing my iPadOS 26 review, enough people were missing the simplicity of Split View and Slide Over that I think Apple’s doing the right thing in making all these multitasking systems coexist with one another.
As I argued on last week’s episode of Connected, and as Myke and Jason also elaborated on this week’s episode of Upgrade, the problem with the iPad Pro now is that we have a great foundation with iPadOS 26 and very few third-party apps that take advantage of it beyond the usual names. I suspected as much months ago, when I explained why, in a world dominated by web apps, the iPad’s next problem was going to be its app ecosystem. The web services I use on a daily basis (Slack, Notion, Claude, Superhuman, Todoist – the list goes on) simply don’t make iPad apps of the same caliber as their desktop/web counterparts. So I find myself using Safari on the iPad to get my work done these days, but, for a variety of reasons and dozens of small papercuts, Safari for iPad simply isn’t as good as Safari on the Mac.
Given how the third-party app ecosystem story for iPad is outside of Apple’s control and how most companies aren’t incentivized to make excellent native iPad apps anymore, now that multitasking has been largely “fixed” in iPadOS 26.2, I hope Apple turns its attention to something they can control: making Safari for iPad truly desktop-class and not a baby version of Safari for Mac.
4.1(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer.
As I wrote earlier this year, this isn’t a new problem, especially for developers of popular games on other platforms. Copycat versions of Blue Prince, Palworld, Wordle, Cuphead, Balatro (before it was released on the App Store), and Unpacking have all appeared on the App Store in recent years.
The update to App Guideline 4.1 shows that Apple is aware of the problem, which is a step in the right direction. Hopefully, the awareness will lead to better enforcement, too.
The agreement was framed by Epic and Google as a conclusion to the court battle between the two that has been rumbling on since 2020. But a report from Law360 quotes the Judge overseeing the case as saying the proposals do not go far enough to rectify Google’s behaviour. Judge Donato also wants another hearing in December or January to straighten it all out.
“My concern here is that these proposed modifications … [are] not providing an adequate remedy for Google’s wrongdoing,” said Judge Donato, according to Law360.
This sort of thing isn’t unheard of, especially when the dispute is over a legal issue that takes into account the effect on consumers along with the parties involved. The judge in the case has scheduled hearings for December and January to consider the proposed settlement, but it looks like this case could end up in the U.S. Supreme Court after all.
Late yesterday, Epic Games and Google announced a settlement of their Google Play Store litigation that, subject to court approval, would open Google’s storefront more widely than ever before.
Like Apple’s revisions to its store in response to the European Commission, Google’s settlement is complex, but here are some of the highlights, as reported by Sean Hollister for The Verge:
Whereas the U.S. District Court’s injunction only applied to the U.S. Play Store, the settlement is global.
The settlement also runs through 2032, which extends beyond the three years ordered by the court.
Google has agreed to reduce its standard fee to 20%, and in some cases, 9% depending on the type of transaction.
Google will create a registration system to allow third-party storefronts.
Developer fees for using Play Billing, Google’s payment system, will be separated from the transaction fees.
As I said, though, there’s a lot more to the proposed settlement that you can read in full in the PDF linked in The Verge’s story, and it’s subject to court approval, but it does seem to reflect significant concessions by Google.
What does this mean for Apple and its App Store skirmishes with regulators around the world? Nothing technically; however, contextually, if the settlement is implemented, it should add to the pressure on Apple to open the App Store more widely in the U.S. and elsewhere.
Earlier this year, Andrej Karpathy wrote an in-depth analysis of four sleep tracking methods that Federico recently recommended I read. I’m glad he did, Karpathy, an AI researcher who has worked at OpenAI and Tesla, took the kind of nerdy, data-driven approach that I love.
Over the course of two months, Karpathy plotted sleep tracking results from:
…my sleep scores correlate strongly with the quality of work I am able to do that day. When my score is low, I lack agency, I lack courage, I lack creativity, I’m simply tired. When my sleep score is high, I can power through anything. On my best days, I can sit down and work through 14 hours and barely notice the passage of time. It’s not subtle.
I recommend reading the entire post for all the details of how each tracking method compared on variety of metrics. I’ve long been intrigued by the Whoop band and Oura ring as a companion to the Apple Watch. There’s overlap between the devices, but Karpathy has planted a seed in my brain that may lead to my own multi-device experiments.
In addition to the M5 iPad Pro, which I reviewed earlier today, I also received an M5 MacBook Pro review unit from Apple last week. I really wanted to write a companion piece to my iPad Pro story about MLX and the M5’s Neural Accelerators; sadly, I couldn’t get the latest MLX branch to work on the MacBook Pro either.
These dedicated neural accelerators in each core lead to that 4x speedup of compute! In compute heavy parts of LLMs, like the pre-fill stage (the processing that happens during the time to first token) this should lead to massive speed-ups in performance! The decode, generating each token, should be accelerated by the memory bandwidth improvements of the SoC.
Now, I would have loved to show this off! Unfortunately, full support for the Neural Accelerators isn’t in MLX yet. There is preliminary support, though! There will be an update later this year with full support, but that doesn’t mean we can’t test now! Unfortunately, I don’t have an M4 Mac on me (traveling at the moment) but what I was able to do was compare M5 performance before and after tensor core optimization! We’re seeing between a 3x and 4x speedup in prefill performance!
Looking at Max’s benchmarks with Qwen3 8B and a ~20,000-token prompt, there is indeed a 3.65x speedup in tokens/sec in the prefill stage – jumping from 158.2 tok/s to a remarkable 578.7 tok/s. This is why I’m very excited about the future of MLX for local inference on M5, and why I’m also looking forward to M5 Pro/M5 Max chipsets in future Mac models.
Earlier this year Synology announced that you’d need to use Synology-branded hard drives in its 2025 line of “Plus” branded network-attached storage devices if you wanted full functionality. While you could theoretically use a non-Synology drive with the Synology DiskStation DS225+, DS425+, DS925+ and other models, you’d be unable to create data storage pools, or use volume deduplication.
As Linder reports, six months later, Synology has reversed course on what was a widely unpopular decision among Mac and PC users that was viewed by many as a way to lock them into overpriced drives unnecessarily. The change of direction was revealed in a Synology press release announcing DiskStation Manager 7.3, the OS that runs the company’s Plus line of NAS hardware.
This is great news for Mac users who felt betrayed by Synology’s previous announcement. However, as Linder also points out it does not change the fact that the same “Plus” series of 2025 NAS hardware does not include hardware-accelerated transcoding of H.264 and HEVC video, which previous models supported.
