visionOS & Vision Pro Development

Both - I'll give you a direct yes or no first, since half the Vision Pro projects I've been pitched should have stayed iPad apps. If it's a yes, I design the interaction for spatial use from the first sketch and build it on RealityKit and SwiftUI; Constellation, my own shipped visionOS app, is the example. Your existing iPhone or iPad app also already runs on Vision Pro in compatibility mode, so sometimes the answer is a small native layer rather than a full build.

It depends on whether your product uses the space. Good candidates: spatial browsing of dense data (graphs, CAD, architectural review), training or simulation where 1:1 scale matters, ambient reference that benefits from peripheral visibility, entertainment that exploits presence. Poor candidates: traditional 2D productivity, forms, settings, anything the user would open in a queue.

Most SwiftUI views port with minor tweaks. RealityKit-heavy parts are visionOS-specific. I'll map the reuse boundary in the first engagement day so you know what's free and what's bespoke.

Yes. RealityKit runs on iOS, iPadOS, and macOS. If your AR feature or 3D viewer doesn't need visionOS-specific gestures or spaces, you can ship it on iPhone today and bring it to Vision Pro later when scope allows.

Yes, and the ones most affected don't always report it. It shapes more of the interaction design than teams expect: reduced motion settings, how content moves relative to the head, where ornaments sit when the user's gaze fatigues. Worth designing around from the first sketch rather than patching later.

Yes. This is the most common reason teams bring me in. Using the room means mixing SwiftUI windows with RealityKit volumes and immersive spaces, handling gestures on 3D entities, and thinking in world coordinates instead of screen coordinates. Apps that skip this step ship an iPad app that happens to float.

Directly - you're hiring me, one senior iOS engineer who writes the code, rather than an agency that routes you through a project manager and a team you never meet. For a lot of my clients that's the whole point: one person who owns the work end to end.

A quick call can happen within days. For project work I usually need 1-2 weeks to clear the calendar, though I keep some buffer for urgent firefighting.

Yes, from pre-seed to Series C and beyond. For very early teams, a short advisory engagement often makes more sense than a full build: you get the architecture guidance without committing to a large piece of work before you've validated the product.

Everything: code, architecture decisions, code review, documentation, async Slack availability during working hours. No surprise add-ons. I bill for time spent working on your project, not for "thinking about it in the shower."

I'm currently in Vancouver (PST), with full overlap for North American teams. For UK and Europe, I'm online by their afternoon. For Gulf or APAC, we'd agree on overlap hours and handle the rest async. I've worked with teams from San Francisco to Dubai.