Development

Websites, web apps and mobile apps.

Three kinds of build under one roof: the marketing website, the thing people log into, and the app on their phone. We build what we design, front end and back end, and hand it over with a guide so you are never stuck waiting on us.

~/yourstartup
$ bad-design build --all› website ............ 24 pages› web app ........... auth, roles, api› mobile ............ ios + android✓ contrast checks passed✓ keyboard nav passed✓ forms → CRM connected✓ backups + monitoring on$ handover --to your-team› you can run this without us

Illustrative log

Three things we build

Site, app, or the thing people log into

Most companies need one or two of these. Pick a tab for the honest difference.

The site that sells while you sleep

Your marketing site: homepage, service and product pages, industry pages, blog, case studies, careers. Pages your team can edit without opening code.

  • Next.js
  • Webflow
  • Framer
  • WordPress

2 to 6 weeks, depending on page count

Typical projects

  • Marketing site rebuild
  • Landing pages for campaigns
  • Blog and resource hub
  • Pricing and comparison pages
  • Migration off Wix, Framer or an old WordPress

What the build includes

  • Design build, exactly as approved
  • CMS so marketing can publish alone
  • SEO basics: structure, schema, sitemaps, redirects
  • Forms wired to your CRM or inbox
  • Analytics and event tracking

In plain English

Front end and back end

Two halves of the same build. You need both, and knowing which is which makes every conversation with a developer easier.

Front end

What people see

The screen, the words, the buttons.

Everything in the browser or on the phone: layout, type, images, animation, forms, the way it responds to a tap. If it looks wrong or feels slow, it is usually the front end.

  • Turns the design into real screens
  • Works on a phone, a laptop and a projector
  • Keyboard and screen reader friendly
  • Loads fast on a bad connection
  • React
  • Next.js
  • TypeScript
  • CSS

Back end

What remembers

The part that stores, checks and sends.

The server side: your database, your logins, your business rules, payments, emails, connections to other tools. Nobody sees it, and everything breaks without it.

  • Stores your data and keeps it consistent
  • Checks who is allowed to see what
  • Talks to Stripe, your CRM, your ERP
  • Runs jobs, exports and reports
  • Node
  • Postgres
  • REST + webhooks
  • Cloud hosting

What happens when someone clicks a button

  1. 01

    Someone clicks

    A visitor taps a button or submits a form.

    Front end
  2. 02

    The screen asks

    The front end sends a request: who is this, what do they want?

    Front end
  3. 03

    The rules run

    The back end checks permissions and applies your business logic.

    Back end
  4. 04

    The data moves

    Records are read or written in the database, and other tools are told.

    Back end
  5. 05

    The screen updates

    The answer comes back and the page shows it, fast enough to feel instant.

    Front end

Your turn

Change the code, watch the button

This is front end work in miniature: a few lines of CSS, a live result, and a contrast check that tells you when it stopped being readable.

button.css

Edit any line. The preview updates as you type.

Live preview

Get a free roast
—Set a background and a colour to check contrast.

Pick the right platform

Built on what you can maintain

We're not married to one tool. We pick the platform your team can run without us.

PlatformBest forWho editsWe pick it when
Next.jsMarketing sites, web apps, anything customMarketing via a CMS, developers in codeYou need custom logic, speed and room to grow
WebflowMarketing sites that change weeklyMarketing team, visuallyYou want marketers shipping pages without developers
FramerFast launches and animated sitesMarketing or design teamSpeed to launch matters most and the site is mostly marketing pages
WordPressContent-heavy sites, existing installsContent team via the editorYou already run on it, or you publish a lot of long-form content
React NativeiOS and Android appsDevelopers, content via your back endThe job genuinely needs a phone app, not a mobile website

More than speed

Eight things we build for

Fast is the one everyone quotes. These are the other seven, with what each one actually means and how you would notice it.

  • 01

    Speed

    It loads before people give up.

    Core Web Vitals in the green, images and fonts optimised, as little JavaScript as the job needs.

    You notice it: Bounce rate drops on mobile

  • 02

    Accessibility

    It works for people who don't use a mouse or see well.

    WCAG 2.2 AA contrast, real focus states, keyboard paths, labelled forms, reduced-motion support.

    You notice it: Procurement and legal stop asking questions

  • 03

    Security

    Your data and your users stay yours.

    HTTPS everywhere, hardened headers, validated inputs, secrets in environment variables, dependencies kept current, sensible roles.

    You notice it: Security reviews go quiet

  • 04

    Findability

    Google and AI answers can read you.

    Clean heading structure, server-rendered text, schema markup, sitemaps, 301s on every old URL.

    You notice it: You keep the rankings you already had

  • 05

    Reliability

    It stays up, and you know when it doesn't.

    Staging before production, backups, uptime and error monitoring, a rollback that takes one click.

    You notice it: You hear it from a monitor, not a customer

  • 06

    Maintainability

    The next person can work on it.

    Components instead of copies, readable naming, documented setup, code in your own repo.

    You notice it: Small changes stay small

  • 07

    Editability

    Marketing ships without a developer.

    A CMS with real fields and hints, preview before publish, and a short training session on handover.

    You notice it: You stop queueing for text changes

  • 08

    Measurement

    You can see what the site is doing.

    Analytics with named events on the things that matter, forms tracked end to end, dashboards you can read.

    You notice it: You can answer where leads came from

