Om Malik (2023):

One of the key advantages of MacWhisper, as it utilizes the Whisper technology, is its superior accuracy in transcriptions compared to other services I have used. I was an early adopter of Rev.com and eventually switched to Otter.ai, for which I paid approximately $100/year. However, I have since canceled my subscription.

[…]

After comparing the audio transcripts from MacWhisper and Otter, I found that while Otter’s formatting is superior, there is hardly any difference in the transcriptions. I started with the free model, which was sufficient for my needs, and eventually upgraded to the large models. Nowadays, I primarily use MacWhisper to transcribe my voice memos, which I then import into Lex.Page.

Bon Adamson:

Whisper, which is made by OpenAI, has the distinct advantage of allowing you to transcribe audio in almost any language you may ever need to. For the time being, Otter can only transcribe English. The benefits of better accuracy and accurate punctuation that the service already holds over Siri hold up across other languages as well. If you’re looking to transcribe non-English audio accurately, Whisper is definitely the best option available on Mac.

Dan Moren:

By taking advantage of OpenAI’s Whisper framework, Audio Hijack can now take any audio it’s recording and generate a text transcript. While this process was possible before—see Jason’s lengthy post about his workflow—it required a lot of fiddling and several different tools to accomplish; it’s certainly a lot easier to simply drop Audio Hijack’s block into your existing session. If you record multiple sources, it can even appropriately label each one—though if you record multiple people via one input, say the other end of a Zoom call, it can’t distinguish between the various participants.

Inscribe (2026, Hacker News):

Apple’s new SpeechAnalyzer is the most accurate on-device speech engine we tested. It beat every Whisper model we ship, including Whisper Small, on both the clean and the noisy half of LibriSpeech, while running roughly three times faster than Small. And the API it replaces, SFSpeechRecognizer, came last on clean speech: behind even Whisper Tiny, a 40MB model.

[…]

The new API cuts word error rate by 3.5 to 4x on the same audio: from 9.02% to 2.12% on clean speech, and from 16.25% to 4.56% on noisy speech. There is no accuracy trade-off to weigh; the new API wins everywhere we measured, and it produces punctuated, cased text where the legacy engine’s output is rougher.

[…]

All five engines ran comfortably faster than real time: between roughly 12x and 40x on the M2 Pro, meaning an hour of audio transcribes in about 1.5 to 5 minutes on-device. SpeechAnalyzer was about 3x faster than Whisper Small per second of audio while beating it on accuracy.

Yuki:

SpeechAnalyzer’s ReportingOption.fastResults reads like a knob you’d reach for when you want to trade power for latency. That framing is what cost me the afternoon.

[…]

If a recording matters — and in a notes app, a lost meeting is the worst thing that can happen to a user — then the container you write while recording has to be PCM in CAF. Not m4a, and not AAC-in-CAF either.

[…]

AVAudioEngine’s inputNode silently ignores your device selection

[…]

I wanted summarization to run on-device. Everything else in Nib’s transcription path does, the audio never leaves the machine, and it would have been a much cleaner story to tell.

But 4,096 tokens for the Foundation Models isn’t enough.

Previously:

• Apple Foundation Models in appleOS 27
• WhisperPad Rejected From the Mac App Store
• Overcast Transcripts
• Generated Transcripts in Pocket Casts
• Apple Podcasts Transcripts
• Dictation and Predictive Text in macOS Sonoma and iOS 17
• macOS vs. Dragon Dictation

Thijs Xhaflaire (via Ric Ford):

Jamf Threat Labs discovers and investigates CrashStealer, a C++ macOS infostealer that impersonates Apple's crash-reporting framework to harvest browser credentials, cryptocurrency wallets and keychain data, encrypting stolen files with AES-GCM before exfiltrating them to a remote command-and-control server.

[…]

Unlike the payload it eventually installs, the dropper is properly code signed and notarized: it is a universal (arm64 and x86_64) binary signed with the Developer ID Emil Grigorov (WWB7JA7AQV), has hardened runtime enabled, and carries a stapled notarization ticket. Notably, the disk image itself is signed as well, not just the application inside it, which is uncommon in malicious DMG delivery where the container is typically left unsigned.

[…]

That file supplies the curl command the dropper runs next. Staging the first hop on a trusted developer domain keeps the initial network activity inconspicuous.

[…]

[The script] clears extended attributes on the staged bundle with xattr -cr, makes the inner binary executable, strips the payload's existing signature and re-signs it ad-hoc (codesign --remove-signature followed by codesign -s - --force --deep --no-strict), registers it with Launch Services via lsregister -f, and finally launches it in the background with open -g -n.

Previously:

• Notarized Mac App That Downloads Malware
• Fake Mac Apps on GitHub
• Notarized Atomic Stealer (AMOS)
• More Notarized Mac Malware
• App Transport Security

Malcolm Crawford (Mastodon):

The open-plan floors make it hard to concentrate. The building is so large that getting from one meeting to the next eats real time out of the day. It’s common for people to run meetings with colleagues over Webex — colleagues on the same campus, sometimes no more than two hundred yards away.

Ironically, Apple Park replaced a campus that did far better on the same measure without ever trying to. Infinite Loop produced far more of the accidental, cross-team contact Apple Park was explicitly built to create. Working out why starts with what Infinite Loop got right by accident. It continues with what the research on office proximity says about why that kind of thing happens at all. And it ends with what Apple Park could become instead — including a version of the fix Apple already trusts enough to run for a hundred people a year.

[…]

There’s no obvious focal point for the whole site — most sections have their own sitting area and their own coffee bar, but nothing plays the role Caffè Macs and the IL1 coffee bar played together at Infinite Loop. Caffè Macs at Apple Park seats a thousand people and feels built for throughput, not conversation. Everything is organised per-segment rather than around a shared centre, which is convenient for the people in that segment and useless for the discovery-by-accident that made the old campus work.

