01 — Frontend
React
Component architecture, server components, suspense boundaries and state that stays predictable as an app grows.
About
Software that removes real, measurable work.
I'm an independent developer building AI-powered apps — working solo, across the whole stack, from data model to the interface people actually touch.
- App Developer
- Website Developer
- iOS Developer
- SaaS Founder
- Problem Solver
(01)The story
The software I find worth building starts with a cost someone is quietly carrying: hours spent on repetitive formatting, a process only one person understands, information that exists but cannot be reached by the people who need it.
So that is where I start. Before choosing a framework or writing a schema, I want to know what a problem actually costs — in hours, in errors, in things that silently do not get done. That number decides whether something is worth building and what it should look like.
I work across the whole stack: AI pipelines and retrieval systems, Next.js and React front ends, native iOS in Swift, PostgreSQL with row-level security, and the cloud infrastructure holding it together. Being one person across all of it means no handoffs and no places for a project to stall.
(02)Expertise
What I work with, day to day.
Depth in a focused set of areas rather than a shallow list of everything — each one used in production, not just tried.
- 01
AI Applications
LLM pipelines, retrieval, structured extraction and evaluation harnesses built for production rather than demos.
- 02
Next.js & React
App Router architecture, server components and streaming interfaces that stay fast as the surface area grows.
- 03
TypeScript
Strictly typed codebases where the compiler catches whole categories of bug before review does.
- 04
Swift & iOS
Native SwiftUI apps with offline-first sync, background location, push notifications and App Store delivery.
- 05
Supabase & PostgreSQL
Relational modelling, row-level security, realtime channels and migrations that survive a growing team.
- 06
API Development
Versioned REST services with documentation, webhooks, rate limits and predictable error semantics.
- 07
UI/UX Design
Design systems, interaction detail and accessibility — treated as engineering concerns, not decoration.
- 08
Cloud Applications
Serverless and queue-backed architectures with observability, sensible cost controls and real disaster planning.
(03)Skills
The stack I build with.
Depth in a focused set of tools rather than a shallow list of everything — chosen because they hold up in production, not because they trend well.
02 — Frontend
Next.js
App Router, streaming SSR, route handlers, caching strategy and edge-ready deployments on Vercel.
03 — Frontend
TypeScript
Strict-mode types, discriminated unions and inference-first APIs that make invalid states unrepresentable.
04 — Mobile
Swift
Modern Swift with async/await, structured concurrency, and SwiftUI backed by a clean data layer.
05 — Mobile
iOS Development
SwiftUI, MapKit, Core Location, background modes, push notifications and App Store submission.
06 — Backend & Data
Supabase
Postgres, row-level security, realtime channels, storage and auth wired into production apps.
07 — Backend & Data
PostgreSQL
Schema design, indexing, migrations, query tuning and RLS policies that hold up under real load.
08 — Frontend
Tailwind CSS
Token-driven design systems, dark mode, container queries and interfaces that stay consistent at scale.
09 — Backend & Data
REST API
Versioned, well-documented endpoints with sane pagination, idempotency, rate limits and webhooks.
10 — AI
AI Integration
LLM pipelines, structured output, tool use, RAG, evaluation harnesses and cost/latency budgeting.
11 — Platform
Authentication
OAuth 2.0, magic links, sessions, MFA, role-based access control and secure token handling.
12 — Platform
Cloud Architecture
Serverless and queue-backed systems, background jobs, observability and cost-aware scaling.
13 — Craft
UI/UX
Interface design from wireframe to polish — hierarchy, motion, accessibility and honest empty states.
14 — Platform
Git
Trunk-based workflows, clean history, reviewable commits and reliable release branching.
(04)Principles
How I work.
- 01
Solve the business problem
Technology is the means. If a simpler approach solves it better, that is the recommendation you will get — even when it means a smaller project.
- 02
Ship, then refine
Working software in front of real users beats a perfect plan. Weekly increments on a live URL, not a reveal at the end.
- 03
Build it to be handed over
Documented, typed and conventional. Your team should be able to extend it without needing me on a call.
- 04
Privacy is a default, not a tier
Collect the minimum, be explicit about it, delete it when it is done. Security is never an upsell.
Available for select projects
Have a problem
worth solving?
Tell me what your team is carrying manually today. If software can remove it, you will get a straight answer on how — and if it cannot, you will get that answer too.