visionOS appears to work so much better with the PSVR controllers that it’s almost unbelievable that it shipped without hand controllers of its own
App developer & mini painter. I make apps and break things.
UIKit. Swift. Gaming. Warhammer. Generative AI. Husband. 🏳️🌈 He/him.
visionOS appears to work so much better with the PSVR controllers that it’s almost unbelievable that it shipped without hand controllers of its own
@b3ll Q_Q
Filing all my radars before Apple engineering stops listening again until next year 🤣
Looking up old posts to attach videos to radars, and seeing '730 days ago' on all my work for Vision Pro was a gut-punch 💀
Still don't have a headset
@gregggreg @b3ll it's been a year? How long does it take them to commission servers? 😅 How can they ever hope to get anywhere if rollout is this slow
Apple Launches ‘Convince Your Parents to Get You a Mac’ Short Film on YouTube, Then Pulls It a Day Later Without Explanation
https://daringfireball.net/linked/2025/06/22/apple-can-convince-your-parents
@b3ll but wasn't that the point of Apple's private cloud stuff? That the AI would sometimes use it, and that it was as secure as on-device? It should be a transparent, drop-in replacement
I have A LOT of questions about Apple's updated Foundation Models and how they work with the excellent Use Model action in Shortcuts for iOS 26.
Also: did you know that the third-party integrations here are...raw JSON content sent over to the model?
My questions and early findings here: https://www.macstories.net/notes/i-have-many-questions-about-apples-updated-foundation-models-and-the-great-use-model-action-in-shortcuts/
The 'Use Model' action in Shortcuts begs the question — Apple's Foundation Models API is basically a text query. It's completely interchangeable, could be run on the cloud model or through ChatGPT instead.
…why on earth is it restricted to Apple Intelligence-capable devices only, rather than being available across the lineup?
Now that we're going to be building these features into our apps, why isn't there a straightforward cloud-based fallback for older devices?
@stroughtonsmith this is such a flashback to the design choices we were making on Groove Music when there was about to be a Surface Mini to slot between Windows Phone, and Surface. If I wasn’t wearing my glasses this would feel exactly like the Podcasts App we were working on at the time.
@andyl @Joekw a very simple example on my part: on iPhone (compact) layout I want a settings tab. On iPad, I do not — that is exposed elsewhere in the UI. But iPad needs to be able to transition between compact and expanded, so I will have to insert/remove tabs dynamically in lieu of an API (or I just remove the tab completely when device idiom = iPad)
@simsaens unfortunately not with public API (please file a radar!)
The WebKit source code points to a private API that it checks, instead
@everyplace that's just splitscreen; slideover let you pin windows on top, no matter what was going on underneath. There's no way to recreate that currently
I'm finding I'm removing a lot of my Mac Catalyst #ifdefs in my apps and turning them into runtime checks to enable advanced features on iPad, too. I think this is the 'missing link' between iPad and (Mac Catalyst + visionOS) that I talked about two years ago — the common ancestor that was missing between the three UIKit platforms. We finally got it. And it only took some fairly 'small' tweaks to iPadOS to make it viable — sensible windowing & a menu bar. But that enables whole new class of apps
@Joekw @andyl this confused me too — the tab group is a list of sidebar items that resolves to a single fallback view controller from the minimized tab bar itself. E.g. a list of folders in the sidebar would compact down to an 'all folders' view controller of your choosing. You need to provide both the tabs and the fallback
@Joekw @andyl I'm still working my way through the APIs, but it seems to me that the sidebar 'must' show everything, whereas you can customize the available identifiers for the compact mode. But I want to customize both. I expect I will have to monitor size class changes and inserts/remove tabs dynamically instead
It wouldn't surprise me to see Apple start to adopt this language by next WWDC, 'posture' vs 'size class'. I don't expect any new size classes for a folding iPhone, but it for sure would be a distinct posture.
A traditional iPad layout may be too big to fit onscreen, but expanding the iPhone layout alone wouldn't do it justice. That's why we need, and are starting to see, a third, middle option. The mighty mophin' tab controller might serve a purpose after all
@Joekw not, unfortunately