Looking good! I feel like you can break the rules and ignore the Duo’s trailing safe area for the Fonti splash screen. The text doesn’t appear optically centred as it is :)

The highest vibe-coded slop signal is a SwiftUI app not using a damn List and instead rolling its own with a ScrollView and (Lazy if you’re lucky)VStack, with custom styling 🫠

Nope, I’m doing this too. I still write a lot of UI code by hand, because agents still do the whackiest shit with UIKit and SwiftUI, and I also enjoy building UI myself. A lot of what I set Claude up to do is the “back end” front end stuff, business logic, database stuff, etc. That’s not the part of the job I really enjoy, but I still review everything.

Got an 18 ready for collection, but been away so haven’t had the chance to collect - I can get excited about that!

7-series chips will be just around the corner in time for my unboxing 🫠

Only 115 days until mine is ready for collection 🥲

X: The Everything App is literally a museum of awful UX decisions.

Ah. In that case… 😄

Villain?? UIScrollView walked so UICollectionView could run…

Truly an unsung hero…

Yeah, that’s probably expected behaviour as UISplitViewController vends its own navigation controller. You end up having nested navigation controllers and, subsequently, two navigation bars.

If you can bear to use a UISplitViewController and UITabBarController, this is a non-issue in UIKit.

There are two factors at play, as far as I’m concerned 1. They’re Telegram. They can get away with it because they’re a value-add to the platform. Users would be frustrated, and it would ultimately be bad PR for Apple if the app disappeared for any prolonged period of time. 2. I’m not sure Apple _really_ care about this sort of use of SPI. They _do_ care about breaking sandbox, or anything which might infringe on a user’s privacy, but NSClassFromString-ing _UILiquidLensView? Eh. Use at your own peril. It might break. It might not. That’s on you. :)

After almost 3 hours in review, Duet’s iOS 27 update is ready to go* *Unfortunately, this is not including the added iPadOS support because…I’ve gotta make screenshots 🫠

I know what you’re saying…

API surface probably hasn’t changed…

Oh, the joys of dealing with ASC infrastructure on a dodgy hotel Wi-Fi network... 🫠

Duet's iOS 27 update isn't _really_ ready but it's also going to have to be... 9K lines of code, 347 commits, and 250 files changed. Still got a bunch of bugs to iron out before I'm happy with it, but they can come in 1.6.1 patch.

UIKit still respects the value associated with the UISupportedInterfaceOrientations key in your Info.plist on the iPhone Duo when the device is fully folded close. I’m guessing what you’re seeing in this demo is just the horizontal layout because, by default, upside down is not a supported interface orientation unless manually opted-in. If you change the Color views for something like Text, it should become apparent that you’re stuck in either of the two landscape orientations?

Shoutout to @_inside for tracking down the implementation of the iPhone Duo’s fold effect in record time. SBContinuousFoldEffectViewController “just” appears to be using a CAMeshTransform on backdrop layer, with a variable blur filter, and some carefully placed gradient layers. Beautifully simple.