← All work
Case study

Linkoo

A smart physical card as an identity layer for professional networking, with one serverless backend serving the website, the mobile app and the back office.

Visit the live site →
Role
Co-founder & Tech Lead
Company
Linkoo
When
Jul 2026 — ongoing
Stack
Supabase · TypeScript Edge Functions
1 → 3one backend, three client apps
NFC + QRcard-to-profile binding
4people on the team
The ecosystem · one backend
Three clients
  1. WebsiteSales, ordering, public card URLs
  2. Mobile appActivation, profile, networking, stats
  3. Back officeDesign queue, shipments, inventory
One backend
  1. Unified authOne identity for every app
  2. TypeScript Edge FunctionsServerless on Supabase
Card binding
  1. NFC + QRThe physical card
  2. Activation-bound profileDurable

The problem

Linkoo is a smart physical card that acts as an identity layer for professional networking. A physical card has to connect to a profile that outlives any single tap, and three different products need to agree on who that person is.

What I built

One backend, three clients

A single serverless Supabase backend, written as TypeScript Edge Functions with unified auth, serves the website (sales, ordering, public card URLs), the mobile app (activation, profile, networking, stats) and the back-office dashboard.

NFC and QR card binding

A binding flow links each physical card to a durable, activation-bound profile, over NFC or QR.

A back-office operations platform

The back office handles design-queue triage, shipment tracking with audit logs, and catalog and inventory.

The calls

Call 1 · Architecture

One backend for every app.

Three clients on three backends would mean three versions of the truth. One serverless backend with unified auth keeps identity and card state in one place.

Call 2 · Identity

Bind the card to a profile at activation.

The card is physical and permanent, so the profile it points to has to be durable. Binding at activation ties the two together.