[…]

By multiple accounts from people who were there during design and construction, the site was flagged as under-provisioned for meetings and conferences before it even opened.

Via Jason Anthony Guy:

Apple Park is a beautiful structure, but is not terribly conducive to focused or collaborative work. Even as an occasional visitor I found it overwhelming. Employees sit shoulder to shoulder, voices bounce off and bleed through glass walls, and privacy is a virtual impossibility. My friends and colleagues who worked there regularly found it difficult to be productive.

I worked in Infinite Loop (Building 3, 2nd floor) for thirteen years (right below Developer Publications, where Malcolm spent a good portion of his Apple career). I loved IL because its design made serendipitous encounters easy. Whether it was sitting outside Caffè Macs or in the IL 1 Atrium, I would inevitably bump into someone and have a conversation that furthered an in-flight project, sparked something new, or simply reinforced the social ties that bind colleagues.

It helped that at that time, Apple had perhaps 10,000 employees, most of whom were in or near IL. After iPhone came about and IL started getting locked down, much of the natural collaboration dissipated, disappearing behind badged doors and disclosures.

Ken McLeod:

IL provided a place to focus on your work[1], as well as seating spaces that are out of the flow of traffic where you can have an informal meeting[2]. At AP, every collaborative space is effectively in the middle of a hallway. That turns out to be enormously distracting, both to you and to those people trying to work in the glass bullpen right next to it.

[1] before all cubicles and offices became multi-person shared spaces

[2] before all those spaces were filled in with more offices

Helge Heß:

“The IL1 atrium really was the crossroads of the company in those days” I really don’t think that this is true literally by any means. Assuming “those days” overlap with the time I’ve been there (pre Park). The XFs in IL have been extremely scarce. IL was way too small and overloaded, I’d actually say it was very similar to Apple Park. No one really wanted to work there in those tiny offices with multiple people 🤷‍♀️

Steve Hayman:

I loved the IL1 atrium. I’d sit there and hope that someone like MMalc would wander by, and they often did. It was a real destination for field people who didn’t get to visit the mothership very often. I miss that. AP had nothing like it.

Eric Schwarz:

I think of my days in college—most dorms residence halls were not air conditioned, so at the end of August, you had to open your window (often to place a box fan) and door to create some airflow. People walking through the building would meet by chance. Newer buildings tended to be less lively and more like a hotel—all the doors closed and rarely much activity. Through renovations, most of the buildings have had air conditioning added, dropping those interactions over the years.

Previously:

• Apple and Design Details
• Apple Park’s Open Work Spaces
• Apple’s New Campus

Update (2026-07-22): Dr. Drang:

As you may know, the Lumon Industries building that Mark, Helly, Irving, and Dylan work in is a former Bell Labs facility in Holmdel, New Jersey. I first learned about the building several years ago, when I read Jon Gertner’s excellent history of The Labs, The Idea Factory. It’s a distinctive place designed by Eero Saarinen in the early 60s.

Bell Labs was known for the fruitful collaboration of its researchers, often started through chance meetings in the hallways of other Bell Labs facilities. The new Holmdel building was supposed to further that sort of teamwork, but things didn’t work out as planned.

macintog:

I worked in IL1 for over a decade. The day I saw the open-plan spaceship, I knew I would never set foot inside. There are more rewarding ways to work in a barn.

Aleem Shaun:

I’ve used Day One for more than a decade. It was an excellent journalling app. Private, minimal, easy to use, with excellent features such as geolocation, weather, ‘On this Day’, and book printing. Features that got out of the way and either worked quietly in the background or appeared only when you summoned them. That’s changed.

Now there are new subscription tiers. Previously, the tiers were Free and Premium. Simple. Premium included sync and a few other things that I can’t remember, but it was compelling enough that I’ve been a Premium subscriber from the beginning. Now, without consultation, I’m Silver (not Premium), and there’s a new, more expensive AI-driven tier, Gold. I don’t object solely on that basis. You would think I could just choose to remain on ‘Silver’ and all would be well. But no. Even with these features turned off in settings, I’m visually prompted in the app to upgrade to Gold and use the Daily Chat (with AI), which I’ve turned off and can only use if I upgrade. And yet, there it is, taunting me.

Via Eric Schwarz:

Even Apple is guilty of doing this in the Settings app and the former iWork apps.

Previously:

• $10 Off at Fandango
• Automattic Acquires Day One
• Productivity Apps and Subscription Pricing

Chance Miller:

Here are the new monthly prices for Apple Music and Apple One as of today:

Apple Music

• Individual: $11.99 (up from $10.99)
• Family: $19.99 (up from $16.99)
• Student: $6.99 (up from $5.99)

Apple One

• Individual: $19.95 (unchanged)
• Family: $27.95 (up from $25.95)
• Premier: $39.95 (up from $37.95)

The price increases for Apple Music come after Spotify announced its own round of price hikes earlier this year, which Apple poked fun at on social media. Even with today’s price hikes, though, Apple Music remains cheaper than Spotify.

Lee Peterson:

Apple Music no longer makes sense when I’m already paying for YouTube Premium. Apple Music goes up to £11.99, YouTube Premium is £12.99 and on top of a good music service you get no ads on YouTube.

Mike Rockwell:

Distilling my longtime argument down to its simplest bit, I’d ask “do you want to pay $10 a month for music for the rest of your life?”

But truly, it was never going to just be $10 per month. The price was going to go up over time. It was going to get more expensive to have access to the same music.

If you purchase your music, though, I think most people would reach a point in their life where they stop buying new music entirely or they’re only buying a few albums per year. The cost of music would go down for you over time.

