Apps that ship,
then keep shipping.

React Native and Expo for small businesses that need one codebase on iOS and Android. TypeScript-first, native modules where they matter, OTA update pipeline from day one. The right choice for most small-business mobile apps — same experience on both stores, one team maintaining it.

When cross-platform genuinely doesn't fit — deep platform integration, heavy graphics, niche SDK support — we build in Swift or Kotlin. We'll tell you on the discovery call which path is right, and why. Most small businesses don't need native. Some do.

Bigger than a marketing site and bigger than a single page tool — multi-user web apps with auth, database, permissions, billing, and a real admin surface. Next.js on the front, a typed API on the back, PostgreSQL by default. Built for small-business operations, not for venture-scale traffic.

The web app that replaces four SaaS tools your team is stitching together. Custom workflow, custom data model, auth scoped to your team. Most of these ship in four to eight weeks and pay for themselves inside a year by cutting the SaaS bill.

A deliberately small first version — enough to put in front of ten real users, measure what matters, and decide whether to invest further. We scope MVPs tight, ship in four to six weeks, and document the path from MVP to v2 so you're not painted into a corner if the idea works.

Taking over an existing app that's hard to change — inherited from another developer, built on a stack that's aging out, or accumulated enough shortcuts that adding a feature takes a month. We audit, pick the smallest rewrite that fixes the bleeding, and get you back to shipping.

The version-one feature list a client writes before the app exists is almost always wrong. We cut it down, ship the smallest thing that tests the idea, and let actual usage decide what version two is. Every app project starts with a conversation about what we're cutting.

Retrofitting auth into an app is how small businesses end up paying for a rewrite. We set up auth, user model, and permission boundaries on day one — even for MVPs — so the v2 feature work doesn't have to re-architect the foundation.

If a mobile app breaks when the signal drops, users stop trusting it. Every mobile app we ship is designed with offline state in mind — local-first data, optimistic updates, retry queues, and sync reconciliation. The app shouldn't require a perfect connection to be useful.

Sentry for errors, structured logs for backend, and analytics wired on day one. We don't ship apps we can't debug. Every production app we launch has alerts that fire when error rates jump, and dashboards the client can read without us in the room.

TypeScript strict mode. Typed database client (Drizzle or Prisma). Typed API clients shared between mobile, web, and backend. Form validation typed with Zod. When the schema changes, the compiler tells us every place that breaks — before your users do.

Mobile-only (cross-platform) is one price. Web-only is another. Both — shared API, shared design system — is roughly 1.4× either alone, not 2×, because most of the infrastructure work is shared.

Simple auth + CRUD sits low. Add payments (Stripe), real-time features (websockets), file upload and storage, background jobs, and third-party integrations — each one pushes the scope up. We'll break it out on the quote, not surprise you mid-build.

Number of distinct screens, density of custom illustration, and how much of the design we're creating versus adapting from an existing system. A twelve-screen app costs more than a four-screen app — not because each screen costs the same, but because the complexity compounds.

Payment processors, auth providers, CRM, analytics, push notification services, email, SMS, file storage, webhooks into a client's existing systems. Three integrations are common. Seven is a bigger project.

Standard app engagements run six to fourteen weeks. A rushed MVP — under four weeks — means concurrent phases, more senior time, and a higher rate. Standard timelines are priced at standard rates.

Web development is websites and the smaller web apps that live inside a site — booking widgets, quoting tools, light dashboards. App development is the bigger builds — cross-platform mobile apps, multi-user web apps with auth and billing, internal tools, and MVPs for new products. If you're not sure which page your project fits, send a brief and we'll scope it either way.

Cross-platform (React Native via Expo) is the right fit for most small-business mobile apps — one codebase, both stores, one team. Native (Swift or Kotlin) is worth the extra cost when the app needs deep platform integration, heavy graphics, or a niche SDK only the native runtime supports. We'll tell you on the discovery call which path fits your project and why.

A tight MVP — one or two core flows, auth, and a minimal backend — ships in four to six weeks. A fuller v1 with payments, push notifications, and three or four flows is eight to twelve weeks. A cross-platform mobile app with a real backend is typically ten to fourteen weeks end-to-end.

You do. Code lives in your GitHub organization. Cloud resources live in your cloud account (AWS, Vercel, Supabase — whatever fits). App Store Connect and Google Play Console accounts are set up in your company's name. If you ever leave the studio, the whole stack travels with you.

Yes. We handle App Store Connect setup, screenshots, metadata, privacy labels, review submissions, and the first round of review feedback. If Apple or Google rejects the first submission, we handle the back-and-forth until it's approved. The client owns the developer accounts — we just run the submission.

Yes. Push notifications via Expo Notifications or Firebase Cloud Messaging. In-app purchases via Apple's StoreKit and Google Play Billing. Payments outside the stores via Stripe. Subscriptions via Stripe or RevenueCat, depending on whether the app is in the stores or web-only.

Month-to-month care retainers cover OS compatibility updates, SDK version bumps, small feature work, analytics reviews, and incident response. Retainers are optional and cancelable any month. For clients who want a ship-and-done engagement, the two-week launch support period plus an honest handoff document usually covers the first round of issues.

Yes, with an honest audit first. Before agreeing to a takeover we read the code, review the infrastructure, and tell you whether it's salvageable — sometimes it is, sometimes the fastest path is a careful rewrite. Takeovers are a regular shape of work, but we don't accept them blind.