Blog
Build notes, architecture decisions, and the occasional hard-won lesson from shipping native iOS, Android, and server-side Swift.
Part 1 of our XCUITest series. The five-layer pyramid we test a production SwiftUI app with, why Apple forces the Swift Testing and XCTest split, the millisecond-cheap source-scanning guards, and seven shapes of coverage that cannot fail.
Part 2 of our XCUITest series. One base class, two byte-identical lanes, structural assertions next to AI-vision contracts, a double-gated --uitesting launch argument, and the hidden-button trick that opens any seeded record in a lazy Table.
Part 3 of our XCUITest series. Container ids overwrite their children, the Button authoring form decides what iOS publishes, a macOS Table is an Outline, menus keep their names on title, and a dozen other measured reasons a stamped identifier never reaches the tree.
Part 4 of our XCUITest series. Why a leg's wall-clock is its query count times 19 seconds, why activate() inside a poll costs a minute, why isHittable is not visibility, the tap that landed on another app, and the iPad, iPhone and macOS traps that name the wrong subsystem.
Part 5 of our XCUITest series. A login smoke test that was vacuous for its entire life, Bool helpers that hid a live product defect, skips that report green, a restored session that donates the wrong identity to every later class, and the rules that fix each one.
Part 6 of our XCUITest series. Stale binaries, simulator contention, automation-mode timeouts and dead hosts; the ten-step diagnosis order that stops you blaming the product; the process that keeps a suite honest; and the ten lines to keep if you keep nothing else.
A TranslationSession is only valid inside the closure that hands it to you. That single constraint decides the batching, the caching and the shape of every object around it.
The PreferenceKey snippet everyone copy-pastes silently reports a frozen 0.0 — and the coordinate space isn't why. Here's the fix, plus scrollPosition(id:) and onScrollGeometryChange.
Feedback scattered across App Store reviews, email and TestFlight isn't a collection problem — it's a loop problem. Here's how to build the loop in SwiftUI.
iOS gives you strong defaults and then stops. Where the platform's guarantees end and yours begin: Keychain and the Secure Enclave, App Attest, ATS and pinning, data-at-rest protection classes, privacy manifests, why jailbreak detection is not a control, and what auditors actually ask.
"Every business needs an app" is a sales pitch, not an answer. What mobile actually changes for a small or mid-sized business, what drives the cost, and how to tell whether you're one of the companies that shouldn't build one.
Seven local packages, one Vapor binary, four public domains. What splitting a Swift project into modules actually buys you, the rule that makes it work, the bug it did not prevent, and when not to bother.
Six years on, this is not a choice between two frameworks — it is a ratio, and every app we ship has both in it. What SwiftUI still does badly, how to bridge in both directions, and how to pick per project.
Swift and MongoDB are not alternatives — but there is a real decision hiding behind that search. Here's when Mongo beats Postgres for a Swift backend, why the old SwiftUI shortcuts are gone, and the wiring that still works.
Unified logging is the best-documented Apple API that almost nobody uses properly. Subsystems, the privacy rules that redact your strings, signposts, pulling logs off a device — and why the server wants a different Logger entirely.
The real sequence from an idea to a live listing: discovery, prototype, MVP, TestFlight beta, App Review, launch. Honest durations for each stage, what actually causes rejections, and the admin that has to start weeks before you think it does.
Not a flamewar. How Android and iOS genuinely differ as software, which platform gives you more accessible support, which app store is actually safer, and how to pick the right devices for a company fleet — from a studio that ships on both.