That was my thinking, too, but then I found that music I’ve purchased from Apple won’t work on my HomePod. I refuse to condone that behavior, so now I have two solid reasons not to subscribe to Apple Music.

Joe Rossignol:

While the monthly and annual prices of AppleCare+ plans for Macs and iPads received a slight increase this week, AppleCare One continues to start at $19.99 per month in the U.S., making the multi-device plan even more valuable.

Previously:

• Apple Financial Statements: Products vs. Services
• Apple Hardware Price Hikes
• Apple’s Q2 2026 Results
• Apple Services in 2025
• AppleCare One
• Spotify Profitable
• AppleCare+ Only As a Subscription
• Apple Services Price Hikes

John Gruber (Mastodon, 2):

Some of [Cook’s letter] remains true, but has lost some truthiness — and truthiness matters. But some of it is no longer true, period. It’s no longer just “one small part” of Apple’s business that serves advertisers. Here in 2026, search results in the App Store not only show paid ads — frequently for casinos — but the search results are visually dominated by paid ads now that Apple has added a second ad to results. Apple News+ is a paid subscription that offers a genuinely great value for the number of paywalled publishers whose content it includes, but articles on the News app tend to include the weirdest AI-generated ads on the Internet. (How many young blond women am I supposed to believe need hearing aids?) And — at this writing, still “coming soon” — Apple is launching ads on Apple Maps. Apple Maps remains free of charge to use, so according to Tim Cook, we’re not the customer. We’re the product. Or, if you prefer, our frustration is the product.

[…]

The ratio of ads to organic results in App Store search — especially when measured in screen area — is clearly not aligned with Cook’s 2014 statement that “Our software and services are designed to make our devices better. Plain and simple.” Obviously not. App Store search today is designed primarily to generate more revenue for Apple. That’s not criminal, but it’s a change.

[…]

What gave Tim Cook’s privacy letter heft in 2014 wasn’t just the clarity of its plain language, but the fact that you didn’t have to take his word for it that the ads Apple showed you respected your privacy, because Apple didn’t show you ads in 2014. Apple today can’t say that.

[…]

John Ternus should return Apple’s privacy policy to its 2014 clarity. The trust Apple would earn from such a move would far out-value whatever revenue these ads pad to their already hefty and ever-increasing quarterly Services numbers.

I wish that were the case, but I fear this is kind of a Hotelling’s Law situation, where Apple can get most of the benefit by being just slightly better on this axis. Where else do its customers have to go?

Jeff Johnson (Mastodon):

In the second fiscal quarter of 2018, services generated $9 billion in revenue (net sales), whereas in Q2 2026, that amount had grown to $31 billion! In this blog post, I want to focus on understanding the relative financial importance of products and services for Apple.

[…]

In 2025, services were 42% of Apple gross margin. How does 26% of net sales become 42% of gross margin? The explanation is that services have a much lower cost of sales. The products gross margin was 37% of products net sales, while the services gross margin was an astonishing 75% of services net sales. In other words, Apple services are almost pure profit!

Does this 75% account for TV and movie production costs?

With persistent general inflation, consumers do not have unlimited money to spend on Apple products. At least in the near future, it’s reasonable to question how much further room is available for growth in profits from Apple products. To satisfy the demands of investors, Apple executives including CEO-elect John Ternus may be forced to rely even more than before on growth in services, which do not face as much pressure on cost of sales as hardware products.

Previously:

• Apple Services Price Hikes 2026
• Apple Hardware Price Hikes
• App Store Personalized Recommendations and Keylogging
• Apple’s Q2 2026 Results
• A Letter to John Ternus
• Ads in Apple Maps
• Blurring App Store Ads and Search Results
• Apple Services in 2025
• More App Store Ad Spots
• Apple Services Price Hikes
• Nowhere Else to Go

Jared Sorge:

I know there are options out there like Paddle, FastSpring, and Lemon Squeezy that have worked for many apps like mine over the years. But I also wanted something simple for my users. Not to mention Apple Pay was a must-have.

I believe all the services he mentions do support Apple Pay.

• RevenueCat serves as the source of truth for whether or not a customer is licensed.

• I create RevenueCat customer IDs from local iCloud identifiers (more specifically, calling userRecordID() on my CKContainer in CloudKit).

• When the user makes a purchase, they earn an entitlement that I look for in Arborist to grant them a license.

He doesn’t need to run his own server, and the purchases are automatically tied to the user’s iCloud account, so there are no e-mails or serial numbers to deal with. On the other hand, well, it’s all dependent on the Apple Account.

The app, which helps manage Git worktrees, is shipping now.

Previously:

• Locked Out of Apple Account Due to Gift Card

Bruno Brito (release notes):

In Tower 15, we introduced the “Fully Merged” badge and Automatic Branch Management to help you keep your repository tidy. With Tower 17, we’re taking the detection behind that badge to a whole new level. […] Tower now matches your local branches against merged pull requests from your hosting service, such as GitHub or GitLab.

[…]

Trust is everything when deleting branches — so we redesigned the “Fully Merged” hint view to show you exactly which checks matched.

[…]

One that is particularly noteworthy is that updating submodules is now significantly faster! Tower gathers each submodule's Git data concurrently instead of one at a time—something you will especially notice in repositories with many submodules.

I’m sad that they got rid of the yellow icon.

Previously:

• Git Tower 16

Federico Viticci (Mastodon):

The AI frontier from the two big labs (and – we have to be honest with the numbers here – probably SpaceXAI and Meta now, too) is in a completely different league at the moment. I spent my first couple of weeks with Siri AI trying to convince myself that I could replace Codex with Siri AI, and that was the wrong approach. There is a potential future in which Siri AI can become a more proactive and capable agent, but that’s not what Apple is shipping this year.

[…]

