Dustin McCaslin
Founder-led Apple-platform audit and build work. Remote-first, based in Oklahoma.
I review code the way a shipping Apple-platform builder does
I offer structured code audits for iOS and macOS apps with a narrow scope boundary: architecture risk, dependency health, security-relevant patterns, App Store readiness, reliability, and remediation framing. The public front door is Code Audit Triage, Surface, and Standard, all built around written deliverables rather than live-call consulting.
The audit work is backed by hands-on shipping experience. My portfolio includes 5 apps total, with 4 live releases and 1 macOS app currently in review, spanning creative writing tools, travel journals, card game utilities, memoir apps, and a cross-platform prompt library. Across those repos there are 133K+ source lines and 1,400+ test cases covering iOS, iPadOS, macOS, and Android.
Most native apps I build rely heavily on first-party frameworks such as SwiftUI, SwiftData, and StoreKit 2. The supporting infrastructure leans on secure proxy patterns, rate limiting, and key isolation so API secrets do not live on the device. That shipping background matters when a report needs to separate real release risk from generic scanner noise.
I also build production AI integrations for Apple apps, including streaming, multi-model routing, and safety constraints. That makes the audit work useful not just for conventional app codebases, but for products where AI features, privacy, and release readiness intersect.
What sets this work apart
Builder-readable audits
The audit is written by someone who has shipped the same Apple frameworks being reviewed. The goal is not just to flag issues, but to make the remediation path legible to founders and engineers.
App Store reality built in
Live releases and repeated App Store review cycles shape the work. That makes the audit useful when the real question is whether a build is launchable, resubmittable, or safe to hand off.
Secure-by-default patterns
Secure proxy architecture, key isolation, rate limiting, and dependency discipline are part of the shipping baseline, not an afterthought added only when something breaks.
Clear scope discipline
This is a boutique Apple-platform audit service, not a pentest or certification firm. That boundary keeps the work faster, clearer, and better aligned with smaller product teams.
Portfolio at a glance
Need your code reviewed?
Review the audit options, inspect the sample packet, and start with the smallest decision that moves the project forward.