# web & apps · web_apps.tsx
Backend & APIs
REST or GraphQL APIs built to your endpoint spec, with the auth flow that was asked for.
Backend assignments are marked on what happens off the happy path as much as on it — a missing validation error or an auth flow that only works when nothing goes wrong. We build every endpoint in your spec, handle the failure cases explicitly, and seed a test database so whoever's marking it can run it in the first minute.
What you get
- Endpoints matched exactly to your spec sheet or Postman collection
- Auth implemented the way your brief names it — JWT, sessions, OAuth
- Input validation and error responses, not just the happy path
- A seeded test database so a marker can run it immediately
- API documentation generated, not written from memory after the fact
- Load-tested lightly so it doesn't fall over during a live demo
What to send first
- The brief, wireframes or screenshots of what it should look like
- The required stack (e.g. React, Django, Laravel, Node, Flutter)
- Where it needs to run — localhost only, or deployed for a demo
- Any existing code or repository you have already started
How it runs
- 01
Send the spec
The brief, the rubric, any starter code and the versions your marker uses. A photo of the PDF is fine to begin with.
- 02
Scope and quote in writing
We read it properly, ask what is unclear, and confirm a fixed price and delivery date. A small advance confirms the order.
- 03
Build against the brief
Work is tracked task by task against the spec. Longer projects are split into milestones you can review as they land.
- 04
Tested handover
A repo that installs from a README, run against your test cases, with the write-up if your rubric asks for one.
- 05
Fixes and walkthrough
One round of fixes if a marker flags something, and a walkthrough of how it works so you can explain it.
Backend & APIs: common questions
Either. Most coursework only needs to run locally from a README; if your module wants a live demo URL, say so and we include a deployment in the quote.
Yes — the stack in your brief is the stack we use. We do not swap in something more convenient for us.
It depends on the scope of the brief, the stack and the deadline. Send the spec on WhatsApp and you get a fixed price and delivery date in writing before any work starts — no hourly meter.
Turnaround depends on scope and is agreed with the quote. Tell us the real deadline, including the timezone, and we will say honestly whether it is workable before you commit.
// related
Often paired with backend & apis
Frontend Builds
Responsive frontend builds — React, Vue or plain JS — matched to your brief's wireframes.
web_apps.tsxFull-Stack Projects
End-to-end app builds for capstones and group projects, one connected system.
web_apps.tsxMobile App Builds
Android, iOS or cross-platform app builds matched to your course's framework.
./send-brief
Send the spec.
Paste the backend & apis brief into WhatsApp — the message already names the service. Scope and price come back in writing.