Siri AI is a dramatically better Siri for typical Siri stuff. The new Siri understands your commands and nuanced requests better because of the LLMs behind it; it can often perform multiple requests in one go (such as setting multiple timers with one command); the new expressive (and customizable!) voices sound great, and they’re terrific at reading and summarizing notifications. Apple’s first advantage compared to other chatbots is right here: only Siri can integrate with the iPhone and iPad to this extent, so even if the Foundation models aren’t as smart as the competition, Siri can do a lot more for most people on their devices because neither OpenAI nor Anthropic have OSes they can control.

[…]

The biggest issue I’ve encountered is the inconsistency of it all. Very often, the new Siri AI still replies with a generic “Uh oh, something went wrong“ error that doesn’t explain what the error was or why it happened. Sometimes, I ask a question via voice, and it errors out, but then a few seconds later, I type the same question in the app, and it’s fine.

[…]

My problem is that, right now with Apple’s own apps, both the index and Siri’s ability to perform actions are very inconsistent. The assistant hallucinates abilities it doesn’t have, and it frequently just doesn’t work.

Dan Moren:

The good news is that Siri AI is capable: impressively so, at times. In the lowest of low bars, it certainly beats the pants off the previous incarnation of Siri, but its access to your own personal data and all of the app on your phone also unlocks a host of new possibilities.

But it’s also not without the pitfalls that underlie all LLM-powered chatbots: errors in understanding, hallucinations, and so on.

[…]

The app itself is pretty barebones, letting you view those conversations in List or Grid layouts, select multiple conversations to delete them, and pin or rename any single conversation. In Settings : Siri, you can choose to either open to the overview or to a new conversation and decide whether old conversations are kept for 30 days, 1 year, or forever. It’s a little strange that one-off queries (“What’s the average height of the Norwegian World Cup team?”) are stored alongside more involved conversations (“Can you help me build a specific RSS feed for this site?”); I also ended up with a few orphan blank “New conversations” which I deleted, but it’d be nice if you could filter to find those. Conversations are fully searchable and sync between devices via iCloud.

John Voorhees:

Despite the current limitations, if you use chatbots as a replacement for Google Search, you’ll probably have a good experience with the new Siri app. That’s because even in these early betas, if you ask Siri something like, “Give me a day trip itinerary for a trip to Chicago this Saturday,” you’re likely to get good but pretty middle-of-the-road recommendations. From there, though, you can drill down with follow-up queries to get something more in line with your tastes. The results include source links you can follow, too. Given the ad-strewn mess that web search has become, using Siri for this sort of thing is a meaningfully better experience.

The one caveat on Siri’s world knowledge is that it’s roughly 2-3 weeks stale in some places.

[…]

A good example is Music. You can prompt Siri to play a song, but most of the rich metadata in the app isn’t exposed to Siri, which is a shame because it is exposed elsewhere, for example to AppleScript.

Previously:

• macOS 27 Public Beta
• iOS 27 Public Beta
• No Siri AI in EU
• Siri AI Announced

Update (2026-08-04): Benjamin Mayo:

Thanks to the top-to-bottom revamp that is Siri AI, Siri is reliably intelligent. Finally. We are still in the midst of beta season, and Apple is yet to confirm whether Siri AI will formally launch with iOS 27 in September or sometime later in the year, but the feature is up to scratch. There are bugs and glitches and edge-case quirks, but on the whole, it wipes the floor with old Siri and is competent enough to supplant my everyday usage of other chatbots too.

[…]

Siri AI can get a snapshot of what’s on screen, but it cannot control the UI for you autonomously. As such, if you ask it to do something outside of its library of available app actions, it will say it can’t do that. Often, it can quote the relevant steps for you to do it yourself, but obviously that falls short of the ideal experience. This feels a bit lacklustre to people already embracing AI agents en masse. Claude and Codex on Mac do not hit these walls; they are all too keen to move your mouse for you and run terminal commands until the job is done.

Previously:

• ChatGPT Work and ChatGPT Classic
• Claude Desktop App
• Perplexity Personal Computer
• Codex for Almost Everything

Wade Tregaskis:

In short: if you have any file in your app (or whatever it is you’re trying to get Apple to sign) that is over 4 GiB, you must use a disk image (DMG) to package it for notarytool, not a zip file.

This is because support for files larger than 4 GiB requires using the “Zip64” zip file format, which would be fine except Apple’s notary servers can’t handle them.

Previously:

• altool Update and notarytool

Update (2026-07-22): Rosyna Keller:

It’s recommended to notarized exactly what you’re going to ship to users and shipping zips is extremely risky because you never know what tool the user will use to decompress the file.

Multiple unzipping tools will strip necessary extended attributes that could cause the code signature to fail to validate. This is especially true if you put non-code files in “code places” and they have to be signed with an extended attribute.

Matt Burgess (MacRumors, ArsTechnica):

On Thursday, San Francisco city attorney David Chiu sent legal notices to Apple and Google demanding that they remove from their app stores 13 face-swapping apps, which allow users to create AI-generated nonconsensual nude images. The letters say the Silicon Valley giants should stop “aiding and abetting” the sale of explicit deepfake images and “sever” business relationships with the app developers.

[…]

Researchers have repeatedly found and reported apps in Apple’s App Store and Google’s Play Store that allow people to generate sexual images using AI—including some apps being rated as suitable for use by children. While new laws and bans aim to tackle the scourge of explicit deepfakes online, technology and social media companies consistently direct millions of people toward the harmful tech.

Both Apple and Google have developer policies that prohibit pornography, abuse, and harassment on their platforms.

Burgess gives the impression, which is my base assumption, that these 13 apps were clear about what they do, so App Review has no excuse for missing them. But I’m sure it’s keeping us all safe in other regards.

