I bought a domain, built a full stack site, stood up a database, wired an email pipeline, and pushed it live, all in one night, in under five hours, from an iPad. No laptop. No desktop. No terminal.

People hear that and assume I'm exaggerating the constraint for effect. I'm not. There's no Terminal app on iPadOS in the way developers mean it. No local server running in the background. No command line where you just type the thing and it happens. Everything I do, I do through a browser tab.

What that actually means in practice

The toolkit looks deceptively simple from the outside: a chat interface to think through architecture and write code, GitHub's web-based editor to commit it, and a hosting platform that auto-deploys the moment code lands on the right branch. That's it. No local dev environment, no npm run dev humming away on a second monitor, no terminal tabs stacked twelve deep.

What that setup forces is a different relationship with the code than most developers have. You can't lean on a local environment to catch your mistakes before they're public. Every commit is closer to "live" than it would be in a traditional workflow, because there's no comfortable in-between step where you're just running things locally and nobody can see if it breaks. You write more deliberately because the feedback loop runs through an actual deployment, not a sandbox.

The build itself

In one sitting: domain purchased and pointed at a hosting provider, a coming-soon page live immediately so the address wasn't sitting empty, then the real architecture going in behind it: a modern React framework, a database with proper access policies so the data isn't wide open to the internet, and a serverless function handling email capture that fires a real, branded welcome email the moment someone signs up. Dark mode and light mode, both fully designed, both respecting whatever the visitor's device prefers.

None of that is hobby-project scope. That's the actual shape of production infrastructure, the kind of stack a small company would hire a contractor to stand up. The difference is I built it without a single piece of dedicated hardware most people would consider mandatory for the job.

Why this isn't a party trick

It's tempting to treat "I did this from an iPad" as a fun constraint, a neat flex, the development equivalent of cooking a full meal with one pan. But I don't think that's actually what it proves.

What it proves is that the bottleneck in building real things has shifted. It used to be access, to hardware, to environments, to the specific machine configured exactly right. Increasingly, the bottleneck is judgment: knowing what to build, in what order, with what tradeoffs, and being able to direct the tools that exist now toward that outcome. The iPad didn't do the thinking. I did the thinking. The iPad just proved the thinking didn't need anything more elaborate sitting underneath it.

That distinction matters more than the device. A laptop wouldn't have made the architecture decisions better. It would have made typing marginally faster and given me a few more apps I didn't end up needing.

The actual proof of concept

This site isn't just a portfolio entry that happens to exist. It's evidence, in a very literal sense, of what I can do with constraints most people assume are disqualifying. If I can take a project from an empty domain to a live, secured, fully wired application in one sitting on hardware that wasn't built for this, that's not a workaround. That's the actual skill on display.

The site is the deliverable. The method is the pitch.