Designed, built and run by one developer. You talk to the person writing the code — no account manager, no handoff, no surprise invoice.
A passport & visa photo tool: crop to any of ten official specs, export at the exact pixel size and file limit. It runs entirely in your browser — the image never leaves your device, and there is no upload endpoint to leak it to.
Drop a photo here
or click to choose one
I don't take everything. These are the four shapes of work where one experienced developer beats a five-person team — because there's nothing to coordinate.
Auth, payments, dashboards, multi-tenant data. The kind of app with real users and real money moving through it.
Replace the spreadsheet plus the group chat. Order tracking, scheduling, approvals — things five people use daily.
RAG over your own documents, classification, extraction, drafting. Wired into your workflow with a human check where accuracy matters.
Pull it, clean it, push it. If someone copies between tabs for two hours a day, that's a two-day script.
Most projects die in a document nobody reads. We skip that. I ask questions, you answer them, I write down what I'm building and what it costs.
30 minutes on a call, or a few paragraphs by email. I ask what's actually broken — not what you think you need built.
One page: what's included, what isn't, the price, the date. Agreed before I write a line of code.
Every week you get a URL you can open and click. Not a screenshot, not a status update — the actual thing.
Deployed to your accounts, source in your repo, written handover, 30 days of bug fixes.
Posting prices filters out most of the noise on both sides. These are starting points — the quote is fixed once we agree on scope, and it doesn't move afterwards.
Care plan — $450/month. Hosting, monitoring, backups, security updates, two hours of small changes. Optional, cancel anytime, everything handed over if you leave. Payment: 50% to start, 50% on delivery — Wise, PayPal or bank transfer.
Hiring someone in another country — the risk isn't the code. It's everything around it. Here's how that works with me.
China, UTC+8. It matters in two ways: I answer European and US-East messages within their working day, and there's a real time-zone gap for anything urgent at 2am your time. For most builds that gap costs you nothing — for a live outage it costs a few hours. If you need 24/7 on-call, I'm not the right hire and I'll say so.
Usually yes. I'll look first and tell you honestly. Sometimes the fastest route is keeping 80% and replacing the part that hurts. If a codebase is genuinely beyond saving, I'll say that too, and explain why.
Functional product design — layout, interaction, hierarchy. Not brand identity or illustration. I'll tell you when you need a designer and work with yours.
TypeScript, React or Vue on the front; Node or Python on the back; Postgres or Mongo for data. Boring, documented tools the next developer can pick up. I've watched enough clever stacks become unmaintainable.
New scope gets a new quote before any work starts. Small things — copy, colours, an extra field — I usually just do. Anything structural is a conversation about time and money before it becomes either.
You'll have the repository, a staging URL and a weekly build from week one. If I vanished you'd lose a developer, not the project. That's also why I take 50% up front, not 100%.
Yes. Send it.
Six products built and still running — all designed, coded and maintained by me. That's why I'm opinionated about what happens after launch: servers cost money, releases break, users complain, and features keep moving.
You deal with me directly. The person who answers your email is the person writing the code and the person who gets paged when something breaks.
Based in China, UTC+8. English and Mandarin. If a project isn't a fit, I'll tell you before you spend anything.
18846441559smile@gmail.comNot a requirements document — a paragraph is enough. What's the situation, what have you tried, what would "done" look like. I reply within 24 hours, usually with questions rather than a pitch.
Four fields. That's all I need to start.
I'll read it properly and reply within 24 hours, usually with two or three questions and an honest read on whether I'm the right person for it.
REF