iOS Developer 👨🏽💻 Chairman of the _UINavigationBarPalette fan club.
Manchester, England
Joined June 2012
- Tweets8.4K
- Following205
- Followers7.1K
- Likes8.5K
Pinned Tweet
Here it is! What's New in UIKit in iOS 26.
This was a pretty mammoth undertaking, and it shows – a whopping 64 minute read!
I'll be keeping this article up to date over the beta cycle. Possibly littered with errors. Shout at me if I've made any stupid mistakes.
Link below 👇
Seb Vidal retweeted
Go behind the scenes of Made by Sound.
A story of music, collaboration and craft with @fredagainagain1 and NEST Acoustics. Discover how sound brought the Apple Music logo to life, captured entirely in camera. Just music, made visible.
Seb Vidal retweeted
I’m really proud how our new iOS 27 onboarding turned out for @one_sec_app 🥰
more than 50% faster
Has anyone run into, or better yet found a fix for, this SwiftUI bug where NavigationLinks remain disabled despite having an ancestor NavigationStack?
The navigation link seems to become active when the underlying hosting controller's view is reparented, such as when the navigation controller's interactive pop transition begins.
Yes! The screenshot popup 😭 Used to be so easy to copy to clipboard, then paste into Pixelmator or something to pixel peep.
Now I have to routinely clear my desktop of simulator screenshots.
Death by a thousand paper cuts.
Seb Vidal retweeted
Today I am open-sourcing my custom SwiftUI animation sequencing package that I developed to drive the animations in Letters. It can do all sorts of things!
github.com/jazzychad/Animati…
Anyone else seeing this weird, green-ish hue to the background of sheet presentations?
I don't think this is Duo-specific. Seems to affect sheets with glass backgrounds that transition to the system's default, opaque background when the active detent changes?
One thing building for the iPhone Duo has taught me: just use a UINavigationController for ad hoc "toolbar" buttons...
Even if you don't need the functionality of pushing and popping view controllers onto a stack, it's worth the extra LOC for the correct system placement.
A pattern I've enjoyed using is view controller subclasses vending their own child navigation controllers so API clients don't have to worry about wrapping the view controller themselves.
Oh, and just to add insult to injury, the toolbar(removing:) modifier works when the process is attached to the Xcode debugger, but not when the app is run in isolation...?? 🤯
Safe areas and back button fixed, thanks to @Typ0genius! Buuut now the sidebar toggle (which I have explicitly removed) is back and isn't honouring the toolbar(removing:) modifier.
Sometimes SwiftUI really is the world's most frustrating game of whac-a-mole. Time to rip this out in favour of UIKit... 🫠
Safe areas and back button fixed, thanks to @Typ0genius! Buuut now the sidebar toggle (which I have explicitly removed) is back and isn't honouring the toolbar(removing:) modifier.
Sometimes SwiftUI really is the world's most frustrating game of whac-a-mole. Time to rip this out in favour of UIKit... 🫠
That's fixed. Now the safe areas are borked. I'm very close to throwing in the towel and getting a UISplitViewController involved.
While I don’t doubt the team behind this are working hard to improve it, using Device Hub has made for a challenging summer.
The addition of Slow Animations is certainly a step in the right direction, but I’m looking forward to the return of point and pixel accurate device screen sizes.
I wish Apple would make their mind up as to what the hardware buttons on the Apple Watch should do. Every other year my muscle memory is wrecked...
Double clicking the Digital Crown used to switch between the current and last used app. Then they changed it to open the app switcher. Now they’ve changed it to do…nothing?
One day I'll be able to scroll past one of these tweets without making the obligatory UIViewController subclass → SwiftUI.View remark...
...today is not that day!
