Stop Adding a Ternary Every Time a New iPhone Ships: A Table-Driven Resolution Design
Every time a new resolution arrived—iPhone Air, 17 Pro—I was bolting another screen-size ternary onto a 29-branch pile. Here is how I reshaped that into a table-driven design where adding the next device is a one-line data change, with the actual Swift from my wallpaper apps.
How Far Can Android Studio's Migration Agent Take iOS Code Into Kotlin? A Hands-On Evaluation
I fed one screen of my ukiyo-e wallpaper app to Android Studio's migration agent. What the generated Kotlin got right, the 12 fixes it needed, and the review workflow I now run before accepting any of it.
Apple Foundation Models Are Now Free for Most Indie Apps — Three Questions That Decide What I Build
Apple Foundation Models are now free for developers under 2M first-time downloads. Three questions I used to decide which AI features belong in my wallpaper apps.
Replacing a Decade-Old SKPaymentQueue with StoreKit 2 — Migrating 4 Wallpaper Apps with an Antigravity Agent
A field report on migrating SKPaymentQueue-based purchase code to StoreKit 2's Transaction.currentEntitlements across four wallpaper apps — what I delegated to an Antigravity agent, and the traps I only found on real devices.
Handing Crashlytics Stack Traces to Antigravity — Three Weeks Across Four Apps
Paste a Crashlytics stack trace into Antigravity, let it narrow the cause, and drive the fix to the finish. After three weeks across four wallpaper apps, here is what I learned to delegate and what I kept for myself.
Recovering Missing iOS dSYMs Across Six Apps with Antigravity's Background Agent — A Four-Week Operations Log
After migrating Firebase iOS SDK from CocoaPods to SPM, six wallpaper apps saw their Crashlytics symbolication rate collapse to as low as 4.2%. This is a four-week operations log of letting Antigravity's Background Agent track, upload, and verify 1,847 missing dSYMs across six repositories — including App Store Connect dSYM polling and AdMob revenue reconciliation.
Orchestrating Six iOS App Updates in Parallel with Antigravity's Main and Sub Agents
Running six iOS app updates in parallel — new resolutions, Firebase SPM migration, StoreKit 2, and ATT ordering — with Antigravity's Main + 6 Sub agents. The notes on what to parallelize and what to keep serial.
Unifying In-App Review Prompts Across 5 Apps with Antigravity Editor — A Few Days of Notes
Notes from a few days spent unifying SKStoreReviewController trigger conditions across five iOS wallpaper apps I run as an indie developer, using Antigravity Editor's multi-file editing to bring the logic onto one shared coordinator.
Phasing AppLovin MAX into iOS with Antigravity Editor: A Four-Week Implementation Record
A four-week record of phasing AppLovin MAX into four wallpaper apps that had been running on AdMob alone. How I split the work between Antigravity Editor's Inline Edit and Agent Mode, settled the SDK initialization order, and designed the revenue verification gates—written with real code and the decisions behind each step.
Handing Nightly Wallpaper Asset Updates to a Background Agent — Time Budgets, Duplicate Detection, and a Completion Gate
A reproducible account of handing nightly wallpaper asset updates to Antigravity's Background Agent. Covers how to write the task definition, perceptual-hash duplicate detection, one-pass resizing across 12 device profiles, a morning report you can review in five minutes, and the time-budget and completion-gate design that makes unattended runs safe.
Two Weeks of Letting Antigravity Translate Localizable.xcstrings Across 8 Languages
A two-week log of letting Antigravity draft 8-language translations for new keys added to Localizable.xcstrings. What I delegated, what I kept under my own judgment, the unexpected behaviors, and how I reconciled drafts against the existing translation corpus.
Splitting Daily Crashlytics Triage Across Five Antigravity Sub-Agents
Running six indie iOS and Android apps, the morning Crashlytics triage was draining me. I split the workflow across five Antigravity sub-agents (Fetcher, Classifier, Repro, Patch, PR) and locked their input and output to JSON schemas. Two weeks of production data shows where the human review boundary belongs.