Ryan Christoffel, 9to5Mac:

On the iPhone and iPad, Apple made the new Creator Studio features available as updates to the existing App Store releases.

On the Mac though, the rollout was a lot more confusing. Apple kept the old iWork apps for Mac available on the App Store and launched entirely separate iWork versions with the Creator Studio features. Starting today, though, that oddity is no more. Per Aaron Perris, Apple has officially removed the old Pages, Keynote, and Numbers apps from the App Store.

If you’ve previously downloaded these apps, you’ll still find them in your download history and can re-download from there. But new users will only see one option on the App Store: the Creator Studio-compatible apps.

One reason — perhaps the reason? — this was necessarily more complex on MacOS is that the iWork apps used to have different bundle identifiers on iOS and Mac. On the Mac, the old (classic?) version of Keynote has the bundle identifier com.apple.iWork.Keynote. On iOS, it was always just com.apple.Keynote, without the iWork part. To make the single-subscription bundle work across both platforms, Apple seemingly needed to unify the bundle IDs, and they unified them using the iOS versions, sans the iWork part. The new Creator Studio versions of the Mac apps now have the same bundle IDs as the iOS versions. You can see this using Terminal, if, like me, you currently have both versions of these apps installed side-by-side:

% mdls -name kMDItemCFBundleIdentifier -r \
    /Applications/Numbers.app 

Result: com.apple.iWork.Numbers

% mdls -name kMDItemCFBundleIdentifier -r \
    /Applications/Numbers\ Creator\ Studio.app

Result: com.apple.Numbers

You can also see from the above that while the display names for the new versions remain just “Keynote”, “Numbers”, and “Pages”, the actual names of the .app bundles in the file system are now “Keynote Creator Studio.app”, “Numbers Creator Studio.app”, and “Pages Creator Studio.app”. That’s how two apps that both appear to have the same name can exist next to each other in the same Applications folder.

I’ll leave the final word to Basic Apple Guy:

Goodbye Keynote, Numbers, and Pages, and long live Keynote: Design Presentations, Numbers: Make Spreadsheets, and Pages: Create Documents

Google, on their Search Central Blog:

Today, we are expanding our spam policies to address a deceptive practice known as “back button hijacking”, which will become an explicit violation of the “malicious practices” of spam policies, leading to potential spam actions.

What is back button hijacking?
When a user clicks the “back” button in the browser, they have a clear expectation: they want to return to the previous page. Back button hijacking breaks this fundamental expectation. It occurs when a site interferes with a user’s browser navigation and prevents them from using their back button to immediately get back to the page they came from. Instead, users might be sent to pages they never visited before, be presented with unsolicited recommendations or ads, or are otherwise just prevented from normally browsing the web.

Why are we taking action?
We believe that the user experience comes first. Back button hijacking interferes with the browser’s functionality, breaks the expected user journey, and results in user frustration.

Good for Google to penalize sites playing such dirty tricks, but, if they believe the user experience comes first, why are they only addressing this now in 2026? Here’s a Reddit thread from 15 years ago: “Why the fuck do websites hijack the back button? Its fucking annoying”. And why are they waiting until June to enforce it? Penalize these dickheads now.

I don’t see much back-button hijacking personally, perhaps because I don’t visit sketchy websites, but this entire issue only exists because of JavaScript. If web pages were documents, this wouldn’t even be possible.

Amazon:

Today Amazon.com, Inc. and Globalstar, Inc. announced that they have entered into a definitive merger agreement under which Amazon will acquire Globalstar, enabling Amazon Leo to add direct-to-device (D2D) services to its low Earth orbit satellite network and extend cellular coverage to customers beyond the reach of terrestrial networks. In addition, Amazon and Apple announced an agreement for Amazon Leo to power satellite services for iPhone and Apple Watch, including Emergency SOS via satellite. [...]

Greg Joswiak, quoted in Amazon’s press release:

“Apple and Amazon have a long and proven track record of working together through Amazon’s core infrastructure services, and we look forward to building on that collaboration with Amazon Leo. This ensures our users will continue to have access to the vital satellite features they have come to rely on, including Emergency SOS, Messages, Find My, and Roadside Assistance via satellite, so they can stay safe and connected while off the grid.”

The Verge’s headline catches my initial reaction: “Apple and Amazon Are Teaming Up to Challenge Starlink’s Smartphone Ambitions”. Apple owned a 20 percent stake in Globalstar, so they were more than a bystander. But I think the deal speaks to the fact that amongst the tech titans, Apple and Amazon are more allies than rivals.

Speaking of John Calhoun, he chimed in on a Hacker News thread last month regarding his experience working with Steve Lemay at Apple:

I think Steve Lemay is a good guy. I kind of fought with him when I was an engineer, he was a young, new designer (at Apple). But I always respected his point of view — even when we argued.

When Jobs came back to Apple in the latter 1990’s “Design” slowly came to have an outsized role. I was one half of the engineering team that owned Preview (the application) when Steve Lemay became a seemingly regular presence in the hallway. As the new “Aqua” UI elements arrived in the OS like the “drawer” and toolbar, Steve and his boss (forgetting his name right now — Greg Somebody?) were often making calls about our UI implementation.

I guarantee that was Greg Christie, who is in my opinion the least-known-but-most-missed person at Apple.

Steve Lemay insisted the drawer live on the right side of the window. This was inexplicable to me. I saw the layout of Preview as hierarchical: the left side of the content driving the right side. You click a thumbnail on the left (in the drawer) the window content on the right changes to reflect the thumbnail clicked on.

Steve said, no, drawer on the right.

“Why? Why the hell would we do that?”

Steve was quick: “The Preview app is about the content. The content is king.”

I admit that I still disagreed with him after the exchange, but I had a new respect for him as a designer because he was able to articulate a rationale for his decision. I suppose I was prejudiced to expect hand-waving from designers.

It’s a good sign when you lose an argument but gain respect for those arguing the opposing side. (And, Calhoun notes, the Preview sidebar eventually did move to the left, after split views replaced drawers in AppKit.)

(Addendum: Steve also invented the early Safari URL text field that also doubled as a progress bar. Instant hate from me when I saw it: it was as if the text of the URL you entered was being selected as the page loaded. So I’m old-school and Steve had some new ideas…)

I had the same reaction as Calhoun when I first wrote about Safari, two days after it was announced and released as a public beta at Macworld Expo in January 2003. (That was a year before I created Markdown, so I had to edit raw HTML just now to update a few broken links to working versions at the Internet Archive.) I wrote then:

Progress Bar Behind Location Field
Hideous. It looks like partially-selected text. Please scrap it.

But by 2009, reviewing the public beta of Safari 4, I had changed my mind, and admitted I was wrong in my initial assessment of the progress-bar-in-location-field combo control:

But I quickly grew accustomed to it, and soon grew to miss it when using other browsers. It was, I soon decided, a damn clever way to show progress in a way that was prominent while the page was actually loading, and without taking up any additional space on the screen after loading was complete.

That innovation is a nice feather in Lemay’s cap.

John Gruber: If I had my druthers, Apple would make a new svelte ultralight MacBook. Not instead of the Neo, but in addition to the Neo. Apple’s inconsistent use of the name “Air” makes this complicated, but the MacBook Neo is obviously akin to the iPhone 17e; the MacBook Air is akin to the iPhone […]