Meanwhile, in a preprint research paper published in May, researchers from Cornell University and Georgetown University identified 420 apps offering general face-swapping capabilities on Google’s and Apple’s app stores. They tested 155 to see if they could be used to create face swaps with nude images; in 70 percent of cases, it was possible, with the apps not including safety measures to prevent this.

Previously:

• Sirius Pomodoro
• Apps for YouTube℠™®•!
• Sanctioned Entities Slip Through App Store Controls

Update (2026-07-21): Danny Bradbury:

Chiu isn’t arguing that hosting an app automatically makes a platform liable for what it does. Platform operators already won that battle with Section 230 of the Communications Decency Act. That 30-year-old law says websites generally aren’t responsible for content posted by users, allowing platforms to host user-generated content without getting sued every time someone defames someone in a comment thread.

Courts have often extended those protections to cover app stores too. Apple and Google are treated as distributors of whatever a third-party developer uploads, rather than publishers.

Chiu is attempting to sidestep that argument by focusing on the companies’ payment systems, noting that Apple and Google collect a cut of every in-app purchase. According to the Tech Transparency Project (TTP), that means they profit from apps that generate revenue by creating non-consensual intimate imagery.

Hartley Charlton:

The European Commission yesterday adopted new exemptions to its Batteries Regulation that free the Apple Watch and AirPods from having to offer user-removable and replaceable batteries.

[…]

The reasoning largely mirrors why devices like electric toothbrushes were already exempt: Opening a compact, sealed enclosure and failing to reseal it properly could let water in and create a safety risk. Products can also qualify for exemption if their construction makes battery removal inherently dangerous, or if there is no realistic way to build in user access given current manufacturing methods.

[…]

The iPhone was already exempt from the removability rule under the original regulation, thanks to its battery cycle life and water resistance rating.

Marcus Mendes:

Although the Commission has adopted the exemption, it must still undergo scrutiny by the European Parliament and the Council of the EU.

[…]

To read the European Commission’s full delegated act, follow this link.

Previously:

• DMA Compliance: Watch and Headphone Interoperability
• European Union USB-C Mandate
• EU Wants All Phones to Work With Interoperable Chargers

Update (2026-07-20): See also: Hacker News.

Update (2026-07-30): Rui Carmo:

This is one of those exceedingly rare cases where EU legislation has produced an unambiguously good outcome: from February 2027, Logitech’s European wireless devices will ship with hard-pack, user-replaceable batteries, and Logitech will sell certified replacements.

Paul Kafasis:

With last year’s release of MacOS 26 (Tahoe), Apple made a mess of app icons. In the first betas of MacOS 27 (Golden Gate), however, there are signs of a turnaround. We’re urging Apple to continue making improvements, by restoring the ability for MacOS app icons to have distinct shapes.

[…]

After decades of beautiful, memorable Mac icons in varying shapes, Tahoe flattened personality to obtain bland uniformity. The platform is worse for it.

Past icons weren’t just more expressive. They were also more usable. Having distinct shapes provided a useful way to tell icons apart. Tahoe eliminates that cue by forcing everything into the same squircle, leaving color as the primary way to tell icons apart at a glance.

Jason Snell:

Kafasis makes the important point that uniform shapes make it more difficult for users, especially those with vision issues including color deficiency, to differentiate between icons.

John Siracusa:

Squircle Jail is the worst design-related thing Apple has ever done to Mac developers, and probably the worst icon-related thing it has ever done, period. Incredibly developer-hostile.

If squircled icons are actually better, then let that design win in the market. That’s how we transitioned from the classic Mac OS icon style to the more photorealistic Mac OS X icon style. Developers adopted it because they wanted to, and because users desired it.

John Gruber (Mastodon):

The squircles, I will point out, are not in and of themselves the problem. The problem would be the same with any mandated shape, like, e.g., VisionOS’s circles.

[…]

I can’t think of any other design crime Apple has ever foisted on Mac developers that I’d argue (with Siracusa) was worse.

[…]

It’s like Apple decided every single one of its own apps must wear a stupid-looking hat, and they put those stupid-looking hats on third-party apps too, whether the developers of those apps want them or not. Scratch that. Not hats but helmets.

[…]

Just the mere silhouette of the old Keynote icon is more recognizable, and thus more iconic, than any icon on any platform from Apple today.

Jeff Johnson:

The traffic sign analogy hits me personally, because the StopTheMadness icon used to be shaped like a stop sign, but I was practically forced into making it a generic road sign.

Gus Mueller:

I get why Apple did it, but I think it’s completely wrong for the Mac.

Marcin Wichary:

On his blog, Jim Nielsen writes how Apple filed away so much expression by forcing rigid icon bureaucracy in macOS. Nielsen focuses mostly on distinctiveness; previously, you could make the icon unique by its general shape or the shape of its contents, but one of these two levers has now been taken away[…]

[…]

However, one also can’t help but notice how ugly and amateurish the Creator Studio icons are, so it all feels absolutely like a net negative – the new system took something away and the proposed replacement feels low quality[…]

Rui Carmo:

I, too, find the squircles aesthetically offensive and utterly pointless.

[…]

The part that genuinely breaks my brain, though, is that I now find icons on Linux more distinctive than on macOS, which would be impossible for my ten-year-ago self to believe. The platform that built its reputation on craft and visual identity has spent a year sanding it off, while the one everyone used to mock for its inconsistency is where individuality survives.

Jeff Johnson:

The subliminal, Orwellian message of the squircle jail is that all software is subservient to Apple, merely accessories to Apple devices, interchangeable cogs in the machine.

Mario Guzmán:

Had to grab the rest of the icons from #MacOSX Leopard. Gosh, they’re so, so pretty. So finely crafted. Gorgeous. Love it.

Dr. Drang:

