I came across this fun website while browsing the Vision Pro community on Reddit: beautifulthings.xyz is a curated collection of 3D USDZ files that you can download for free on any Apple device. On the Vision Pro, these models can be freely placed anywhere in your environment alongside other windows, allowing you to inspect up close, say, a Spider-Man model, a Lamborghini, or, should you feel like it, a first-gen iPod classic.
Here is, for instance, a screenshot of a nice-looking Italian pizza and a Hylian shield just floating around my living room:
Pizza and Zelda? Yep, that’s me.
According to the website’s creator, more than 100,000 items have been uploaded to the site in the past week alone, and the developers are working on a curated daily feed to showcase the best objects you can view on a Vision Pro.
Fun project, well worth a few minutes of your time even just for opening 3D models of stuff you can’t afford in real life. I hope they’ll consider adding a search functionality next.
Speaking of Apple Music, Apple appears to be testing ways to migrate your music library and playlists from other streaming services to its own.
Chance Miller, writing for 9to5Mac, reports on the discovery made by users of the Apple Music for Android beta on Reddit:
Now, Apple appears to be testing native integration with SongShift. According to users on Reddit, there is a new prompt in Apple Music for Android that asks users if they want to “add saved music and playlists you made in other music services to your Apple Music library.” There’s also a new option for doing this through Apple Music’s settings on Android.
SongShift is an excellent third-party app that we’ve covered over the years at MacStories. However, I’d be surprised if Apple winds up partnering with a third-party developer for this sort of new user onboarding experience instead of building a similar tool itself. Regardless of the direction Apple decides to take, a migration tool makes a lot of sense for anyone who is deeply invested in another service but is interested in trying Apple Music.
I have low vision. A kind you can’t really correct for with glasses or contacts. I also bought Apple Vision Pro at launch. Why would I do this? Well because I’m a nerd who wants to see the future, but also because I was fascinated to see how Apple would handle accessibility for this new product. Apple’s track record on accessibility in the past decade has been stellar, in my opinion, with their teams adding powerfuloptionsevery year and ensuring every new platform has accessibility support built in from the start.
After watching Apple’s WWDC23 session on visionOS accessibility, I knew accessibility on visionOS was an important point for them. But even after consuming as much information on the platform as I could, I knew I had to try it for myself to know the answer to the important question: how well does it work for me?
It’s no surprise to learn that Apple’s Accessibility team did some amazing work for this new platform too, but it’s impressive to see that on day one of the Vision Pro there are already dozens of Accessibility features and accommodations in place. And keep in mind that these are Accessibility options that work with Apple apps and third-party ones, right out of the box. This is the kind of ecosystem advantage and platform integration that newfound tech reviewer Zuckerberg probably forgot to mention in his video.
See also:Tom Moore’s story on trying the Vision Pro with one eye only, Peter Saathoff-Harshfield’s Mastodon thread, Shelly Brisbin’s story for Six Colors, and Ryan Hudson Peralta’s fantastic overview (via 9to5Mac) of using the Vision Pro without hands, which I’m embedding below.
This week on AppStories, we move on from hardware to explore visionOS, where it hits, where it misses, and what we’d like to see in the future from the OS.
On AppStories+, we discuss the developer strap and how it could potentially gain new features in the future, as well as the idea of using a headless Mac as a Vision Pro accessory.
Adi Robertson writes for The Verge about the Vision Pro’s lackluster support for multiple users and how hard it is to share the device with someone else:
The Vision Pro is $3,499 and only one person in your household can ever use it fully, which makes no sense at all. The privacy issues are technically there on the Vision Pro — letting anyone else use it without setting restrictions in guest mode grants them access to everything you’ve got on the headset, including your messages. But as my experience demonstrates, they may not even be able to use it well enough to get that far. You can start a guest session by holding the Vision Pro’s left-side hardware button for four seconds, but you can’t store a second user’s information so they can log in quickly next time without calibration. Basically, imagine if every time you passed an iPad to somebody else in your family, they had to spend a minute poking colored dots.
The worst part of using the Vision Pro for the past two weeks has been trying to get someone else in my family to use it. As a novel type of computer that almost demands to be tried by different people in your life, the lack of multi-user support at launch is a major cause of friction for me right now. I’ve been able to get a separate set of light seal and cushion for Silvia and my mom, but the problem is visionOS. There is a guest mode, but every time someone other than me wants to try the Vision Pro, they have to do the eye setup process from scratch. It gets annoying quickly without the ability to save calibrated presets for other people.
In the demos I’ve conducted for people in my family over the past week, I’ve also realized how hard it is to guide someone else through visionOS for the first time. I wish Apple had built a dedicated “demo app” for new users who try the Vision Pro – sort of like a pre-installed (and interactive) version of Apple’s guided tour, which is also very similar to the demo I had at WWDC last year.
One change in iOS 17.4 is that the iPhone now supports alternative browser engines in the EU. This allows companies to build browsers that don’t use Apple’s WebKit engine for the first time. Apple says that this change, required by the Digital Markets Act, is why it has been forced to remove Home Screen web apps support in the European Union.
The upshot of Apple’s answer to why PWAs no longer work in the EU is that it would be hard to implement the same thing for other browsers, few people use PWAs, and the Digital Markets Act requires browser feature parity, so they took the feature out of Safari. Each step in that logic may be true, but it doesn’t make the results any more palatable for those who depend on web apps, which have only grown in importance to users in recent years.
For anyone who was there when Steve Jobs declared web apps a ‘Sweet Solution’ when developers clamored for Apple to open up the iPhone’s OS to native apps, taking them away in the face of regulations that force Apple to open up to alternative browser engines carries a heavy dose of irony. It also illustrates that when the motivations behind software design are driven by lawyers and regulators, not market forces, things get weird. And as iOS 17.4 shows, EU-iOS is solidly in weird territory.
PWAs may not be a top 10 feature of Safari, but that’s at least partly the result of the company’s own decisions because it wasn’t until recently that PWAs became viable alternatives to some native apps. Web apps aren’t going anywhere, and choosing to eliminate PWAs from Safari instead of doing the work to extend them to all browsers runs counter to the open web and the momentum of history. I hope Apple reconsiders its decision.
While I admire the great care Apple takes before it brings a product to market, I do sometimes think that the company is missing out on some potentially great products because they’re not willing to get weird and risk failure. Consider the original MacBook Air, which was deeply weird but led to a second-generation model that became the template for Apple’s laptop design for the next decade!
The technology already exists today for Apple to create some wild stuff, the likes of which we’ve never seen from them. The Vision Pro has broken the seal. Let’s get weird, Apple.
As a longtime proponent of Weird in my computing life (I mean), I love that Apple released the Vision Pro in its current form: it’s a weird product with tons of rough edges and I want to make it my main computer. But, like Jason suggests, there are so many other product categories where I’d like to see Apple try and make something weird and wonderful. I have some experience with Android foldables, including some recent ones, and while I like the form factor a lot, I can’t help but think how glorious an Apple device that unfolded to become a larger tablet could be.
Luke Miani (who runs a great YouTube channel I’ve been following for a while) has created the sort of beautiful monstrosity I would absolutely consider for my own workflow: he was able to remove a display from an M2 MacBook Air and use the remaining “macOS slab” as a fully functioning computer for the Vision Pro’s Mac Virtual Display mode.
If the sentence above doesn’t make any sense to you, go watch the video first:
The idea of using headless MacBooks has been around for a while, but I was wondering if it’d find new life with the Vision Pro and the ability to virtualize a Mac display or use Universal Control with it. Which is why I’m very glad that Miani tried this first and confirmed that, yes, a headless MacBook Air totally works as a very expensive Vision Pro accessory.
The reason I’m so fascinated by this project is that I find the current keyboard/trackpad setup on the Vision Pro lackluster. If you don’t want to use a Mac in the middle, your best bet is to get an accessory like a Twelve South MagicBridge to hold a Magic Keyboard and Magic Trackpad together. However, as I shared earlier this week, that accessory’s form factor is not ideal for lap usage:
I’m waiting for twodifferent “trays” that promise a laptop-like configuration, but as I’ve been told by others online, those don’t fix the fact that the desktop Magic Trackpad doesn’t offer the sort of palm rejection features typically found in Mac laptops.
Which brings me back to Miani’s wonderfully weird and amazing experiment: what if the input portion of a Mac laptop could become a more portable and accurate input method for the Vision Pro, with support for Mac Virtual Display when needed? What if a keyboard computer (Apple II says hi) could be used with the Vision Pro or docked at a desk with a Thunderbolt hub and external monitor?
Realistically, Apple should make this kind of accessory and I’m so surprised that their answer for people who want to work solely on a Vision Pro is “buy the keyboard and trackpad from a few years ago that still have a Lightning connector”. I’m not going to do this to my own MacBook Air. But you have no idea how tempted I am to try.
The EU has decided that Apple’s iMessage service is not a core platform, meaning that it will not be subject to regulation under the Digital Markets Act (DMA). Jon Porter writing for The Verge:
The decision is the culmination of a five month investigation which the Commission opened when it published its list of 22 regulated services last September. Although it designated Apple’s App Store, Safari browser, and iOS operating system as core platform services, it held off on making a final decision on iMessage until an investigation could be completed. A similar investigation into iPadOS is ongoing.
In the same press release, the European Commission also decided against designating Microsoft’s Edge browser, Bing search engine, and advertising business as core platforms subject to the DMA.
As you may recall from our prior coverage, Apple’s Safari browser, App Store, and iOS are all subject to the DMA, but the EC deferred making a decision on iMessage. In the interim, Apple announced it would support the RCS messaging standard that will exist alongside iMessage in Apple’s Messages app and will include several features that previously were unavailable to non-iPhone users who messaged iPhone users. It’s likely that Apple’s decision to incorporate RCS, which the company says is coming later this year, and iMessage’s relatively small European market share played a role in the EC’s decision, although the reasoning behind the decision was not shared by EU regulators.
](https://cdn.macstories.net/banneras-1629219199428.png)