The numbers behind two of them

Speed and access, measured

We build to Google's "good" Core Web Vitals thresholds and WCAG 2.2 AA. Slow, inaccessible products lose buyers before they read a word.

LCPLargest Contentful Paint

≤ 2.5s

How fast the main content shows up

INPInteraction to Next Paint

≤ 200ms

How quickly the page responds to a tap or click

CLSCumulative Layout Shift

≤ 0.1

How much things jump around while loading

Targets from web.dev Core Web Vitals, measured at the 75th percentile.

Accessibility checklist

  • Text contrast meets WCAG 2.2 AA
  • Visible focus states on every control
  • Full keyboard navigation
  • Alt text on meaningful images
  • Form labels and clear error messages
  • Respects reduced-motion settings

It has to fit your stack

What we connect it to

Nothing here is a plugin dumped in and forgotten. Each connection gets tested end to end before launch.

  • Leads + CRM

    • HubSpot
    • Salesforce
    • Pipedrive
    • Zoho
  • Payments + billing

    • Stripe
    • Razorpay
    • Paddle
  • Auth + identity

    • Google SSO
    • Microsoft Entra
    • Magic links
    • Roles and teams
  • Comms

    • Email (Resend, SES)
    • WhatsApp
    • Slack alerts
  • Data + analytics

    • GA4
    • Plausible
    • PostHog
    • Looker Studio
  • Ops

    • Google Sheets
    • Notion
    • Zapier or Make
    • Your own API

How it runs

Handed over, not held hostage

A website, web app or mobile app that loads fast, works for everyone, and that your team can run without us.

  • Website build

    Next.js, Webflow, Framer or WordPress

  • Web app build

    Dashboards, portals, internal tools and MVPs, with logins and roles

  • Mobile app build

    iOS and Android from one codebase, store setup included

  • Front end

    Your design, turned into fast, accessible screens

  • Back end

    Database, APIs, business rules and the integrations you already pay for

  • CMS setup

    Blog, case studies and pages your team can edit

  • Quality pass

    Speed, accessibility, security, findability and monitoring

  • Care plan

    Updates, fixes and small changes after launch

  1. 01

    Scope

    Pages or screens, data, integrations, who edits what. You get a fixed plan, not a surprise invoice.

  2. 02

    Setup

    Repository, environments, design tokens and components, CMS or database schema.

  3. 03

    Build

    Screens and logic in weekly slices, on a staging link you can click through as it grows.

  4. 04

    QA

    Devices, browsers, keyboard, screen reader, slow connections, forms and integrations end to end.

  5. 05

    Launch

    Redirects, analytics, monitoring, DNS and store submission, checked the same day.

  6. 06

    Care

    Handover guide, a training session, then updates and small changes on a plan if you want us around.

Sounds like you?

Time to rebuild if…

  • err_01Changing a headline needs a developer and a two-week wait
  • err_02Your site is slow, especially on mobile
  • err_03Forms, analytics or your CRM are half connected
  • err_04You've been burned by a dev who vanished after launch

Development FAQ

Questions about the build

Something else? Email admin@baddesign.io. The founder replies.

Which platform should we use?

Whatever your team can maintain. If marketing needs to ship pages weekly, Webflow or Framer. If you need custom logic or you're already on React, Next.js. We'll recommend one and explain why.

What's the difference between a website, a web app and a mobile app?

A website is pages people read, and your team edits the words. A web app is software people log into in a browser, so it stores data and knows who they are. A mobile app is the same kind of software, installed from the App Store or Play Store. Plenty of companies need the first two and never need the third.

Do you do front end only, or back end too?

Both. Front end is what people see, back end is the database, logins, rules and integrations behind it. If you already have a back end team, we fit into their API and stay on the front.

Can you build an app for both iOS and Android?

Yes, from one codebase with React Native, so you are not paying twice or waiting twice. We also handle store accounts, screenshots and the review process.

We have an idea but no spec. Where do we start?

A short scope round: the screens, the data, who logs in, what it connects to. You get a fixed plan and a price before anyone writes code.

Do you migrate existing sites?

Yes, including content, redirects and forms, so you don't lose traffic or leads in the move.

Who hosts the site?

You do, on your own accounts. We set it up and hand over the keys.

What happens after launch?

You get a handover guide and a short training session. If you want us around, a care plan covers updates, fixes and small changes.

Tell us what you need built.

A website, a web app, an app on a phone, or all three. Send what you have and we'll tell you what it takes, in plain numbers.