Work · Case study
NFC Digital Business Card Platform
Jema Cards · Independent project · live product
A web platform where a tap of an NFC card, or a scan of its QR code, opens the owner's digital profile on any phone, with no app to install.
Visit Jema CardsThe problem
Paper business cards run out, go out of date and tell you nothing about who used them. Professionals need a way to share up-to-date contact details instantly and see whether it worked.
My role
I designed and developed the platform independently: the public profile pages, the account dashboard, the data model and the integrations.
What it does
- Tap or scan to share
- Each card carries an NFC chip and a QR code that open the owner's profile on iPhone and Android.
- Profile builder
- A choice of profile templates, unlimited links on paid plans and a one-tap “Save contact” button.
- Lead capture
- Visitors can leave their details; owners export their leads as CSV.
- Analytics
- Owners see taps, scans and profile views over time.
- Card management
- A lost card can be switched off from the dashboard and re-linked.
- QR Code Studio
- Generates downloadable QR codes in PNG and SVG.
- Premium tools
- Online bookings with reminders, payment links and deposits, a small online store, and custom domains.
Technologies
- Next.js
- React
- TypeScript
- MariaDB / MySQL
- Prisma ORM
- Clerk (authentication)
- Stripe (payments)
- Resend (email)
- Cloudinary (image uploads)
- Zod (validation)
- Recharts (analytics charts)
- Vercel (hosting and scheduled jobs)
Challenges and solutions
Custom domains
Customers can serve their profile from their own domain. The platform checks DNS records to prove they own the domain and that it points to the service, then re-checks on a schedule and activates it only when both pass.
Plan-based features
Free and paid plans unlock different features and link limits. One gating module decides access on the server, so a limit can't be bypassed from the browser.
Analytics with privacy in mind
Taps, scans, views and link clicks are recorded on the server, then summarised by a nightly job. Visitor IP addresses are cleared on a schedule and old raw data is purged.
Keeping accounts and billing in sync
Sign-ups and subscription changes arrive as signed webhooks from the authentication and payment providers, which the platform verifies before updating its own records.
What it demonstrates
- Turning a product idea into requirements, a data model and a working system
- User accounts, access control and plan-based feature limits
- Event tracking and reporting (taps, scans and views)
- Payments and subscription billing through a third-party provider
- Linking physical hardware (NFC cards) to user accounts
- Deploying and maintaining a live application
What I learned
Building a complete product alone taught me to think beyond the feature in front of me: how data is modelled, what happens when an outside service fails, and how to keep a live system reliable for the people using it.