How I Built TapBoss: NFC Digital Business Cards with React and Supabase

The Challenge

• Reprints lag hiring, new domains, and campaign links. The physical card becomes a liability.
• vCard files and PDF links still need a place that is branded, editable, and fast on mobile.
• The buyer wants a product, not a static HTML page with a QR taped on.

The Solution & Architecture

This is the software side of OrlanDev’s offer: auth, profiles, and a public tap URL. NFC is the trigger; the system of record is the web app.

1. 01

   Tap / NFC

   Tag encodes a stable URL. The chip does not store the career history — the server does.

2. 02

   Profile software

   Owners edit contact, socials, and links in one place. Next tap reflects the change.

3. 03

   Public page

   Mobile-first profile the recipient actually opens — the conversion surface, not an NFC novelty.

4. 04

   Handoff

   React + Node + Supabase so the product can take payments, teams, or more card SKUs later.

The Tech Stack

• React

  Fast profile UI on the phones that receive the tap.

• Node.js

  API for profiles and updates without coupling to a page builder.

• Supabase

  Auth and data so owners can change links without a deploy.

• Tailwind CSS

  Tight, branded layout that still loads quickly on cellular.

The Results

• • A role or URL change is an edit, not a reprint.
• • Recipients get a page, not a dead PDF.
• • The same stack is a template for other “tap to a live record” products (badges, equipment tags, field IDs).

A living card: one tap, updated links, no reprint cycle.