A fast global choice game became a working product, backend and launch system.
Product direction, native interaction design, aggregate result logic, privacy boundaries, a production API, sharing and App Store presentation were handled as one connected loop.
Proof21/21 tests passed. Five final App Store visuals completed from Release UI.
Personal health signals, turned into experiments without manufacturing certainty.
A privacy-first evidence engine, native product system and device QA workflow translate Apple Health signals into prospective sleep experiments while keeping scientific authority out of the interface.
Proof56/56 canonical sleep-product tests passed; the physical Apple Health comparison flow was exercised.
Ctrl+F for the camera roll—screenshots and spoken moments included.
On-device OCR, speech indexing, Turkish-aware ranking and timestamp navigation turn selected media into a private search layer, with no product backend or account required.
ProofXCTest, Debug and Release builds, connected-device install and a local Release archive passed.
Consumer products, deep technical systems, fast prototypes and careful launch work. The through-line is an appetite for hard problems—and a refusal to confuse motion with progress.
The useful version of the early questions—before a brief becomes a specification.
01What does getyear build?+
Native iOS products, consumer AI experiences, local-intelligence systems, technically ambitious prototypes and the QA and launch systems around them.
02Can you take a product from idea to App Store?+
Yes. Product direction, experience design, SwiftUI engineering, StoreKit, device QA, release evidence and App Store presentation can run as one connected engagement.
03Do you work with existing product teams?+
Yes. A focused engagement can own a risky product slice, clarify a stalled direction, harden a release path or add senior product and engineering continuity to an existing team.
04Is the work limited to MVPs?+
No. The appropriate outcome can be a decision-ready prototype, a production-grade vertical slice or a launch-ready product. The proof standard is matched to the actual claim.
05How does a project start?+
Send the messy version: the problem, the ambition, what already exists and the uncomfortable constraints. We begin by identifying the next decision that reduces the most risk.
Select collaborations · 2026
Have something worth building?
Bring the ambition, the uncertainty and the uncomfortable constraints. We’ll find the clearest path through.