M K Wiro
Subtle - Hardcore
Available for freelance

I build the app and run the server it lives on

Most developers hand off at “it works on my machine.” I keep going — Docker, nginx, PostgreSQL, backups, TLS, deploys — so when something breaks at 2am there is no vendor queue to wait in.

20–30 hrs/week · GMT+7 · English & Bahasa Indonesia

2
apps live on Google Play + App Store
~1,000
people using one of them every day
13
systems running in production
42s → 0.2s
a real query, after I rewrote it
What I do

Four things, done properly

Prices are starting points for a scoped project, not hourly guesses. You get a fixed number in writing after we talk.

Mobile app, empty repo to store shelf

from $5,000 · 6–10 weeks

One Flutter codebase for Android, iOS and Web. I handle the store submission too — including the rejections, which is where most first-time launches stall.

  • Flutter app + the API behind it
  • Google Play and App Store submission
  • Payments, auth, push, offline states
  • Source code and store accounts are yours

Backend and API

from $3,000 · 3–6 weeks

Next.js + TypeScript + PostgreSQL. The unglamorous parts done properly: idempotent payment webhooks, real auth, a schema that survives its second year.

  • REST API with documentation
  • SSO (Google / Apple / phone) and JWT refresh
  • Payment gateway integration
  • Admin dashboard for your team

Get off managed hosting

from $1,200 · about a week

Vercel, Supabase or Firebase bills climbing faster than your revenue? I move the whole thing onto servers you own, with no downtime and no vendor lock left behind.

  • Database migrated, every row verified
  • Docker, nginx, TLS, automated backups
  • Deploy on git push
  • A runbook, so you are not dependent on me

Make it fast again

from $800 · 1–2 weeks

An app that was fine at a thousand rows and is unusable at a million. I find where the time actually goes, fix it, and show you the before-and-after numbers.

  • Profiling report — what is slow and why
  • Query, index and N+1 fixes
  • Measured before / after
  • Notes so it does not come back
How it goes

In that order

  1. 1

    A call, and an honest answer

    Thirty minutes on what you are trying to ship and by when. If I am not the right person, I will say so on that call rather than three weeks in.

  2. 2

    Written scope, fixed price

    You get the scope in writing with a price and a date attached, before any money changes hands. Changes are re-quoted, never absorbed silently.

  3. 3

    Something working, every week

    Not a status report — a build you can open. If it is going wrong, you find out in week two instead of at delivery.

  4. 4

    Handover you can actually use

    Code, servers, store accounts and a written runbook, all in your name. You should be able to hire someone else after me without a rescue project.

Straight answer

What I turn down

Better you know now than after a deposit.

  • Pure visual design — I build well-designed things, but I am not your designer.
  • WordPress, Wix, or no-code platforms.
  • Rescuing a codebase I have never seen, by tomorrow.
  • Anything where the plan is to underpay someone else to do it.
Start here

Tell me what you are trying to ship

What it is, and by when. That is enough for me to tell you honestly whether I am the right person — and roughly what it costs.