Snapp Technology
Hi folks,
Swift keeps refusing to stay in the neat little Apple-platform box, and honestly, good.
This week we’ve got Swift on the web, SwiftUI picking up the boring-but-needed pieces we used to wrap ourselves, foldable iPhone prep landing in real developer checklists, and on-device foundation models doing actual app work instead of demo magic.
The thread is simple: our apps are being asked to stretch — across screens, runtimes, toolbars, tests, messages, and AI workflows — and the best tools here are the ones that delete ceremony without pretending the edge cases disappeared.
Articles
Swift
What’s new in Swift: August 2026 Edition
Swift’s August roundup is very much a “look how far outside Xcode this language is wandering now” moment. Elementary and ElementaryUI push Swift deeper into web UI work, SwiftTUI brings state and animation ideas into terminal apps, and the Windows story keeps getting less theoretical. If our mental model of Swift is still mostly “the language we use for iOS screens,” this digest is a useful shove. The ecosystem is getting wider, messier, and more interesting — as it should.
UI / UX
iPhone Duo: First Developer Good-to-Knows
The foldable iPhone conversation is no longer just gadget gossip; it’s a layout problem with a hinge in the middle of it. The useful bits here are practical: trust size classes over device assumptions, test asymmetric safe areas, let system containers manage bars, and don’t hide core features behind some cute folded pose. I like the warning baked into all of this — if our app only works because we guessed the shape of the device, we’re already late. Duo support sounds flashy, but most of the work is just honest adaptive design.
Adaptive SwiftUI toolbars in iOS 27
SwiftUI toolbars are getting a vocabulary for the thing we’ve all been faking: what matters when space runs out. visibilityPriority, ToolbarOverflowMenu, pinned trailing items, and minimization behavior give us knobs instead of hoping the framework guesses our hierarchy of actions correctly. That matters more now with resizable windows, search taking over chrome, and devices that may change shape mid-session. Who doesn’t like deleting a weird custom “more” button and letting the system carry the overflow story properly?
SwiftUI has a native WebView in iOS 26
The little UIViewRepresentable WebView wrapper we’ve all copied between projects can start packing its bags. iOS 26 gives SwiftUI a native WebView, and WebPage covers the bits real apps need: title, loading state, progress, history, secure-content state, and async JavaScript. The catch is small but easy to miss — import both SwiftUI and WebKit, because this arrives through a cross-import overlay. Keep the old wrapper for older deployment targets, sure, but new code gets pleasantly boring here.
Testing
Swift Testing explained with code examples
Swift Testing is settling in as the default path, and the migration story is getting clearer: @Test, #expect, #require, parameterized tests, attachments, and exit tests where the platform allows them. The big win is not just fewer assertion names to remember; failure output is closer to the expression we actually wrote, which helps when CI is yelling and coffee has not kicked in yet. XCTest still has a place for UI automation and performance work, so no need for a dramatic rewrite. But for most unit tests in our codebase, the modern shape is hard to argue against.
Utils
SQLiteData
SQLiteData feels like SwiftData for teams who still want the database to be real. You get familiar wrappers like @Table, @FetchAll, and @FetchOne, but underneath it’s SQLite, GRDB, type-safe queries, and CloudKit sync without pretending schema design doesn’t exist. I like that tradeoff: a little more upfront database thinking, a lot more control when our apps grow past the toy phase.
Video
043 - RCS
RCS has been easy to ignore if most of your world lives inside iMessage, but cross-platform messaging is finally less awful on iPhone. The real-world test here — texting friends in Germany for a month and checking whether it stayed free — is more useful than another feature checklist. iOS 26 adding end-to-end encryption makes the story feel less like a grudging compatibility layer and more like something users may actually trust. Not glamorous, no, but our apps live in the same user expectations soup as Messages does.
Building a Plant Identifier with Foundation Models
A plant identifier is a nice excuse to see Foundation Models image attachments doing something concrete: pass an image, generate a structured plant name, then keep the conversation going with follow-up questions. The smart part is not re-analyzing the image every time; caching the identified plant keeps the UX from feeling like it is paying the same expensive bill again and again. There are rough edges, including model weirdness and real-device requirements on iOS 27, but that’s useful honesty. This is the kind of AI demo that maps cleanly to our own apps: identify once, ask many times, stream the answer when it gets longer.