I agree, but Apple’s 50th anniversary has gotten me thinking a lot lately about the early days of the Mac, so it’s only natural that my mind shifted to the highly constrained icons Mac applications had back then.

[…]

Many of the complaints about squircle jail are about the loss of icon elements that “stick out” from the rest of the design. As you can see, this idea was there from the very start; the hands stick out from the tilted rectangles.

John Gruber:

I never loved the hand on these icons. It felt too uniform. It functioned like a “this is an application” badge, but such a badge never felt necessary to me.

[…]

I think it’s less that Apple gave up on them and more that it came into focus that the “hand holding a pen over a diamond-shaped document” convention was intended for document-based apps. It signified “This is a creative tool that you use to create documents”. Apps that weren’t about creating document files — like Disk First Aid and Font/DA Mover — got different icons. Font/DA Mover’s truck icon in System 2 signified that you use this tool to move things. Disk First Aid’s ambulance was an obvious metaphor for repairing something unwell.

[…]

But the main thing about the “hand holding pen over diamond” convention was that it was only ever a convention.

John Gruber (Mastodon):

(a) I don’t think this is a good mandate for iOS either;

(b) it was always so for iOS, though, so it’s not like Apple has ever taken away rich creative icon shapes on the platform;

(c) MacOS is a far richer and more precise environment than iOS.

[…]

App icons on the iOS home screen are effectively simple buttons. I think it’s rather obvious that’s why they have had that squircle/roundsquare shape ever since the iPhone was announced in January 2007 (source). They’re one-tap launchers. App icons in MacOS are not mere buttons. You can drag them, move them, and drop things on them. You click them to select, and double-click to launch. They are richer objects that deserve a richer visual vocabulary. iOS is a world meant for fat-tipped Magic Markers and blunt safety scissors. MacOS is a world meant to support fine-tipped drafting pens and precision razor-sharp X-ACTO knives.

Louie Mantia (Mastodon):

While developers have submitted full-bleed square images for iOS app icons since 2008, for these new squircle icons in macOS 11, Apple provided a template to compose app icons in an image editing tool like Photoshop, with full control over the canvas beyond the suggested—but not required—squircle. This template made it easy-ish for designers to compose macOS app icons that were identical to or synonymous with an iOS app icon, while leaving the door open to continue using arbitrarily-shaped app icons on macOS.

[…]

The second type of Squircle Jail is more controversial, because these app icons were specifically drawn with the intention of fitting in. Overriding that intention feels like punishment for having done the right thing. App icons in a style that was recently encouraged by the system are now scaled down and put inside the squircle as if it were a container. Every icon that was utilizing the previous squircle shape suddenly looks much worse than before.

[…]

Instead of taking care to design and develop solutions specifically for Mac and iPhone, newer and bigger companies that don’t only make apps often ship apps with logo icons, rather than app icons. We’ve all seen it.

[…]

I would love if Apple provided a way for designers to poke outside that squircle boundary. Some of my favorite app icons did that. But also some of my least-favorite app icons ignored this shape entirely, when it was used for every system icon in the last five years. Whenever those apps showed up in my Dock, it was like a stain on my shirt I couldn’t get out.

John Gruber:

Ultimately this is what I object to with the squircle mandate. It favors the bottom of the heap by restricting the top. It makes bad icons mediocre but pushes great icons toward mediocrity too. That’s not The Macintosh Way.

Nick Heer:

Mantia touches on all the pragmatic reasons to unify the shape of icons in an operating system, all of which I have considered, and then drops the above paragraphs — and things started to make more sense to me. This is a different way to think about it. This is not a situation where a cleaner looks like a zesty beverage with toxic consequences. The shared general function of these icons does help communicate something and makes them less ambiguous in that sense.

But a broad category of functionality is only part of the story of an icon and — with respect to Mantia’s long and illustrious history of work in this area, and that of co-Parakeeter Luka Grafera — taking away a difference of shape also limits what an icon can communicate. It may not be a cleaning product that looks and is packaged like juice, but imagine if every consumable liquid was in identical bottles with only a different label.

Steve Troughton-Smith:

Louie’s squircle jail post just underscores that the squircle jail benefits 99% of apps, and is better for the platform overall. There is only ever a handful of apps that make great Mac app icons, and a withering number of ‘great Mac app icon designers’ — you can probably only name one or two left in the scene.

Jeff Johnson:

Mantia talks as if it were more important for apps to “belong to the Dock” than to allow Dock users to quickly select the right app in the list. That’s choosing form over functionality.

“The shape of apps is a squircle.” But Mac users already knew those were apps in the Dock!

See also: Accidental Tech Podcast.

Tyler Hall:

If you’re lucky enough to distribute an app outside the Mac App Store, you can break free of squircle jail using NSDockTilePlugIn. It’s not strictly the intended use-case of that API. And it’s not allowed in the Mac App Store, either. But it can solve the problem.

BasicAppleGuy:

If you recognize these icons, it’s probably time to schedule your routine back exam.

Previously:

• Clear and Tinted Icons Are a Hard Pass
• Liquid Glass 27 Icons
• Apple Creator Studio Icons
• Tahoe’s Terrible Icons
• One Size Does Not Fit All
• macOS Tahoe 26 Developer Beta 4
• macOS Tahoe’s New Theming System
• macOS Tahoe 26 Announced
• The macOS App Icon Book

Update (2026-07-17): Louie Mantia:

But my perspective right now is to be very pragmatic. The decision to mask all icons with squircles is a long-time coming. It was perhaps the most predictable thing to happen in Apple’s history. For 20 years, it’s been leading up to this.

I want to make nice things for macOS, whatever macOS is. And this is what it is.

Roger Wong:

Some of my favorite icons over the years have had interesting shapes, like the truck for Transmit, the vise for Compressor, or the cute bird for Twitteriffic.

