# web & apps · web_apps.tsx
Frontend Builds
Responsive frontend builds — React, Vue or plain JS — matched to your brief's wireframes.
A frontend assignment usually comes with a wireframe or a Figma file, and marks are lost matching it loosely rather than exactly — wrong spacing, a breakpoint that was never tested, an input with no label. We build to the file you were given, check every breakpoint it specifies, and hand back a component structure a teammate can actually read if this is a group submission.
What you get
- Pixel-matched to the wireframe or Figma file you were given
- Responsive across the breakpoints your brief specifies
- Accessible markup — labelled inputs, alt text, keyboard nav
- Component structure documented for a group-project handover
- Cross-browser checked, not just tested in one browser
- A short screen-recording demo included with delivery
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.
Frontend Builds: 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 frontend builds
Backend & APIs
REST or GraphQL APIs built to your endpoint spec, with the auth flow that was asked for.
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
Share your brief.
Paste the frontend builds brief into WhatsApp — the message already names the service. Scope and price come back in writing.