Principal mobile engineer.
I lead iOS and Android architecture for myColorado, the State of Colorado's official citizen app — about 2M downloads, 610k monthly active users, 4.8 stars across 144,000+ ratings. The current work covers mobile driver's licenses, verifiable credentials, identity, and the long migrations underneath all of it.
Three-developer mobile team. Three QA engineers. I cover both platform leads, mentor the iOS and Android devs alongside me, and pick up AWS Lambda or legacy PHP when a task crosses the line.
Shipped issuance and presentation of mDL credentials under ISO/IEC 18013-5, integrated with PingOne IAM, ID Dataweb identity proofing, FaceTec biometric liveness, and the SpruceKit credentials runtime. Phase 2 rollout is live and ongoing.
Built a release-gating policy and a structured triage protocol on top of Firebase Crashlytics. Sprint reviews catch regressions before phased rollout. The same dashboards now drive customer-support root-cause work.
Phase 1 scaffold for a shared business-logic core across iOS and Android. XCFramework distributed via Azure Blob Storage, Maven AAR via Azure Artifacts, two-stage Azure Pipelines (Linux for JVM/AAR, macOS for XCFramework).
Two-week sprints. The product manager owns prioritization; I add to the backlog. Migration work slips first when something has to slip; features second, crashes almost never. Net of that, I try to keep the team's options open: smaller PRs, fewer dependencies, and documentation that survives whoever wrote it.
I keep an eye on adjacent state mobile-ID rollouts (CA DMV Wallet, LA Wallet, the Apple Wallet ID-in-Wallet integrations) as input rather than competition. The standards space around mDL and verifiable credentials is moving quickly and I don't want to ship the wrong primitives.