Adrien LacourpailleFull-stack developer

By day, I am the sole developer of a multi-screen platform in production. By night, I build apps born from a real need.

Portrait of Adrien Lacourpaille

Open to workNantes

Projects

Each one solves a different problem: realtime, offline, public data. Open one for the details.

  • A shelf of party games turned into a made-to-measure evening. The host lines it up game after game from a console, everyone plays on their phone, and a wall on the TV keeps the board, the teams and the score from one game to the next.

    • One server, one WebSocket to every screen.
    • The server stamps every buzz: the fastest hand wins, not the fastest clock.
    • Tested end to end: real sockets, Playwright journeys across two screens.
  • How French deputies actually vote, vote by vote. Every public vote of the Assemblée nationale, explained in plain French for readers who never followed a session, each figure traced back to the official record.

    • No server and no database: a nightly job asks the open data what changed, and rebuilds only that.
    • About 750 pages prerendered by the very loaders the browser runs.
    • Over 8,000 votes split to fit the host’s file budget.
  • A live scoreboard for sports clubs running several tables at once. Four screens in the browser — the big screen, the umpire console, the organiser console and the spectator view — share one Durable Object per event on Cloudflare’s free tier, with nothing to install.

    • One Durable Object per event keeps the scoring and fans it out over WebSocket.
    • Points scored offline wait in a queue and resend on reconnect.
    • Score, server and timings all derive from the events, so a mistake is fixed live.
  • Hono on Cloudflare Workers, D1 and Core Web Vitals, with a public dashboard. A row holds a path, a referrer host, a country, a locale, a theme and a device class, and there is no consent banner because there is nothing to consent to.

    • No cookie, no IP, no user agent and no fingerprint stored.
    • tracker.js weighs under 1 kB gzipped and follows single-page navigation.
    • Four sites send their visits; one Worker writes one row.
  • A bodyweight training programme drawn as a gymnastics manual, one plate per movement. It guides a thirty-minute session, keeps a journal and draws the progress curves — installable, offline, with reminders, and with every number kept on the device.

    • Installable and fully offline, with a hand-written service worker.
    • Reminders without a server, and a screen that says plainly what this browser can do.
    • Every number stays on the device; a JSON backup carries it elsewhere.
  • Small solo puzzle and card games, printed as a puzzle book, without the ads of the apps that usually carry them. Every level is generated on the phone and proved solvable before it is shown, and the whole app installs and runs offline.

    • Every level is checked by a solver before it is shown: no guess, no unwinnable deal.
    • The daily puzzle is the same on every phone, with no server.
    • Installable and fully offline, saves kept on the device.
  • A family tree the whole family keeps up to date together, made for a father who kept his in an old desktop program and reprinted it after every birth or separation. A shared link replaces the reprint: relatives fix the tree from their phones, every change can be undone, and the paper version prints with a QR code back to the live one.

    • A link, not an account: the whole family edits one tree from their phones.
    • Nothing is ever lost: every edit can be undone, any past state restored.
    • Prints on paper with a QR code back to the live tree.
  • A list a group fills together and one person carries out. Colleagues add their lunch order, a household its groceries; whoever goes ticks the lines off on a phone while the others watch them go, live. It is written on a market-stall slate, each line signed in its author’s chalk, and a second kind of list keeps a wishlist’s reservations from its owner.

    • A link, not an account: whoever has it adds, ticks and rewrites.
    • One Durable Object per list, every change on every open screen at once.
    • A wishlist hides from its owner who reserved what, on the server.

The packages underneath

11 small TypeScript packages published on npm, each lifted out of a project once a second one needed it. Every app above installs them, down to its compiler and linter settings:

About

I did not come in through a school. I spent years in logistics, between a stockroom and a supermarket at 5 a.m., before a remote course in 2021.

Since 2023 I have been the sole developer of a multi-screen platform in production. I care about sound architecture, from monorepos to APIs typed end to end, about accessibility and tests, and I keep my projects on the latest versions of their ecosystem.

Off the clock: cinema, and table tennis.

The whole route

Your team, perhaps?

I am looking for my next job. Write to me, or take the CV: a designed one, and a plain one for applicant tracking systems.