KING’S DEVELOPMENT And AI

Our work

Bespoke software. Built for real businesses.

Every project here was designed and built from nothing for the business that needed it: platforms, websites, native applications and a multiplayer game. Where a client is happy to be named, we name them and link the live site. Where they are not, we describe the work and leave the name out.

Discuss your project Our services

Projects
Eight, from a business platform to a multiplayer game
Applications
Web, mobile and native, from one codebase
Every size
A single website through to an operation on one platform
  1. 01Bespoke business platform

    Bringing an entire organisation together.

    Type
    Multi-tenant SaaS platform
    Runs on
    Web, iOS and Android

    The problem

    An organisation running a complex operation on paper registers, a spreadsheet schedule and a group chat. Several different groups of people needed different things from the same information, and none of them could get at it without going through somebody else.

    What we built

    A bespoke platform bringing together the tools, information and workflows needed to manage the organisation: scheduling, attendance, capacity, billing and messaging, over one set of records. Different users have interfaces and functionality suited to their individual needs, within one connected system. Web, iOS and Android all come out of the same codebase, so there is one version to keep up to date rather than three.

    How it holds up

    Every record belongs to one organisation and must never reach another. That rule is enforced by the database itself rather than trusted to the app, so a tampered client gets nothing back. It is covered by 550 automated tests across 33 files, plus 121 assertions that check each permission twice: that the right person is let in, and that the wrong one is not.

    Key features

    • Multi-user platform
    • Role-based access control
    • Scheduling and booking
    • Customer management
    • Reporting and analytics
    • Billing and invoicing
    • Mobile and desktop support

    Redacted: every name, photograph and figure covered

    • The dashboard: four summary figures across the top, a list headed 'What needs your attention' with items tagged Urgent, Today and Review each carrying its own action, and a panel of what is happening today beside it.

      The dashboard. Not a wall of charts: a list of what actually needs doing, each row carrying the action that deals with it.

    • The attendance screen: an overall attendance figure and a count, above a list of groups each showing a percentage and a progress bar.

      Attendance. One figure for the organisation, then every group underneath it, so a problem gets found rather than reported.

    • The schedule screen: a week laid out as seven columns, each weekday holding time-slotted sessions colour-coded by type, with the current day marked Today.

      The week. Sessions are colour-coded by type and the current day is marked, because that is the question people arrive with.

    • The places screen: four summary figures, then a table showing a session at twenty of twenty places with a full bar in red, and a breakdown by weekday each with a percentage and a bar.

      Capacity. A session at twenty of twenty places turns red, and the weekday breakdown underneath shows where the room actually is.

    • The invoices screen: a list of invoices with amounts and status labels reading Overdue and Paid, with a draft invoice grouped separately from those already issued.

      Billing. Drafts sit apart from what has been issued, so nothing goes out before somebody has looked at it.

    • The same dashboard on a phone: the four figures as a two by two grid of coloured cards, the attention list below them, and a bottom navigation bar with Home, Calendar, Messages and More.

      The same system on a phone. The same records, laid out for a thumb.

  2. 02Foundry

    Smarter project planning.

    Type
    macOS application
    Runs on
    One Mac, entirely local

    The problem

    Project tools are built for teams reporting upwards, and they all have the same failure: keeping them accurate is work, so they stop being accurate, so nobody trusts the dates in them. The two questions that actually matter are what to do next and when this will be finished.

    What we built

    A Mac app holding projects, phases, milestones, decisions, blockers and logged work in a local database, which gives each project a completion range it can explain rather than a date it asserts. Built in Swift 6 on SQLite, across six modules and a test suite of seventy files.

    There is no cloud service, no account and no API key. Everything stays on the machine it was written on.

    The part that matters

    It ships its own MCP server, so an AI assistant reads and writes the same records through the same validation the app uses. The plan stays current as a side effect of the work being done, rather than as a separate job somebody has to remember. It is the clearest example we have of building AI into something useful instead of bolting a chat box onto it.

    Key features

    • Native macOS application
    • AI-assisted project planning
    • Local-first architecture
    • Intelligent forecasting
    • Integrated knowledge management

    Captured from the app running · navigation cropped to keep a client unnamed

    • A project's forecast: a completion range of 28 October to 3 November with low confidence and provisional labels, a timeline showing the likely date, then the assumptions it rests on, the risks to it, the pace it assumes and a list of things that would improve it.

      A range, not a date, with every assumption and risk behind it written out. The last column says what would make the estimate better, which is the only useful thing to do with an estimate you do not trust.

    • A project overview: scope complete at one hundred per cent with four of four milestones, the current phase, no work remaining, an estimated completion reading ready to wrap up, a blockers panel reading all clear, the linked repository and a list of recent activity.

      A project at a glance. Scope, phase, what is left, what is blocked and the repository it lives in, with the activity that produced those numbers underneath.

  3. 03Placely

    Helping students find opportunities.

    Type
    Student placement platform
    Runs on
    Web, iOS and Android

    The problem

    Finding a placement is long, mostly silent, and spread across job boards, email and whatever the school happens to use. Students lose track of where they are, and the people supervising them cannot see it either.

    What we built

    A CV builder, placement matching, company profiles, a revision planner, homework and an admin back office, with a dashboard that answers one question: what is the next thing worth doing. Sign-up is five short steps rather than one long form, because long forms get abandoned.

    The iOS and Android apps wrap the same web app, so a change ships to all three at once.

    Key features

    • Placement marketplace
    • Student dashboards
    • CV builder
    • Progress tracking
    • Employer portal
    • Administrative dashboard
    • Mobile applications

    Explore the screens

    Placely

    • Sign-up step two of five: choosing between a student and a company account, with a progress bar.

      Signing up. Five short steps with a guide, rather than one long form that gets abandoned.

    • The dashboard: a greeting, a find placements button, an XP level card and a five-stage progress tracker.

      The dashboard. Where you are in the process, and the single next thing worth doing.

    • The placements list: filterable cards showing employer, role, sector, location, hours and deadline.

      Finding a placement. Filterable listings with the details that decide it up front.

    • The achievements screen: an XP level card above earned and locked achievements grouped by stage.

      Achievements. Progress made visible, because a placement search is long and mostly silent.

  4. 04REIGN

    Training without interruptions.

    Type
    Live web app
    Runs on
    Any phone, offline

    The problem

    A gym floor is an awkward place for software. The screen locks between sets, the signal drops in a basement, and nobody is going to retype a session they have already done.

    What we built

    Everything is written to the phone first and uploaded when the connection comes back, so a dropped signal loses nothing. The rest timer keeps sounding while the app is asleep, and the screen stays awake during a set.

    Alongside the session log: a weekly plan, body tracking with trends, nutrition against targets, and a leaderboard, because turning up is the hard part.

    How it holds up

    The database decides who can see what, using security-definer functions rather than trusting the app, and 526 assertions across 17 files check that it does.

    Key features

    • Offline support
    • Workout tracking
    • Progress analytics
    • Nutrition management
    • Personal planning
    • Performance insights

    Explore the screens

    REIGN

    • The workout screen: today's session, the current exercise, set counters and suggested warm-up weights.

      The session. Set counters, warm-up weights and the last thing you lifted, all on one screen.

    • The plan screen: a weekly split with each day assigned a session type and an edit control.

      The week. Each day gets a session, and the exercises behind it are editable.

    • The body screen: a weight trend chart with seven day, thirty day and weekly changes above a check-in form.

      Body tracking. Trend chart, deltas over three windows, and a check-in that remembers last time.

    • The nutrition screen: calories remaining, macro progress bars and a quick-add list of saved meals.

      Nutrition. Macros against targets, and one tap to log a meal you eat every week.

    • The board screen: a weekly leaderboard and a six-month grid of training days.

      The board. A leaderboard between two people, and six months of turning up at a glance.

  5. 05Krosshair

    High-performance multiplayer.

    Type
    Multiplayer game
    Runs on
    The browser, and Roblox
    Status
    In development

    The problem

    One life per round, friends on different connections. If the server does not decide every hit, the player with the better connection wins, and everyone can feel it.

    What we built

    A round-based tactical shooter where one Node process serves the page and runs the match, owning every hit, health point and credit. Hit zones, damage falloff, armour and helmets, wall penetration that depends on the material, and lag rewind, so a shot is judged against what the shooter actually saw rather than where the target has since moved to.

    Nothing is downloaded: every model, texture and sound is generated in code. Players sign in with Discord, or stay a guest with a callsign, and their progress follows them.

    Then again, on Roblox

    The same game rebuilt as a Roblox experience, sharing no servers or accounts but sharing every number: weapons, economy, round rules, twelve arenas, materials and lighting are exported from the browser game's own code, so the two play identically.

    Explore the screens

    Captured from the game running

    • The game's menu: seven numbered modes including quick play, battle royale, ranked and unranked team sizes, an arcade mode, a bot match and a practice range, beside a rendered player model, a sign-in panel and a guest callsign field.

      Seven modes, each explained in a line. Signing in is optional: a guest gets the game, an account gets to keep what they earn.

    • In the practice range: a first-person view down a bolt-action sniper rifle at distance-marked targets, with health, armour and credits in one corner, the weapon and its ammunition in another, and a checklist of range drills down the side.

      The practice range, where the drills teach the controls rather than a wall of text. The readout top right is the real frame time.

  6. 06Notchly

    Reimagining an existing product.

    Type
    macOS application
    Built on
    An open-source notch app

    The problem

    An open-source app for the MacBook notch that was genuinely good had grown into an everything-app: a terminal, clipboard history, system stats, notes, a file shelf, an extension system. The useful parts were buried in the parts nobody wanted.

    What we built

    A fork cut back to a notch app and rebuilt around its own design language. Fifteen subsystems were removed one at a time, with the build and the tests kept green after each, which is the only way to take a large codebase apart without discovering a month later what depended on what.

    Then the additions: a hub with a context-aware chip row, time-synced lyrics with an on-disk cache, timer and stopwatch live activities, battery detail down to charger wattage and cycle count, a tray for text and files, and background work gated on display sleep and Low Power Mode. Settings, the menu and onboarding were rebuilt from scratch.

    Why it is here

    Most software work is not a blank page. This is what it looks like to read, understand and reshape 285 files of somebody else's SwiftUI and AppKit, which is the same job as being handed a system nobody has touched for two years and asked to make it do something new.

  7. 07WERM

    Building trust through design.

    Type
    Website, live
    Runs on
    A static build

    The problem

    Water & Environmental Resource Management trace misconnected drainage for water companies, property by property. Most people arriving at their site are not buyers: they are householders who have just had a letter and want to understand who has contacted them and why.

    What we built

    A site that answers the householder's questions in order: why you were contacted, what a visit involves and how to confirm a caller is genuine, before anything about credentials.

    It ships as a static build, so there is no CMS to patch and no server to keep secure, and it loads on a phone in a driveway.

    Visit WERM Explore the screens

    WERM

    • The WERM home page: the headline 'Drainage and misconnection investigation specialists', a paragraph of background, a photograph of the office entrance, and two buttons offering an explanation or a phone number.

      The home page. Who they are and why you might have heard from them, above the fold.

    • A section headed 'Why we've been in touch, and what happens next', with three numbered steps beside a panel headed 'Check it's really us' listing ways to verify a caller.

      The reason most visitors arrive. Three numbered steps, and a panel on how to verify the caller before letting anyone in.

    • The contact page: office address in Romford, a telephone number and an email address.

      Contact. A phone number and an address, because that is what someone checking you are real wants.

    • The same home page on a phone, with the navigation collapsed and the headline and photograph stacked.

      On a phone, where most of these visitors are reading it.

  8. 08WERM field application

    Digital tools for teams in the field.

    Type
    Field and office application
    Runs on
    A phone on site, a desktop in the office
    Status
    In development

    The problem

    Every job starts with a risk assessment and every van needs a monthly equipment check. On a street in the rain, with the pad in the cab, those get done from memory and written up later, which is exactly when the detail goes missing. The forms are not optional: they are the code of practice.

    What we are building

    A phone app for the people doing the work and a desktop back office for the people who need the records. A risk assessment is ten questions and a timed vehicle count, and it comes out as the company's own signed form rather than a new format somebody has to accept.

    The monthly van check is fifty-one items across six compartments, done by swiping. Anything worn, damaged or missing is flagged with a count and a spoken note, and the flag follows the van rather than sitting in a photo on somebody's phone.

    The detail that matters

    The traffic control options carry the page numbers of the code of practice they come from, and the vehicle count enforces the limits that code sets, counting down three minutes while you tally cars and HGVs. The rules live in the software rather than in somebody's memory, which is the whole reason to build the thing rather than print the form again.

    Where it has got to

    In development, with four roles to sign in as so the client can try it as an operative, a team leader, an H&S coordinator and the office. Working with no signal and uploading to the office are specified and not built yet, and the app says so in its own settings instead of pretending otherwise.

    Explore the screens

    In development, captured from the running app

    • The home screen: the day and the van's registration, a card showing sunrise, sunset and weather, then four actions for risk assessment, incident report, van mileage and the weekly health and safety check, above the monthly van check's progress.

      The day, and the four things that might need doing in it. Light and weather are there because works after dark need a different conversation.

    • The van check: an illustration of the back of a van with six labelled compartments for uniform, tools, PPE, van kit, traffic equipment and hygiene, none checked yet, above a counter reading zero of fifty-one.

      Fifty-one items, drawn as the van they are actually in, so you check the compartment in front of you rather than hunting down a list.

    • A sheet for flagging an item: a quantity stepper, four condition buttons reading good, worn, damaged and missing with damaged selected, and a note field with a button to dictate it.

      Flagging something takes one tap and a spoken note. Typing on a phone in gloves is why paper checks get ticked without looking.

    • The van check part-way through: forty-two of fifty-one done with nine left, one flag raised, and the flagged item named underneath as crow bars in the tool bag, damaged.

      Progress by compartment, and the flag carried to the top. The check is resumable, because it is rarely done in one go.

    • Question six of the risk assessment, asking how traffic is controlled, with four illustrated options showing low risk works, works between parked cars, two way traffic and give and take, each citing a page of the code of practice.

      Each option is drawn and carries the page of the code of practice it comes from. The knowledge is in the app, not in the person.

    • The vehicle count: a three minute countdown ring, a counter for cars reading seventeen of a maximum twenty, and a counter for HGVs and buses reading three of twenty, each with an add button and an undo.

      The count the code requires, timed, with its limits enforced as you tally. Go over and the method is no longer allowed.

    • The check and sign screen: a green traffic light reading good to go, above a table of the answers including project, manhole reference, location, road category, speed limit, duration and traffic control.

      Everything answered, read back in one screen, with a plain verdict at the top before anybody signs.

    • The saved assessment: a confirmation that it has been signed and saved, above a preview of the company's own short duration street works risk assessment form, filled in and stamped as signed.

      Out comes the company's own form, filled in and signed. Nobody has to accept a new document, and the audit trail is the one they already keep.

    • The new form screen listing five forms: risk assessment, incident report, van check, van mileage and the weekly health and safety checklist.

      The five forms the work actually generates, each the paper version shortened to what a phone can ask.

Why clients choose us

The same studio does the thinking and the building.

Design and engineering are not handed between two companies here, so what gets drawn is what gets built, and the detail survives the journey from the first sketch to the thing people use every day.

  • Design and engineering together. One studio holds both, so nothing is lost in translation.
  • Built around the business. The software follows how the work already happens, rather than the other way round.
  • Designed, not assembled. Every screen is designed, not assembled from a template.
  • Projects of every size. From a single website to an entire operation on one platform.
  • Still here afterwards. Software is looked after once it is live, not handed over and forgotten.

Let’s build your next project.

Tell us what you need and we will tell you how we would build it.

Discuss your project