Numi
Solo design & build · iOS · SwiftUI · Released on the App StoreAI nutrition tracking for iPhone: photo-based meal logging with a vision model, a deterministic health score, and fasting and weight on one timeline.
Work with me · Contract projects
Product design and AI-assisted app development.
I design and build iOS and web apps as one person — product strategy, UX, UI, code and launch. I shipped Numi and Tysha to the App Store and built Karta, a two-sided web platform, with AI tooling and no engineering team. If you have an idea, a prototype that needs to become real, or a product that needs a designer who can also ship, this is how we can work together.
01 — Engagements
Three ways to work together.
Each one ends with something that runs, not a deck. Pick the shape that matches where your product is today; the proposal pins down the rest.
01
App from idea to release
You have an idea and a reason to build it. I take it from problem definition and core flows through UI, implementation, testing and launch support — a released app on the App Store, or a deployed web product.
Best for founders and small teams who need one person to design and ship the first version.
02
Working MVP or prototype
A clearly scoped core workflow, built for real: a deployed web build or an installable iOS build on TestFlight, plus an honest list of what is still needed for production. Enough to test with users, show to investors, or hand to an engineering team.
Best for validating a product before committing to a full build.
03
Design and build partnership
Ongoing UX improvements, new features, coded components and iteration on an existing product — working inside your team’s codebase and conventions, as the designer who also ships.
Best for products with a team that needs design work that ships as code.
02 — What you receive
What a project includes, and what we decide together.
The first list comes with every engagement. The second is real work that some products need and others don’t, so it is scoped per project and named in the proposal rather than assumed.
Included in every engagement
- A written scope: what the first release includes, and what it deliberately leaves out.
- Design assets where relevant: Figma files, flows, and a design system with tokens and components.
- Source code, in a repository you own.
- Deployment or release instructions: App Store Connect and TestFlight for iOS, hosting and environment setup for web.
- A short handover document: how it is built, how to run it, and what to do next.
Defined per project
- Backend and data: hosting, database, authentication.
- Third-party integrations: payments, point-of-sale, maps, email, push notifications.
- Analytics and event tracking.
- AI features inside the product — vision, language models, recommendations — and their running costs.
- Post-launch support and iteration.
03 — Proof
Built on my own, with the same workflow.
Three products, each with a case study that spells out what I built, what AI assisted with, and what stayed a human decision. Two are on the App Store; the third has a public working demo.
Tysha
Solo design & build · iOS · Offline, real-time audio · Released on the App Store, 5.0 ratingSleep sounds for babies and tired parents: real-time synthesized sound, saved Rooms, a fading timer, Siri and Lock Screen control. No accounts, no ads, no sign-up.
Karta
Solo design & build · Web · Guest app + owner dashboard · Public demoQR ordering and payments for restaurants: guests scan, browse in their language, order and pay with no app; owners get a live floor plan, menu editor, analytics and a visible settlement split.
04 — Questions clients ask
The practical answers.
Do you write the code yourself?
Yes, with AI writing the first draft. Claude Code and Cursor generate first implementations from my designs; I review, change and test that code, and I’m responsible for what ships. Numi and Tysha on the App Store, and Karta’s guest app and dashboard, were all built this way, with no engineering team.
Which platforms do you build for?
iOS, in Swift and SwiftUI, and the web, in React, TypeScript and Next.js. I don’t currently offer native Android builds; if you need both platforms from day one, a web app is often the fastest honest answer, and we can talk it through.
Which AI tools do you use, and where?
Two separate things. To build the product: Claude Code and Cursor for code, Figma for design. Inside the product, only when it needs it: vision models (Numi’s photo analysis) and AI recommendations (Karta’s menu recommender). Every case study has a section on what I built and how I used AI.
Who owns the source code and the designs?
You do. Unless we agree otherwise, code is delivered in a repository you own, design files are shared to your workspace, and the App Store Connect and hosting accounts are in your name — so nothing depends on me after handover.
How do we work together?
Remote and async-first, with regular working builds — TestFlight for iOS, a preview URL for web — so you review the real product rather than mockups. Cadence, calls and tools are agreed per project.
How do you scope and estimate?
Start with a short written brief and a call. I come back with a proposal: what the first release includes and leaves out, which of the per-project parts are in (backend, integrations, payments, analytics, support), and an estimate. Every product is different, so there are no fixed prices here; the estimate and the timing come with the proposal, once we’ve talked.
Can you join an existing product or team?
Yes — that is the partnership engagement. I work inside your codebase and conventions, ship coded components and features through your review process, and bring the design side with me.
Are you also open to full-time roles?
Yes, senior product design roles alongside contract work. The résumé has the full history, including nearly a decade at DraftKings.
05 — Start
Tell me about your product.
A few lines are enough: what it is, who it is for, where it stands today — idea, prototype or live product — and the platform you have in mind. I reply with questions, then a proposal.