[…]

But I also recall clicking some icons and not being able to select them. Why? Because I was inaccurate in my click and instead my cursor landed in the empty space just outside the shape.

[…]

If I recall correctly, developers could use a different mask for the click target to help users out. But I don’t think many did all the time, including Apple, which you can obviously see in the video above.

Louie Mantia:

I don’t want to step on toes regarding your new [StopTheMadness] icon which has great color— but I don’t understand why you elected to abandon the octagon as the outer shape. That’s a choice. You are not forced to abandon it. Why not do something like this?

I like this.

Nick Heer:

Losing some of the artistry in an icon makes it more difficult to distinguish between legitimate and well-crafted Mac apps, and everything else. It is not a perfect proxy, to be sure, and there are some very nice squircle icons. But it is nevertheless a unfortunate change that makes apps of varying levels of quality look more similar.

Adam Engst:

Of the TidBITS readers who chose to respond to the poll, only 1% said they use clear icons on the Mac, and no one admitted to using tinted icons. On the iPhone, clear icons were twice as popular—a whopping 2%—and just 1% of respondents said they use tinted icons. Dark icons, which retain color, were slightly more popular, but still couldn’t exceed single digits, with 6% on the Mac and 9% on the iPhone.

Squircle Jail is one thing; redesigning icons to be assembled within Icon Composer is another. The latter makes a lot less sense but for supporting clear and tinted icons.

Previously:

• Golden Gate Squircle Jail
• Icon Composer Notes
• macOS Tahoe’s New Theming System

Jason Koebler (tweet, Reddit):

The AI music generation tool Suno scraped millions of songs and lyrics from YouTube Music, Deezer, and Genius, as well as from the stock music libraries Pond5, Jamendo, Freesound, the International Music Score Library Project, and podcasts via RSS feeds, according to a hacker who breached the company and shared data about Suno’s training libraries with 404 Media. The hacker was also able to access user information for hundreds of thousands of Suno’s customers, as well as Stripe payment information, they said.

[…]

As part of these legal proceedings, Suno previously admitted that it was trained on “essentially all music files of reasonable quality that are accessible on the open internet,” which included a total of “tens of millions of recordings.” Suno has been making the argument that it is allowed to train on copyrighted works as fair use in those cases, one of which has been settled.

Corbin Bolies:

Suno has long acknowledged that its AI music generator relied on the scraping of millions of songs available across the internet, but a new hack reveals just how the company pulled from streaming services and websites[…] all while user information remained vulnerable.

[…]

“Our goal has always been to help people create original new music, not replicate someone else’s. That’s why we build our models around what we call ‘Original Creation, By Design,’” the spokesperson said in a statement. “For example, we intentionally do not use artist names as a category of training metadata because we want our models to help people create brand new songs, not music that replicates other artists’ existing work. It’s also why we built Suno with detection filters that block or prevent a user from using specific artist, song, or album names as prompts, and prevent users from uploading lyrics or sound recordings that match existing works.”

Previously:

• Apple Scraping YouTube for AI Training Data
• Disney vs. Google and OpenAI
• The New York Times Sues Perplexity
• Apple Intelligence Training Lawsuit
• Sora App
• Reuters Wins AI Copyright Case
• AI Companies Ignoring Robots.txt
• The New York Times Sues OpenAI

SpamSieve 3.3.1 is an update of my Mac e-mail spam filter that improves the filtering accuracy and includes various optimizations, fixes, and updates for macOS 27. Some interesting engineering issues were:

• I’m still supporting macOS 10.13, but the app can now build with the macOS 12 deployment target in preparation for Xcode 27. The way Swift handles calling deprecated APIs remains annoying. You need workarounds like protocols to suppress a warning in a particular region of code. Often, I am updating to a newer API, but I want to continue using the old one on earlier versions of macOS. Right now I am heavily testing on macOS 26, so I would like to only deploy the new code there. Sometimes the initial versions of APIs are buggy, and I don’t want to have to retest every feature on every version. But Swift doesn’t like me to gate the calls to macOS 26 and later if the new API was actually introduced in, say, macOS 11.

• The most risky update was probably switching to the Swift API for Scanner. This is tricky because the current scan position changes from being based on UTF-16 indexes to String.Index. And in some cases my code was intentionally scanning into the middle of a combining character. I was really glad to have extensive tests here.

• Recent versions of Tahoe introduced a Core Data bug that broke save recovery (when invalid Unicode can’t be written to the database and we have to fix it up first). When the error comes in, SpamSieve looks under the NSDetailedErrorsKey key, but the value of this key is "NSDetailedErrorsKey" while the actual error info is under the key "NSDetailedErrors".

• Database corruption combined with a Core Data bug and two Swift behaviors were causing crashes. The root problem, I think, is that in this situation Core Data neglects to set the error pointer for -[NSManagedObjectContext countForFetchRequest:error:]. Normally, Swift would detect this and throw a generic nilError. However, this method signals errors by returning NSNotFound instead of nil. It’s annotated as swift_error(nonnull_error), which I think means that Swift doesn’t even look at the return value, only the (unset) error. So my code was receiving NSNotFound on the non-error path, treating it as a real count, and doing some math with it, which (by default in Swift) leads to a crash if there’s overflow. Now my code checks for NSNotFound and uses Int.addingReportingOverflow().

• I reimplemented Core Data batch fetching because of two problems with the fetchBatchSize option. First, it logs spurious errors when fetching from multiple stores at once. Second, it leads to high memory use. It will load objects in batches, but it never releases the earlier batches. You can manually refault objects that you no longer need, but it will still hold onto the full object shells, which can add up. My implementation only holds onto IDs, and it can fetch the IDs using a different context than the objects to push more work to background threads.

• I’m now using String.makeContiguousUTF8() in various places to avoid slow iteration of bridged strings.

