Sheets on iPhone Duo mostly do the right thing, but “mostly” is where the product polish lives. Across closed, open, and partially folded poses, the system moves sheet controls, centers presentations, or slides UI away from the fold so actions do not land in awkward places. The practical takeaway is simple: start with standard sheets and system components, then disable vertical toolbar behavior for the cases where one lonely Close button steals too much width. It is a good reminder that Duo adaptation is less about inventing a new layout religion and more about checking the weird poses before our users do.

Cross-promote your own apps inside the one someone already has open. Icons, names, and prices come live from Apple's iTunes Lookup API — no hardcoded lists to go stale. A SwiftUI "More Fro...

SwiftUI’s iPhone Duo toolbar story is getting more specific now: vertical bars, item axis behavior, compression priorities, and an escape hatch when the vertical layout makes a screen worse. The useful bit is not “new modifiers exist”, it is the judgment around when to let the system adapt and when to pin an item to horizontal space. `axisBehavior(_:)`, `toolbarVerticalEdge`, and `toolbarVerticalCompressionBehavior(_:)` give us just enough control without turning every toolbar into a custom layout project. I like this because it keeps our apps in the system’s lane, but still lets us say, “no, that slider really should not be crammed into the side bar.”

Skip enables the creation of native SwiftUI apps for iOS and Android - skiptools/skip

Download Appstead: App Sales & Reports by SEOU B HOUNKANRIN on the App Store. See screenshots, ratings and reviews, user tips, and more apps like Appstead: App…

Xcode 27.2’s new `project.xcproj` format is one of those boring-looking changes that could save real pain in our codebase. The old `pbxproj` file has always been a merge-conflict magnet, full of flat object tables and IDs nobody wants to review. JSON alone is not the win here; the nicer part is that Apple reshaped the project graph so file membership and build settings read closer to what we actually changed. Not a revolution, no, but for teams still touching `.xcodeproj` directly — and for coding agents trying not to mangle it — this feels like overdue cleanup.

Explore interactive SwiftUI component previews for iPhone Duo in portrait and landscape across closed, partially open, and fully open hinge states.

MIYAKO SUZUKIの「みたび」をApp Storeでダウンロードしてください。スクリーンショット、評価とレビュー、ユーザのヒント、「みたび」に似たゲームを見ることなどができます。

Swift 6 strict concurrency can still leave a nasty hole when Objective-C APIs take plain callback blocks and run them on queues the Swift type system cannot see. The crashes here come from `BGTaskScheduler` and PhotoKit callbacks created inside `@MainActor` code, then invoked off the main actor before the `Task { @MainActor in ... }` body even gets a chance to run. That is the kind of bug that looks “obviously handled” in review, which is why the concrete grep targets and testing advice are useful. If our apps bridge into older Apple frameworks — and of course they do — this is worth reading with crash logs open.