Android Digital Business Card

This is a documented concept, not a finished application. The first version is Dominic’s own card: a practical reference implementation to build and test before the requirements of a future commission are frozen.

Stable destination

The NFC tag and printed QR code store one permanent HTTPS URL rather than a complete contact record. That page can change its visible details, branding, buttons, and highlighted destination without rewriting a fabricated card or reprinting the QR code.

Shared public data

One allowlisted data source should generate the mobile-first Astro page, focused VCF download, QR artwork, canonical NFC destination, and later wallet pass fields. This keeps the website, downloaded contact, physical card, and wallet representation from drifting apart while excluding private address-book data.

Product boundary

The personal implementation and a neutral client template are related but separate outputs. A handover can include Astro source, prebuilt static output, approved card data, VCF, optimized artwork, QR files, build instructions, and hosting expectations. A client’s domain or hosting operator remains responsible for provider-specific DNS and server access unless that work is explicitly part of the commission.

Google Wallet support is planned through its signed pass model. Apple Wallet is a later option once an Apple Developer membership and ongoing maintenance are justified. Physical printing, chip placement, finishing, and quality control remain fabrication work rather than a feature of the web template.