/01
Mobile development
iOS and Android apps, soup to nuts. Discovery, design, build, binary signing, store submission, in-app purchase, and the back-and-forth with App Review.
We build incredible apps for startups.
Twenty years building products. We sit inside small teams and ship apps to the App Store, Play Store, and the web. We also run a couple of our own.
Dashboard.tsx
api.ts
● main
01
// src/screens/Dashboard.tsx02
import { View } from 'react-native';03
import { useMetrics } from '@/hooks';04
import { Card, Stat } from '@805/ui';05
06
export function Dashboard() {07
const { data } = useMetrics();08
return (09
<Card title="Today">10
<Stat label="MRR" v={data.mrr} />11
<Stat label="USERS" v={data.users} />12
</Card>13
);14
}
● typecheck ok
● 2 tests passing
14 ln · 0 todos
9:41
●●●▮
DASHBOARD
MRR$24,820
USERS1,204
SIGNUPS+38
01
//
Services
What we build
Full-stack product engineering.
We work alongside founders and small teams. Strategy, design, code, ship, and most of the boring parts in between.
/02
Web development
Marketing sites, SaaS dashboards, internal tools, real-time apps. Phoenix LiveView when it fits. Laravel when the team or the ecosystem calls for it.
/03
Desktop development
Desktop apps for macOS, Windows, and Linux. Small downloads, quick cold starts, code-signed and notarized. Tauri and Rust under the hood, TypeScript on top.
/04
UI / UX design
Product design from the person writing the code. Flows, components, design tokens, and the small interaction touches that get dropped when design and engineering live on different teams.
/05
Technical consulting
Architecture reviews, stack decisions, hiring loops, and fractional engineering leadership. For teams that need a senior engineer (or EM) a few days a week.
/06
App Store operations
We've shipped paying apps through both stores. Privacy manifests, IAP setup, ASO copy, screenshots, App Review. We've seen the rejections and gotten through them.
02
//
Stack
What we use
The short list of tools we know well.
We pick stacks that age well and don't slow a small team down. Below is what we reach for by default.
CapacitorFramework
Firebase & Google CloudBackend
React (TypeScript)UI
Phoenix LiveView (Elixir)Backend
Laravel (PHP)Backend
React (TypeScript)UI
TauriFramework
RustBackend
React (TypeScript)UI
03
//
Work
Apps we build & operate
Apps we built. Apps we still run.
Demoworthy
demoworthy.com ↗Build an interactive API demo in seconds. Spin up a live, embeddable sandbox where prospects can edit code, hit your API for real, and see responses inline. Built for sales teams who'd rather show than tell. Built and run by 805 Software.
Botbudget
botbudget.com ↗A free AI cost calculator. Estimate spend across OpenAI, Anthropic, AWS Bedrock, and more, with starter templates for chatbots, voice agents, and RAG systems. Built and run by 805 Software.
// CLIENT WORK
// UNDER NDA
Mobile apps shipped to both stores for early-stage startups.
04
//
Process
How we work
How we actually work.
We sit inside your repo, your standups, and your Slack. We write the decisions down so the work outlives the engagement.
// AI METHOD
Two years writing code with AI. We've worked some things out.
AI lets a small team ship like a bigger one, but only if you treat it like a junior with infinite enthusiasm. We use it for scaffolding, refactors, and tests. We don't let it pick the architecture or commit code we haven't read line by line. The result: code your team can ship on day one and still understand a year later.
- ▸ Write the spec before the code. Every feature, no exceptions.
- ▸ Every AI-generated change gets reviewed, typed, and tested.
- ▸ No mystery files. No dead code paths. No "I think the AI added that."
/01
DISCOVERY
A working session and a short scope. Users, constraints, success metrics, the things already broken.
We write down what we agreed to before any code is written.
You get: a one-pager with goals, risks, and a recommended architecture. Yours to keep, no strings.
Week 1
/02
SHAPE
We write the spec the way we'd write it for a new engineer starting Monday. Milestones, demo-driven
slices, what's in scope and what isn't.
You get: a milestone plan with target dates, design prototype, and a working repo skeleton.
Week 1–2
/03
EMBED & PAIR
We work as part of your team. Your Slack, your standups, your code review. We pair with AI the way a
senior engineer would: daily commits, weekly demos, every AI-generated change reviewed, typed, and
tested.
You get: working software every week, a changelog, and architectural decisions captured as specs in the
repo, not in a chat window.
Build phase
/04
SHIP
We handle the unglamorous parts: code-signing, App Store + Play Store submissions, privacy manifests,
App Review, analytics, crash reporting, on-call.
You get: a launched app, a working CI/CD pipeline, and the credentials and admin access in your name.
Launch
/05
DOCUMENT & HAND OFF
Every project ships with a README that gets a new engineer productive in a day. Architecture,
runbooks, decision logs, on-call playbooks, and the rationale behind the trickier calls.
You get: a self-serve handoff with everything you need to maintain your app over the long term.
Ongoing
05
//
About
Who's behind 805
Hi, I'm Jake. I run 805 Software.
Tech founder, product engineer, and engineering manager. 20+ years building B2B and consumer software. Hands in the codebase, not a layer above it.
I've spent the last two years figuring out how to write code with AI without making a mess of it. What I aim for: code your team can read, tests that catch real bugs, and decisions you can trace back to written specs.
I've shipped iOS and Android apps end-to-end, stood up Phoenix and Laravel backends from zero. The boring parts work because I've done them before.
Have a product that needs to ship? Let's talk.
Tell us what you're building, what's blocking, and roughly when you need to ship.
hello@805software.com ↗