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.
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.
Reuters reports that China’s Cyberspace Administration registered Apple’s on-device generative AI service this week, putting it on a list of newly cleared providers that also includes homegrown systems from Chinese phone makers.
An unnamed source told the outlet that Apple’s AI features in the country will draw on models from both Baidu and Alibaba.
This isn’t about Siri AI, announced last month at WWDC for iOS 27 — this is the initial approval for Apple Intelligence, which was announced two years ago and rolled out in iOS 18.
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.
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.
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.
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.
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.
Apple released the iOS 27 public beta today, and if you’ve been curious about the new software, now’s the time to try it out. iOS 27 brings Siri AI, performance improvements, and lots of new Apple Intelligence features.
[…]
Everything feels snappier than it did in iOS 26. Animations are quicker, apps launch faster, and AirDrop transfers complete faster. You’ll see improvements when taking photos, opening the keyboard, using the App Library, and swapping Home Screen pages. Your iMessages between devices sync more accurately, messages won’t fail to send and will be automatically retried, and your iPhone can transition more smoothly between Wi-Fi and cellular.
In general, the iOS 27 incarnation of Liquid Glass is far easier on the eyes, dialing down the transparency in favor of legibility. Apple’s also imposed some distinction between user interface elements and content. For example, in list views like in Messages and Mail there are now much clearer “toolbar” areas at the top when you start scrolling, even if they still have some degree of translucency. App icons have also gotten a face lift; they’re sharper, and feel more vibrant.
[…]
That’s because one of the odd things about looking at iOS 27 is that there’s just a ton of small stuff—those “quality of life” improvements that chip away at little frustrations and annoyances.
Spotlight doesn’t currently appear able to search Time Machine backups reliably, at least not in Sequoia or Tahoe, although this may not be universal.
[…]
If I now step back through my backups to reach one that I know contains that file, I can restore it. But if I type anything into the search field, nothing is found. If I change the scope of the search to that backup, the window title changes but its contents remain blank, and there isn’t even a busy spinner to indicate a search is in progress.
[…]
As I can’t disable Spotlight indexing on that volume without macOS telling me that it’s required to be indexed by Spotlight, neither can I force that volume to be reindexed.
[…]
My conclusion is that using Spotlight to search Time Machine backups no longer works, and the instructions given by Apple are also broken.
That has been my experience, too. As I see it, there are four separate problems:
I want to be able to search all my backup snapshots, because I don’t know which one might contain the file I want to restore. Time Machine only lets you search one at a time.
Searching an individual snapshot doesn’t actually work.
Spotlight indexing is invasive, using lots of CPU time, and with spinning hard drives causes wear and tear and creates lots of noise. If search doesn’t work anyway, I’d like to turn it off, but macOS won’t let me.
If the problem is with the index, there’s no way to reset it without deleting your backup.
Unfortunately, all those saved versions in the version database fall outside the scope of Spotlight indexing, and Spotlight search can’t look inside any of the old versions saved in a volume’s version database. Surprisingly, the version browser doesn’t offer any search facilities either, as that’s presumably another feature intended for a future that never came.
[…]
One way around this is to save each document version as a separate file, allow Spotlight to extract their contents and add those to its indexes for that volume, then to search those files. This is quick and simple using my free utility Versatility.
In an exclusive conversation with The Deep View ahead of WWDC 2026 in June, Doug Brooks, senior product manager of Apple silicon, discussed how Apple’s long-term investments in neural processing, unified memory, power-efficient computing, and hardware-software integration have positioned its devices for the AI era.
He also explained why Macs have become a favorite platform among AI developers, why Mac minis and Mac Studios are emerging as the preferred AI agent machines, and how Apple sees the future of on-device AI across iPhone, iPad, and Mac.
[…]
“We build a chip knowing exactly what systems it’s going to go into. The chip can influence the system design, and the system design can influence the chip requirements. They’re married together very tightly. I’d actually go a step further and include software in that equation. As we enable new capabilities in the chip, we want to make sure those capabilities are exposed all the way through the software stack so developers can benefit and customers can benefit. Because if those transistors go unused, what’s the point? It’s not about adding something and hoping somebody finds a use for it. We want those capabilities available to solve real problems. I think that’s what allows us to build better systems and ultimately better products.”
It seems like a lot of it is just that developers like macOS.
A vulnerability in Apple’s “Hide My Email” tool lets almost anyone discover a person’s real email address that is supposed to be hidden by the feature, and Apple has failed to fix it for more than a year, according to a security researcher and 404 Media’s own tests.
[…]
“Apple Hide My Email is leaking email addresses that are supposed to be hidden. We reported the issue and replication instructions to Apple over a year ago. We don’t know why it hasn’t been fixed, but we don’t feel comfortable waiting any longer. Hide My Email users deserve to know that it may be possible for attackers to discover their hidden email addresses,” Tyler Murphy, the co-founder of EasyOptOuts, which discovered and reported the issue to Apple, told 404 Media.
“Free, publicly accessible people-search sites make it easy to link an email address to other personal details, so people relying on Hide My Email for safety may be at risk,” Murphy added.
[…]
To test the issue I generated a new Hide My Email address and provided it to Murphy. Around five minutes later, he replied with my real email address linked to my Apple account which was supposed to be hidden.
Murphy said that he reported the issue to Apple in June of last year, and the company told him it was looking into it. Apple said it had been fixed in March of this year, but Murphy found that wasn’t the case. He again contacted Apple, with the company saying that it would appreciate him not revealing the existence of the flaw until it had been resolved.
Apple then said it planned to address the issue in June, but since it still hasn’t been fixed[…]
March 19, 2026: Using the reproduction instructions from our initial report, we determined that the vulnerabilities hadn’t been fixed.
May 22, 2026: We realized that the vulnerabilities may have greater severity and scope than we thought initially and reported this to Apple. Apple never acknowledged the report of increased severity.
June 30, 2026: Apple again reported that the vulnerabilities were fixed and asked us to verify. We determined that the vulnerabilities hadn’t been fixed.
Very few details are available right now. I have seen speculation that the original email address is revealed when someone replies using their hidden email address, but the impression I get from Cox’s reporting is that no user interaction is necessary[…]
[…]
I am also unclear about how, as of May, the EasyOptOuts guys found the “vulnerability may have greater severity and scope” than initially reported. Ominous, though.
I don’t know whether I’ve accidentally stumbled upon that vulnerability, or perhaps in this case the Hide My Email user just messed up in some way, but I’ve definitely discovered a bizarre and troubling Hide My Email bug in Mail app (on macOS Sequoia 15.7.7).
[…]
Bizarrely, however, Mail app displayed an alert that I’ve never seen before, “This message was forwarded to you by Hide My Email,” despite the fact that I have previously received many emails from people using Hide My Email.
[…]
Why I am seeing two different @icloud.com email addresses, one of which appears to be the sender’s unhidden address?
Why are the To: and From: fields in my reply disabled?
Why is my reply not from my @underpassapp.com email address but rather displayed falsely as from the sender’s @icloud.com address and really from my unrelated Apple Account address?
Apple this week was sued over a reported “Hide My Email” flaw that could expose a user’s real email address. The proposed class action lawsuit alleges that Apple violated California’s false advertising law and other consumer protection statutes by knowingly offering a feature that does not work as advertised.
This is interesting in that the June 2025 bug report is the evidence that Apple “knew” the feature didn’t work, while “Apple continued to represent to consumers that Hide My Email
would actually hide users’ email.” How long are they supposed to get to fix a bug?
The misleading user interface elements in Mail app are a bug, but by themselves they’re not a vulnerability. The vulnerability is that when I send a reply to my maliciously crafted email, my Apple account email address is disclosed in the “From” field of the sent reply! In other words, the Mail app interface lies, fails to show the true sent value of the “From” field.
There are a couple of crazy aspects to this information disclosure vulnerability:
It does not require that the victim actually use Hide My Email! I never use it. As I mentioned in my previous blog post, I don’t even have an icloud.com email account.
It does not matter which of the victim’s email accounts receives the email from the attacker. If your Apple account email address is a@foo.com, but you receive a maliciously crafted email addressed to b@bar.com, Mail app will still send your reply from a@foo.com, thereby disclosing your Apple account address.
Apple addressed a vulnerability in Hide My Email that exposed a user's real email address, reports 404 Media. Apple told the site the issue was fully fixed in a patch released on July 3.
[…]
While the bug has now been addressed, email logs that pre-date the fix could still expose user email addresses.
The social media company Meta and the video streaming service YouTube harmed a young user with design features that were addictive and led to her mental health distress, a jury found on Wednesday, a landmark decision that could open social media companies to more lawsuits over users’ well-being.
[…]
Citing features like infinite scroll and algorithmic recommendations, K.G.M. sued Meta, which owns Instagram and Facebook, and Google’s YouTube, claiming they led to anxiety and depression.
For its part, the Wall Street Journal editorial board is standing up for beleaguered social media companies in an editorial today criticizing everything about these verdicts, including this specific means of liability, which it calls a “dodge” around Section 230.
[…]
Product design, though, is a different question. It would be a mistake, I think, to read Section 230 as a blanket allowance for any way platforms wish to use or display users’ posts. (Update: In part, that is because it is a free speech question.) From my entirely layman perspective, it has never struck me as entirely reasonable that the recommendations systems of these platforms should have no duty or expectation of care.
To me, a non-lawyer, much of the actual text of the ruling (PDF) explaining why this lawsuit was not immediately turfed on Section 230 grounds seems pretty reasonable. For example, the judge says “[u]nder the default settings, Meta enables approximately forty types of notifications” for the Instagram app, which the government alleges “is designed to overwhelm young users and compel them repeatedly to reopen Instagram”. We can argue whether this is a meaningful thing for a government to police or if it is just another example of Meta resorting to tacky growth-hacking techniques instead of trusting their product is sufficiently compelling on its own. (Most days when I open Instagram in my browser, it puts a red badge over the notifications tab and suggests I have one new follower. I do not; I never have. It lies to me every time, presumably because it knows most people, including me, will usually click on that, thereby increasing a number on a dashboard somewhere.)
couple weeks back, Jonathan Haidt published another entry in his ongoing campaign to convince the world that social media is inherently ruining kids’ lives. This one was a victory lap titled “Seven Lines of Evidence Against Social Media,” treating recent developments — including the social media addiction verdicts against Meta that most people are misunderstanding — as vindication of his thesis.
Indeed, the research repeatedly suggests that for the very small number of kids who are facing mental health problems and overrelying on social media in response, the answer is a targeted intervention to help those individuals — not a broad “ban kids from social media” program.
A group of 48 China-based iOS developers have filed an antitrust complaint against Apple with the country’s market regulator over the App Store’s commission rates, the South China Morning Post reports.
The developers sent an open letter to China’s State Administration for Market Regulation (SAMR), alleging that Apple failed to deliver on a promise to offer the lowest commission rate to the Chinese market. The group asked the SAMR to investigate and penalize Apple for allegedly abusing its market dominance to impose “unfair and excessively high” costs on local developers.
Apple lowered the fees in March but not as much as it did in Brazil and Japan.
Discover the latest enhancements to SwiftData. We’ll show you how to persist custom and third-party types using Codable, and group fetched data into sections in your SwiftUI app. We’ll also explore how to observe data store changes anywhere else using ResultsObserver and HistoryObserver, giving you the flexibility to drive powerful state objects and react precisely to model updates.
Again, there seems to be nothing new in Core Data this year, nor any communication about it. There’s still no interoperability for object IDs. The SwiftData changes seem fine but don’t really address the new framework’s deficiencies relative to Core Data. It seems like there are still basic problems with threading. I just don’t understand how Apple is deciding what to prioritize with this framework.
With SwiftUI, the bones seem questionable, but at least we can see that Apple is full steam ahead, with substantial progress to address limitations and pain points. SwiftData seemed to have better bones and is much less ambitious. Getting it right seemed like just a matter of follow through. But, for some inexplicable reason, it seems to lack the resources and/or urgency to reach its potential. And even though SwiftUI is clearly the chosen one, AppKit remains in development. Meanwhile, Core Data seems to be abandoned, even though SwiftData feels more like a side quest than a genuine attempt to supplant it.
The implicit message, for those who have build the core of their app on top of Apple’s old persistence framework, seems to be that Apple is not looking out for their needs. Core Data will surely get maintenance to the extent that Apple’s own apps need it, but there’s no evidence of a future or even a migration plan. The answer, I guess, is third-party frameworks, but that’s not an easy migration, either, since none is even as close a match as SwiftData.
Experience SwiftData in action as we add persistence to an existing app. We’ll show you how to define your data models and seamlessly integrate persistent data with SwiftUI. You’ll also learn foundational skills for managing your app’s state using this expressive, declarative API.
Join us online for a deep dive into WWDC26 with Apple engineers and designers to ask questions, get advice, and follow the discussion about the week’s biggest SwiftData announcements.
SwiftData predicates can now work directly with enum values, resulting in cleaner models and simpler query code.
[…]
In iOS 27, Apple introduced support for compound predicates through the Predicate(all:) and Predicate(any:) initializers, making it easier to build queries dynamically based on user input.
I’m not sure why that took so long.
The framework is gradually moving beyond simple demos and becoming easier to use in larger, more sophisticated projects.
[…]
iOS 27 is the first release where many of the framework’s early rough edges have started to disappear.
Compared with @Query gaining support for section fetches, and ResultsObserver enabling observation of query result changes outside views, I am more interested in @Attribute(.codable). It provides a clearer storage intent and gives developers a way to avoid falling into the black box of composition.
Of course, @Attribute(.codable) is not a silver bullet. It is more like a clearly defined escape hatch SwiftData provides for opaque Codable types: suitable for storing external types that you cannot model yourself, but still genuinely need to persist. The cost is that this content cannot participate in SwiftData’s predicate, sort, or migration awareness. Precisely for this reason, its value lies not in being “more powerful,” but in being “more explicit.”
However, SwiftData still does not provide cloud syncing for public / shared data, nor have I seen a clearer signal of performance improvements. These issues will continue to limit its adoption. For many developers, SwiftData this year feels more like it is filling key gaps rather than making a leap significant enough to fundamentally change confidence in it.
Codable types in SwiftData seem pretty lame given that SQLite absolutely does have JSON support and does support queries on it?
But the funnier thing in the MKMapItem.Identifier example is that MKMapItem.Identifier is a RawRepresentable==String, so it could actually be stored as a String in the store.
AppKit adds NSRefreshController, providing pull-to-refresh functionality for NSScrollView.
[…]
NSToolbarItemGroup adds the role property and the NSToolbarItemGroupRole enum, allowing toolbar item groups to be tagged with a semantic role. NSSegmentedControl similarly adds a role property and the NSSegmentedControlRole enum, including a tabs role for controls that represent tab-based navigation and content selection.
[…]
NSTextSelectionManager provides common text selection interactions (click, drag, shift-click, double/triple-click word/line/paragraph selection) to a NSView with a set of NSGestureRecognizers rather than overriding NSEvent mouse methods. NSTextView now uses NSTextSelectionManager and provides its own set of NSGestureRecognizers to provide additional features in addition to text selection.
[…]
By default, NSMenu hides all menu item symbol images — non-symbol images remain visible. […] Use the new preferredImageVisibility property on NSMenuItem to customize the image visibility for your menu items. As in macOS 26.0, NSMenu automatically provides default visible menu item images for certain common system-wide menu items, such as Settings, Share, and Print.
Bring your AppKit app up to date with modern macOS conventions. Dive into handling input with control events and gesture recognizers, moving beyond traditional tracking loops. Enhance keyboard navigation in your app, implement graceful state restoration after restarts, and take advantage of new corner concentricity APIs that let your interface blend seamlessly with the macOS aesthetic.
To summarize the singular AppKit session this year: hey remember all these APIs and design patterns from UIKit? Well they’re now in AppKit and you should use them! Also make your glass use interactive bounce effects.
In macOS 27, AppKit continues to standardize on gesture recognizers as the primary mechanism for input handling. This change directly affects Sidecar because gesture recognizers are the only way to respond to touch input from a Sidecar-connected iPad running iPadOS 27. If your app relies on tracking loops for mouse event handling, migrate to gesture recognizers to support Sidecar touch input.
This article explains how the gesture recognizer model works, how to implement gesture recognizers correctly for Sidecar touch input, how to update your existing event-handling code, and which APIs macOS 27 adds. Codebases that implement nextEvent(matching:) or mouseDown(with:), mouseDragged(with:), and mouseUp(with:) events are most affected by the updates discussed.
Discover how to combine the convenience of built-in text views with the control of TextKit. We’ll show you how new APIs make it easy to extend UITextView and NSTextView with custom behaviors like line numbers and collapsible sections. We’ll also explore the TextKit architecture and walk through new caching and reuse policies for text attachments.
[You] can use UIScene.extendStateRestoration and UIScene.completeStateRestoration to extend state restoration for UIScene.ActivationState.background to UIScene.ActivationState.foreground lifecycle transitions.
[…]
iOS and iPadOS apps built with the 27.0 SDK or later are required to include a launch screen.
[…]
Siri can load resources from drag interactions installed in your app’s interface.
[…]
In apps built with the iOS 27.0 SDK, a presented view controller inherits its trait collection by walking up its view’s superview chain through the intermediate views of the presentation, rather than jumping directly to the presentation controller.
Discover the latest updates to UIKit. Learn how to update your iPhone app layouts to work great when resized with iPhone Mirroring and on iPad. Explore new APIs for tab and navigation bars, find out how to prepare your app for new Apple Intelligence capabilities, and get introduced to a skill for your coding agent of choice that helps modernize your codebase.
iOS 27’s UIKit is a tiny release in terms of API changes, but does have some changes. There are no new top-level paradigms, but there’s an new addition to TextKit 2, a new scene accessory API, Liquid-Glass-era bar minimization controls, and a small amount of quality-of-life additions to menus, tab bars, and drag interactions.
Apple appears to be laying the groundwork for a foldable iPhone in iOS 27, with new references discovered in the operating system’s frameworks and a notable emphasis on flexible app layouts at this year’s Platforms State of the Union.
The nav bar and its friends got quite a bit of attention, and to be honest that’s where we will find most of the changes. They adapt to all sorts of sizes and situations…hmmm, I WONDER WHY!?
[…]
A few years ago, I wondered if UIKit would be deprecated altogether. That would’ve been drastic, sure, but I did wonder. These days, I don’t share the same concern anymore. SwiftUI gets better each year, and yeah — it’ll have top billing. But UIKit is solid, and it appears to be a core part of Apple’s strategy into the future.
Not much changed this year, and not much was added that’s flashy. But, that’s true of iOS 27 in several ways.
macOS Tahoe threw an icon on every menu item, making them impossible to distinguish at a glance. macOS Golden Gate has rectified that design taboo with blessedly iconless menus.
In macOS 27.0, menu bar and context menus present a reduced set of menu item images, similar to the behavior prior to macOS 26.0. By default, NSMenu hides all menu item symbol images — non-symbol images remain visible. For menu items created from a xib file, NSMenu also observes the value of the “macOS 26.0 only” checkbox in the menu item inspector. If this checkbox is unchecked, the menu item image remains visible; if checked, it is hidden. These changes in menu item image visibility apply to applications linked on macOS 26.0 and later. Review the updated Human Interface Guidelines to determine which menu items in your app should still display images. Use the new preferredImageVisibility property on NSMenuItem to customize the image visibility for your menu items. As in macOS 26.0, NSMenu automatically provides default visible menu item images for certain common system-wide menu items, such as Settings, Share, and Print.
I like that Menu Icons now are hidden by default again on macOS - Quite a lot of concessions towards liquid glass being the wrong move last year. Takes courage to take so many steps back, literally. I’m appreciating that. Even if they present it as improvements rather than “undo” - that’s just what one has to do for marketing.
Kudos to Nielsen and Prokopov for pushing on this and explaining the problem so well. This wasn’t about ugly icons. This was about improper use and misunderstanding of iconography.
O Google aproveitou o evento Galaxy Unpacked de hoje para anunciar novos recursos que chegarão ao Switch to Android, sua ferramenta que ajuda usuários a migrar do iOS para o sistema operacional do robozinho verde.
De acordo com a gigante de Mountain View, a solução agora também permite transferir contas do Google, senhas, credenciais de redes Wi-Fi e até mesmo eSIMs salvos em iPhones para dispositivos Android.
Antes disso, o Switch to Android já suportava a transferência de fotos, vídeos, contatos, mensagens e dados de calendário. Em qualquer caso, vale notar, é necessário que o iPhone envolvido na transferência esteja rodando pelo menos o iOS 26.3.
Essas melhorias serão integradas ao Android 17 e já começaram a ser liberadas para dispositivos Pixel. Os smartphones das linhas Galaxy Z Flip8 e Z Fold8, anunciados pela Samsung no evento supracitado, também serão contemplados por essa nova versão da ferramenta em breve, o que também vale para aparelhos de outras marcas.
Com o Switch to Android, pessoas que estão migrando do iOS para o Android podem transferir seus dados sem fio e sem baixar nenhum aplicativo separado — solução que surgiu após pressão regulatória, principalmente por parte da União Europeia e sua Lei dos Mercados Digitais (Digital Markets Act, ou DMA).
A produção girará em torno de um financista desacreditado acusado de fraude em larga escala e colocado sob custódia. Na cadeia, ele se verá obrigado a lidar com a política da prisão, recuperar sua reputação e enfrentar as consequências de seus atos enquanto aguarda o julgamento.
Benicio Del Toro is set to make his leading comedy series debut on Apple TV.
Also starring and executive produced by Ben Stiller, and hailing from Emmy Award-winner Mike Judge, Emmy Award-winner Steve Hely and Dave King, comes a new series about a disgraced financier navigating… pic.twitter.com/3rglVYsR7C
“Protective Custody” também marcará o reencontro entre del Toro e Stiller, que já colaboraram na minissérie “Escape at Dannemora”. A produção marca, ainda, a estreia de Stiller como protagonista em uma série de comédia roteirizada, fora do formato de esquetes.
O Apple TV está disponível no aplicativo Apple TV em mais de 100 países e regiões, seja em iPhones, iPads, Apple TVs, Macs, dispositivos Android, smart TVs ou online — além de também estar em aparelhos como Roku, Amazon Fire TV, Chromecast com Google TV, consoles PlayStation e Xbox. O serviço custa R$29,90 por mês, com um período de teste gratuito de 7 dias. Por tempo limitado, quem comprar e ativar um novo iPhone, iPad, Apple TV ou Mac ganha 3 meses do Apple TV. Ele também faz parte do pacote de assinaturas da empresa, o Apple One.
NOTA DE TRANSPARÊNCIA: O MacMagazine recebe uma pequena comissão sobre vendas concluídas por meio de links deste post, mas você, como consumidor, não paga nada mais pelos produtos/serviços usando os nossos links de afiliado.
A quarta temporada de “Ted Lasso” estreará no Apple TV no dia 5 de agosto e, embora a Maçã ainda não tenha encomendado uma quinta temporada, o astro Jason Sudeikis afirma que o objetivo é reunir novamente a equipe de roteiristas, no final de agosto, para trabalhar em ideias para uma possível continuação.
Em entrevista ao The Hollywood Reporter, ele disse ter em mente um arco de mais três temporadas (já contando com a quarta) e que existem, especificamente, ideias para a quarta temporada que não foram utilizadas.
Se tudo correr conforme o planejado, a equipe de [Ted] Lasso retornará à sala de roteiristas no final de agosto para estruturar uma quinta temporada — que ainda não foi oficialmente encomendada. Eles ainda têm ideias não utilizadas do retiro em Ojai, e o aplicativo de notas de Sudeikis continua sendo uma fonte inesgotável de material. Mais uma vez, Sudeikis tem em mente um arco de três temporadas e espera que o público continue acompanhando. “Eu sei que precisava disso. Eu precisava tanto quanto as outras pessoas”, diz ele.
Falando sobre a quarta temporada, Sudeikis insiste que falava sério quando disse que a série terminaria após três temporadas. Ele afirma que sua intenção era genuína, mesmo tendo recebido uma oferta de mais de US$1 milhão por episódio para continuar.
A história foi contada. Ted voltou para casa [em Kansas City] para ficar com o filho. Eu não ia fazer o Ted virar a vida deles de cabeça para baixo só para justificar uma fortuna. Isso não fazia sentido para mim.
Ainda assim, os espectadores continuavam dizendo a ele que a série os havia salvado, e ele respondia prontamente: “Ela me salvou também.”
É contagiante interpretar um personagem que vê o melhor nas pessoas e não guarda rancor do mundo por todas as suas fraquezas, valentões e sombras. Não é como se eu fosse o Daniel Day-Lewis, mas foi bom viver isso — sentir essa energia percorrendo minha mente e meu corpo o dia todo.
Sudeikis e sua equipe acreditam que a quarta temporada está muito boa. Inclusive, o roteirista Brett Goldstein, que também interpretou o jogador de futebol Roy Kent, disse que “ela resgata um pouco daquela magia da primeira temporada”.
A entrevista completa traz outras informações, incluindo detalhes dos bastidores de todas as temporadas lançadas até agora e os desafios enfrentados na pré-produção.
Ademais, caso não tenha acompanhado, Sudeikis e Brendan Hunt (intérprete do Coach Beard) fizeram uma aparição surpresa durante a performance de Justin Bieber na partida final da Copa do Mundo 2026.
O Apple TV está disponível no aplicativo Apple TV em mais de 100 países e regiões, seja em iPhones, iPads, Apple TVs, Macs, dispositivos Android, smart TVs ou online — além de também estar em aparelhos como Roku, Amazon Fire TV, Chromecast com Google TV, consoles PlayStation e Xbox. O serviço custa R$29,90 por mês, com um período de teste gratuito de 7 dias. Por tempo limitado, quem comprar e ativar um novo iPhone, iPad, Apple TV ou Mac ganha 3 meses do Apple TV. Ele também faz parte do pacote de assinaturas da empresa, o Apple One.
NOTA DE TRANSPARÊNCIA: O MacMagazine recebe uma pequena comissão sobre vendas concluídas por meio de links deste post, mas você, como consumidor, não paga nada mais pelos produtos/serviços usando os nossos links de afiliado.
O Apple TV adquiriu antecipadamente os direitos de produção de “Peculiar Stars”, o vindouro (e bastante disputado) romance de Rebecca Yarros, autora conhecida pela série de livros “Empyrean”.
A aquisição foi confirmada pelo serviço no X. A série será produzida pelo Apple Studios e contará com Yarros como produtora executiva, por meio da sua empresa Full Measures Productions.
A new tale of survival and romance from bestselling author Rebecca Yarros.
Apple Studios will develop Peculiar Stars, and Yarros will serve as executive producer through her banner Full Measures Productions. pic.twitter.com/g2KTQ6ZnSL
Uma nova história de sobrevivência e romance da autora best-seller Rebecca Yarros.
O Apple Studios desenvolverá “Peculiar Stars”, e Yarros será produtora executiva por meio da sua produtora, a Full Measures Productions.
“Peculiar Stars” será publicado em novembro e acompanhará uma jovem que fica presa em uma ilha deserta com um membro da família do seu noivo — o que transformará sua visão sobre o amor.
Quando eles são finalmente resgatados e retornam aos seus mundos repletos de privilégios, expectativas e segredos, esse retorno se mostra muito mais perigoso do que a ilha onde estavam.
De acordo com o Deadline, a Apple ainda está à procura de um roteirista para escrever a adaptação. No livro, a história terá um ritmo lento, se desenrolando por 543 dias na ilha supracitada.
O Apple TV está disponível no aplicativo Apple TV em mais de 100 países e regiões, seja em iPhones, iPads, Apple TVs, Macs, dispositivos Android, smart TVs ou online — além de também estar em aparelhos como Roku, Amazon Fire TV, Chromecast com Google TV, consoles PlayStation e Xbox. O serviço custa R$29,90 por mês, com um período de teste gratuito de 7 dias. Por tempo limitado, quem comprar e ativar um novo iPhone, iPad, Apple TV ou Mac ganha 3 meses do Apple TV. Ele também faz parte do pacote de assinaturas da empresa, o Apple One.
NOTA DE TRANSPARÊNCIA: O MacMagazine recebe uma pequena comissão sobre vendas concluídas por meio de links deste post, mas você, como consumidor, não paga nada mais pelos produtos/serviços usando os nossos links de afiliado.
Segundo o que foi reportado por fontes de cadeia de suprimentos, a Foxconn já teria dado o pontapé inicial na produção em massa do “iPhone 18 Pro” e do “iPhone 18 Pro Max”, os próximos smartphones topos-de-linha da Apple.
A informação partiu do portal de notícias chinês MyDrivers, o qual afirmou que a principal fabricante contratada da Apple iniciaria em breve seu período de pico de contratações para dar conta desse estágio de aumento da produção em massa, já iniciado no mês de julho.
Pela primeira vez, a Apple deverá segregar o lançamento dos novos iPhones, separando os modelos tradicionais dos da linha Pro: tanto o “18 Pro” quanto o “18 Pro Max” deverão ser anunciados em setembro ao lado do “iPhone Ultra” — a estreia da Apple no segmento de celulares com telas dobráveis —, enquanto lançamentos como a segunda geração do iPhone Air, o “iPhone 18” e o “iPhone 18e” deverão ficar para o começo do ano que vem.
iPhone 17 Pro Max
Cores: prateado, laranja-cósmico ou azul-intenso Armazenamento: 256GB, 512GB, 1TB ou 2TB
NOTA DE TRANSPARÊNCIA: O MacMagazine recebe uma pequena comissão sobre vendas concluídas por meio de links deste post, mas você, como consumidor, não paga nada mais pelos produtos/serviços usando os nossos links de afiliado.
Os novos dobráveis chegam meses antes de a Apple alegadamente adentrar nesse segmento do mercado com o famigerado “iPhone Ultra” — logo, as apostas da gigante sul-coreana baterão de frente com o futuro dispositivo da Maçã.
Sem mais delongas, vamos conferir os detalhes de cada anúncio abaixo!
Galaxy Z Fold8
Divulgação/Samsung
Agora que os dobráveis da Samsung possuem três variantes, o Z Fold tradicional passou por um reposicionamento, tornando-se talvez a adição mais diferente dentre toda a linha de novos produtos anunciados.
Seu grande destaque é a reformulação no design, adotando um formato que se convencionou chamar de “passaporte”, com uma proporção maior do que aquilo que foi estabelecido nas últimas gerações do dobrável principal da Samsung. Isso resultou em uma tela externa de 5,5 polegadas e aspect ratio de 10:16, além de uma principal de 7,6″ e proporção de 4:3 — especificações bem semelhantes ao que se especula sobre o “iPhone Ultra” —, ambas com taxas de atualização de até 120Hz.
A sul-coreana destacou ainda o peso do modelo, sendo o celular dobrável mais leve já lançado por ela até agora (201 gramas, para ser exato).
Uma das principais diferenças do modelo em relação ao Z Fold8 Ultra está nas câmeras: o modelo padrão conta apenas com duas lentes traseiras (um sensor principal e uma lente ultra-angular, ambos com 50 megapixels), além dos 200mAh de diferença na bateria (4.800mAh no caso do Z Fold8 e 5.000mAh no caso do Z Fold8 Ultra). A linha também marca a estreia das baterias de silício-carbono nos celulares da fabricante.
Quanto ao restante das suas especificações técnicas, destaca-se pela implementação da tecnologia Flex Titanium — baseada em alumínio — para a resistência da tela, a presença do chip Snapdragon 8 Elite Gen 5, opções a partir de 12GB de memória e 256GB de armazenamento (até 1TB), resistência IP48 contra água e poeira, além de suporte ao carregamento de 45W com fio e 15W sem fio. Assim como os demais aparelhos, ele chega com o Android 17 e a One UI 9.
Nos Estados Unidos, ele chega a partir de US$1.900 (US$200 a menos que o Z Fold8 Ultra e US$100 a menos que o Z Fold7) nas cores preta, branca, lavanda e verde pistache (esta última exclusiva para compra no site oficial da Samsung).
Galaxy Z Fold8 Ultra
Divulgação/Samsung
Para os entusiastas do tradicional formato dos dobráveis da Samsung, a melhor opção é o modelo Ultra. Ele conta com as mesmas 8″ na tela principal e 6,5″ na tela externa do Z Fold7, com aspect ratios de 3:2 e 21:9, respectivamente.
Outra diferença notável em relação ao modelo menor é a presença da lente teleobjetiva de 10MP, aos moldes da presente no Z Fold7.
Como citado anteriormente, o aparelho conta com uma bateria de 5.000mAh de silício-carbono, além de compartilhar o Snapdragon 8 Elite Gen 5, as mesmas opções de memória/armazenamento, a resistência IP48 e o suporte aos 45W de carregamento com fio e 15W sem fio do Z Fold8.
Um de seus maiores destaques (nesse caso, negativo) é o preço: US$2.100 — um aumento em comparação ao modelo equivalente da geração passada (vale lembrar, o Z Fold7 chegou por US$2.000 lá fora). Ele está disponível nas cores preta, branca, roxo escuro e verde escuro (esta última exclusiva para compra no site oficial da Samsung).
Galaxy Z Flip8
Divulgação/Samsung
Modelo mais básico da nova linha, o Z Flip8 se destaca pela redução na espessura (13,1mm dobrado contra os 13,7mm do antecessor) e no peso (188g contra 180g do Z Flip7), possibilitando o que a Samsung chama de “uma experiência cotidiana sem vinco”.
Ele conta com uma tela interna de 6,9″, enquanto a externa tem 4,1″, com proporções de 22:9 e 1:1, respectivamente, e suporte a taxas de atualização de 120Hz em ambas. O aparelho chega com um conjunto duplo de câmeras, sendo a lente principal de 50MP, um sensor ultra-angular de 12MP e câmera frontal de 10MP.
Ele chega com o processador Exynos 2600, resistência IP48, 12GB de memória e opções de armazenamento de 256GB e 512GB. Em termos de bateria e recarga, o componente de silício-carbono possui uma capacidade de 4.300mAh, carregamento de até 25W por fio e 15W sem fio.
O Z Flip8 custa US$1.200 (um aumento de US$100 em relação ao Z Flip7) e está disponível nas cores azul, preta, vermelha coral e menta (esta última exclusiva para compra no site oficial da Samsung).
Galaxy Watch9 e Ultra2
Ambos os modelos ganharam suporte ao recurso “levante para falar”, que aciona de imediato o Gemini do Google sem a necessidade de toque ou botão. Os dois relógios contam com o Wear OS 7 e a One UI 9 Watch, compatíveis com smartphones que possuam Android 13 ou superior.
Divulgação/Samsung
Com especificações e design um tanto semelhantes ao seu antecessor, as grandes novidades do Galaxy Watch9 incluem a ampliação de bateria (o modelo de 40mm ganhou um aumento de quase 20%, com 390mAh, enquanto a versão de 44mm possui 445hmAh), a pulseira com design Air Pocket (até 25% mais leve que a presente no Watch8) e a estreia do processador Snapdragon Wear Elite.
Ele continua com as opções de 2GB de memória e 32GB de armazenamento e está disponível em caixas de 40mm e 44mm, nas cores preto e creme, custando a partir de US$380 (um aumento de US$30 em relação ao Watch8).
Já o Galaxy Watch Ultra2 adota uma reformulação na identidade visual que o aproxima do restante da linha, sendo até 12% mais fino que o seu antecessor, mantendo a bateria de 800mAh. A tela também ganhou melhorias, contando com 5.000 nits de brilho máximo.
Para experiências aquáticas, o Ultra2 atende o padrão EN13319 para mergulho e possui certificação IP69K. Além disso, o app Marz deverá receber suporte à metrificação de velocidades e orientações de descompressão.
Disponível nas cores titânio preto e titânio prata, o modelo está disponível a partir de US$700, um aumento de US$50 em relação à primeira geração.
Inteligência artificial
Durante o evento, a Samsung reforçou sua ciência e presença quanto às IAs agênticas, expandindo a experiência para além das telas dos smartphones e passando a oferecer assistência contínua de IA em tempo real nos dispositivos do seu ecossistema; o foco da Samsung é a entrega da experiência hands-free (ou seja, mãos livres). Ela afirmou ainda que essa integração contará com mecanismos de proteção e segurança, embora não tenha adentrado em detalhes técnicos de como fará isso.
A empresa também mencionou a integração de dados biométricos coletados pelos Galaxy Watch ao fluxo de trabalho médico, focada na prevenção de riscos de saúde com o auxílio da inteligência artificial (IA), permitindo a sugestão de refeições e treinos adaptados com base em interpretações de biossinais.
Preço e disponibilidade
Os novos smartphones chegarão ao Brasil no dia 6 de agosto, mas ainda não tiveram seus preços divulgados; ainda assim, a Samsung já antecipou que a aquisição de algum dos dispositivos durante a pré-venda garantirá até seis meses de Google AI Pro sem custos adicionais.
NOTA DE TRANSPARÊNCIA: O MacMagazine recebe uma pequena comissão sobre vendas concluídas por meio de links deste post, mas você, como consumidor, não paga nada mais pelos produtos/serviços usando os nossos links de afiliado.
Login