• There was a regression where some menu code could crash on macOS 10.13. -[NSMenu setItemArray:] is only available on macOS 10.14 and later, whereas the getter is always available. With old Objective-C, the two methods could be annotated with separate availabilities. The Objective-C property syntax doesn’t allow this, so there’s no way for the compiler to flag calls where the setter is missing.

• The AppleScript support works much better with large data sets. The key, I think, is to never return an array to Cocoa for a scripting property/element. First, if you give it a lazy array it will sometimes try to access all the elements even if it only needs a few. And, second, AppleScript will run out of memory if the array is too large. By using indexed accessors, you can maintain laziness and only convert one object to a descriptor at a time. By caching a batch-fetching collection, you can limit the number of fetches and respond quickly when AppleScript requests individual objects.

Previously:

• Xcode 27 Announced
• SpamSieve 3.3
• Swift Proposal: Precise Control Flags Over Compiler Warnings
• Swift at 10

Phil Gyford:

Flickr recently updated their iOS/iPadOS app to version 5 (App Store link) and, while it’s not radically new, for a service whose changes have been incremental over recent years it contains a lot of differences. However I’ve yet to find any official changelog or update information.

[…]

When displaying multiple grouped photos from a person you’re following, it is no longer possible to view all the subsequent ones, other than the three or four initially displayed.

In the list of your Followers’ photos, their name now appears under their photos, so you must scroll down beyond the photos to see who took them.

[…]

When zooming into a photo the app no longer loads a higher resolution version, so now the zoomed-in version will be very pixellated.

He has a long list of missing features that may or may not be coming back. And there’s what seems like a major change: tags can no longer use capital letters.

The main changes I noticed were:

• In the Home/Discover view, when there’s a large group of new photos, you can only go into the group and view them individually, swiping to see each one. There’s no longer a way to see the whole group at once and scroll through it. (And tapping on the group icon or number of photos doesn’t do anything.)

• Double-tapping to favorite doesn’t work in some situations.

• The interface is more busy, showing more interaction chrome like other social media sites, rather than focusing on the photos.

• Swiping/navigation seems more clear than before, though without the old app side-by-side I can’t be exactly sure what’s changed.

Update (2026-07-16): Wesley Moore:

The Android version has been updated too:

“Flickr is back and better than ever — rebuilt from the ground up with a fresh new look and feel.”

I would guess it’s been built with cross-platform technology as it looks the same and came out the same time as iOS. The performance is terrible on Android. Scrolling my Photostream is juddery on my Pixel 9a (120 Hz display). It’s worse on my Android tablet.

Scrolling between photos swipes the whole UI (not just the photo), there’s also a flash of white loading the new photo. Needs some serious iteration.

See also: Reddit.

Update (2026-07-27): A. Lee Bennett Jr.:

Hooray! #Flickr restored a thumbnail view of all items from a specific post.

It turns out that Flickr 5.0.3 reverts back to the 4.x codebase.

Flickr (Reddit):

We know the new app hasn’t met the bar you expect from Flickr. Since launch, we’ve heard your feedback about bugs, missing features, and rough edges, and we want to acknowledge that directly. Here is where we currently stand:

iOS: We’re in the process of rolling back the iOS app to the previous version while we address these issues. You should see this reflected in the App Store shortly.

Android: The Android app will remain on the updated version. Due to technical limitations and the risks involved in reverting, a rollback isn’t possible on this platform. Instead, expect frequent updates as we fix bugs and restore preexisting features.

Across both platforms, this app refresh represents a significant, long-term investment in the Flickr app. The app was long overdue for an update and getting it right matters to us. Thank you for your patience, and for continuing to share what’s missing and not working. It’s shaping exactly what we address next.

Juli Clover:

Apple today released the first public beta of macOS Golden Gate, expanding the macOS 27 beta test to non-developers. You can sign up to test the update on Apple’s beta website, and then download it by going to System Settings > General > Software Update and toggling on the macOS 27 beta.

Jason Snell:

The fact that there are more design changes in macOS than any of Apple’s other 27 updates speaks volumes about how broken many of the Tahoe design decisions were. Apple describes the design as “even more refined,” because in Apple marketing-speak, broken features are never remedied or fixed—past features are just improved. The truth is, Apple has rolled back numerous missteps and made changes to others to mitigate the issues they caused.

Antonio G. Di Benedetto:

The Golden Gate developer beta has proven stable in my everyday use on an M5 MacBook Air and M5 Max MacBook Pro, which is notable since dev betas often have side effects like tanking battery life or causing hardware to run hotter than normal.

[…]

Would I still prefer to go back to the flatter design of macOS Sequoia? Yes, unequivocally. But at least Liquid Glass is more tolerable and less distracting now.

John Voorhees:

Nowhere is the Snow Leopard of it all more apparent than in the hundreds of little changes made to improve the day-to-day use of your Mac. I’m not going to catalog them all here, but I’ve used Golden Gate on two different Macs at this point, and based on my experiences so far, the changes are meaningful.

Jeff Johnson:

This is the crazy Finder column view file selection dragging behavior I’m seeing in the latest Golden Gate developer beta.

Matthias Gansrigler-Hrad:

With the release of the macOS 27 Golden Gate public beta, can we finally submit Mac apps built with Xcode 27?

Previously:

• Golden Gate Spotlight
• Apple Intelligence in appleOS 27
• macOS Touch
• AI-Generated Shortcuts
• Siri AI Announced
• Glow Leopard
• macOS 27 Golden Gate Announced
• Liquid Glass 27 Slider
• Liquid Glass 27 Icons
• Golden Gate Window Corners
• Golden Gate Sidebars and Toolbars
• Golden Gate Menu Icons
• appleOS 26 Public Betas