basics
How long does it take to build the parts every app needs?
Measured against a real codebase: what sign-in, payments, tenancy, email, mobile, and deployment actually contain, and why every estimate for them comes in low.
Writing
Guides on shipping an app: what to build, what to reuse, and how to get it live.
basics
Measured against a real codebase: what sign-in, payments, tenancy, email, mobile, and deployment actually contain, and why every estimate for them comes in low.
agents
Cursor puts the agent in your editor, with multi-file edits and a diff for everything. Here is how that changes the loop, and what to have set up first.
agents
Your own agent, your own model, driven from the chat apps you already use. Here is what that changes about building, and the two things to get right first.
agents
Codex proposes multi-file changes and waits for approval. Here is how that loop works on a codebase with clear conventions, and what to review first.
security
One missing filter is all it takes, and it has no symptoms in development. The structure that makes correct scoping the default, not something you remember.
writing
Files beat a database, and the biggest mistake is blocking the crawlers that actually send you traffic. The whole setup, including what we built for this site.
agents
A walkthrough of the real loop: what you type, what it reads, what it writes, and where you step in. One prompt and one review for a tested feature.
Almost always missing DNS records, not your code. What SPF, DKIM, and DMARC do, the order to set them up, and the From-address mistake that undoes all three.
mobile
Wrap it in a native shell that loads your existing screens. What it costs, what the stores require, and the in-app purchase rule that decides your economics.
agents
Short, specific, and about decisions rather than description. What belongs in a guide file, what to leave out, and why most of them get ignored.
agents
Say what it is, say what it is not, name the example to copy. Three sentences beats three paragraphs, and over-specifying makes the result worse.
security
Twelve checks that separate a demo from something you can put in front of strangers, ordered by how much damage each one prevents.
jobs
No. A queue on your existing database removes a service to run, secure, and pay for. The real tradeoff, and four rules that make jobs reliable.
agents
Hermes keeps context as you go and runs the same core wherever you drive it from. Here is what that changes about a build session, and what to set up first.
payments
The checkout is the easy half. The whole flow, why the webhook is the source of truth, and four failures that let people use what they never paid for.
sign-in
Emailed codes and social sign-in remove the password database and the reset flow. What you gain, what you take on, and the detail everyone gets wrong.
deploy
One command, a $5 box, and a container. What running your own server involves in 2026, what it costs, and when a managed platform is the better answer.
basics
A realistic breakdown of the money and the time: what you pay before your first customer, what is genuinely free, and where the real cost sits.
basics
One Shot is a working app with accounts, payments, email, jobs, security, and mobile shells already built and tested. The complete list of what is included.
agents
Ask a coding agent for an app and most of its first run goes to sign-in, payments, and email, not your idea. Why that happens, and what to do about it.
agents
Sign-in, payments, email deliverability, and keeping customer data separate. Four things where generated code looks right, passes review, and fails later.
getting started
A working application with the universal parts already built. What belongs in one, what does not, and when starting from scratch is the better call.
