Normal view
- Scienze Notizie
- Una lama di 3.000 anni fa nasconde un segreto: fu forgiata con materiale proveniente dallo spazio
Backporting SwiftUI APIs
I can improve the process of removing backwards compatibility shims by using conditional compilation to remind me when they’re no longer necessary!
[…]
This does mean that the first time we change our deployment target, we’ll get a bunch of compilation errors. But given the nature of how
Backportis implemented, this should be a relatively quick process to move past. (And of course, you’re welcome to use#warninginstead of#error).
SwiftUIBackports mirrors Apple’s SwiftUI API names, shapes, behavior, documentation, and availability where practical. This keeps app code familiar today, and easy to migrate away from once your deployment target reaches the native API.
Backports are discovered through
.backport, theBackportnamespace, orbackport-prefixed environment values.
Usually, we don’t see many new APIs in intermediate releases like 27.1, but this time is different. Apple introduced several new iPhone Duo-related APIs in the 27.1 release. This week, we will learn how to use all of these new APIs without bumping your project’s target version.
[…]
Here we introduced the
toolbarVerticalBehaviorfunction on theBackporttype that handles availability checks and calls the new APIs if available or returns a plain view when it is not available.
Previously:
FruitMenu Redux
FruitMenu Redux revives a utility (FruitMenu) that brings lost Mac OS Classic features to Mac OS X. Specifically, it restores the fully customizable Apple menu.
It’s no longer a haxie that works by patching the operating system. Now, it’s a regular app that hooks into other apps (e.g. to switch to a particular window) using the accessibility APIs.
The first step was to implement every FruitMenu feature that’s still possible in the current macOS security environment. That immediately ruled out features requiring patching menus (sigh, I really miss patching menus) and features that require privileges now gated behind restricted entitlements. I also added support for viewing and executing Shortcuts.
[…]
Additionally, you can set a hotkey to any item you add to FruitMenu Redux!
[…]
Because SwiftUI doesn’t support dynamic menus, I had to rewrite all the menu code to use AppKit’s NSStatusItem and NSMenu as NSMenu is now a first-class citizen on macOS and fully supports dynamic submenu building. This means that FMR doesn’t even try to build the contents of a folder under you actually attempt to show the contents of the folder. Not only is this significantly faster, but it also uses significantly less memory.
FruitMenu is now available (Mastodon):
A built-in visual editor displays your menu on the left and a library of over 30 item types on the right. You drag items from one to the other (almost like Font/DA Mover, the best UX ever created). The library includes files and folders, submenus, Running Applications (and you can enable an option to show open windows and tabs), Mounted Volumes, Recent Items, Force Quit, Sleep, Restart, Shut Down, Shortcuts, Software Update, separators, System Settings panes, and more!
Anything you put in the FruitMenu Redux Items folder in your Library also appears in Files, folders, and aliases.
$10 (with $7 intro price), not in the Mac App Store because of accessibility.
OMG, Core Transferable, why do I have to declare a public UTI in my info.plist for internally dragging from one list in my app to another list in my app?! It’ll never be decoded by another app!
This was the fix to a bug I reported. With the new SwiftUI drag API, you apparently have to declare private internal drag types in your plist (on Tahoe, but not on Golden Gate).
Xounds, which plays sounds in response to user interface actions, is also back. Unlike FruitMenu, this one never appealed to me—I actually prefer to have the audio muted most of the time. I do find it interesting that it supports the old sound set files from Mac OS 8. Apple dropped the APIs for playing these way back during the 64-bit transition, but Xounds knows how to extract and play the audio.
Previously:
Suporte da Apple, SmartGym, Tripsy e outros apps têm interfaces adaptadas ao iPhone Duo
Com o início das entregas do iPhone Duo previsto para esta sexta-feira (23/10), alguns desenvolvedores de aplicativos (inclusive a própria Apple) estão correndo contra o tempo para adaptar os softwares ao novo formato.
No caso da Maçã (que, obviamente, já adaptou a maioria dos apps da empresa por meio de atualizações de sistema), a novidade é o aplicativo Suporte (Support), atualizado hoje para a versão 5.17 com “suporte ao iOS 27.1 e iPhone Duo”.
Posts relacionados
Partindo para os apps de terceiros, o SmartGym chegou recentemente à versão 8.1 com uma interface que se adapta à forma como o usuário posiciona o dispositivo, incluindo visualizações lado a lado, em tela cheia e outras novidades.
SmartGym is ready for the iPhone Duo! A massive update, designed to take full advantage of every pose. Already available on the App Store.https://t.co/piwzqQpFMH pic.twitter.com/4pAGyXGCQV
— Matt Abras (@AbrasMateus) October 21, 2026
O Tripsy também já foi atualizado para suportar as novas visualizações do dispositivo. Como você pode conferir na captura de tela abaixo, a novidade já está disponível na versão 3.10.3 do aplicativo, liberada recentemente.



A lista ainda inclui apps como o Flighty (versão 4.11.2), que permite acompanhar voos de mãos livres quando o aparelho está posicionado em formato de tenda, o Instapaper (10.1) e o aplicativo oficial da Sonos (90.1).
Certamente, muitos outros ainda virão!
