What to Look for in a Digital Business Card (And Why Most Apps Get It Wrong)

A junior associate at an Amsterdam law firm asked me at a networking dinner in February which digital business card app she should buy. I gave her the wrong answer.

She signed up, paid, and quietly stopped using the platform six weeks later because the recipient experience on Android was a disaster. Her contacts landed on a page where the vendor's branding was larger than hers. Two months later, we sat down at a kitchen table on Prinsengracht and walked through the decision properly.

That conversation was more useful than any feature comparison chart I've read. Here it is.

Start Where Nobody Starts: The Receiving End

Forget the design interface. You'll see it ten times before launch and then almost never again. What runs hundreds of times a year — in the wild, on phones you don't control — is what happens after the tap.

Start there.

Text yourself the link to any demo card and open it on an Android device you don't normally use. Not your iPhone. A fresh browser, logged out of everything. Watch what happens:

• Does the page load in under two seconds?
• Are the contact details visible without creating an account?
• When you tap "Save contact," does your address book open — or a sign-up screen?

If you hit a registration screen, you've found what I call the save-gate: the silent killer of the category.

The Save-Gate Problem

Forty to sixty percent of recipients drop off when a digital business card requires registration before saving a contact — a pattern I've seen consistently in analytics dashboards across networking campaigns from 2022 to 2025. Some platforms specifically gate the friction-free contact-save behind their paid tier. You can't tell from the marketing copy. You only discover it after upgrading and watching your save rate climb.

The architecture is simple. Good platforms generate a .vcf file — vCard 4.0, per RFC 6350 — that any address book app on any platform can import directly, with no intermediary account. Bad platforms store your contact in their proprietary database and require recipients to create an account before accessing it. The first respects your contacts' time. The second generates sign-ups for the vendor.

Test this before you pay for anything. Count the taps from "I just opened the card" to "the contact is saved." If it's more than three taps on Android, the platform is failing the most fundamental test.

Cross-Platform Consistency

After the save-gate test, check cross-platform consistency. Send the same link via WhatsApp, via Instagram DM, via plain email, and as a direct URL in a browser. Open each in a different context — or at minimum on iOS and Android.

What to look for:
- Does the page render correctly in all contexts?
- Does your photo load in WhatsApp's link preview?
- Does the layout adapt to narrow mobile screens?
- Does the contact-save flow work from every entry point?

Most vendor demos are filmed on a clean iPhone in good light with a staged recipient. Real conditions involve WhatsApp link previews, five-year-old Samsung phones, and people with five seconds of attention. Test accordingly.

The Watermark Question

Vendor branding on your recipient page is not a trivial aesthetic detail. When your contact saves you from a page where the platform's logo outweighs yours, the association that sticks in memory is platform > person.

More practically: when that saved contact clicks through a year later and sees the vendor's brand instead of yours, it undermines the trust signal your card was supposed to create.

Check the recipient view on any platform you're considering:
- Whose branding is more prominent on the page a recipient actually sees?
- Can you remove the vendor watermark — and at what pricing tier?

On several major platforms, "remove platform branding" is the feature at the highest tier, not the lowest. That changes the effective cost considerably.

Retroactive Updates: The Criterion Everyone Misses

This is the one that non-technical buyers almost always underestimate — and regret later.

When you change jobs, update your title, get a new phone number, or add a portfolio link — what happens to the digital cards already in circulation? The QR codes you printed on materials six months ago? The link in your email signature?

Platforms fall into two clear architectural categories:

Static cards. The QR code or link points to a snapshot of your information at the time of creation. Change anything, and you need to redistribute everything. Printed materials become wrong immediately.

Dynamic cards. The QR code or link points to a permanent server-hosted URL that you control. Change your title, and every card in circulation — old and new — reflects the update instantly.

Ask this directly before buying: "If I update my job title next year, will every QR code and share link I've ever distributed automatically show the change?" A clean "yes" is the right answer. Any caveat is a red flag.

The technology behind it is simple: a permanent URL that resolves to a server-generated vCard file (RFC 6350 / vCard 4.0). The URL never changes; what's behind it does.

The Seven Criteria That Actually Matter

After running through this with clients across multiple industries, here is the framework I use now. These predict real-world card performance, not how the demo looks.

Criterion	What to Check	Pass Condition
Android receiving experience	Open on a fresh Android device	Loads in under 2 seconds; contact info visible without registration
Contact-save friction	Tap "Save contact" on Android	Address book opens in 1–2 taps, no sign-up required
Cross-platform consistency	Send via WhatsApp, email, SMS, browser	Photo loads; layout correct in all contexts
Vendor watermark	View the recipient page	Your branding equals or exceeds the platform's — or is fully removable
Retroactive updates	Change a field, check old share links	All existing links show the update immediately
Privacy policy	Read the actual terms	No silent opt-in to vendor's email list; GDPR-compliant data handling
Data portability	Find the export feature	You can export contacts and card data any time

What Doesn't Matter (Despite Vendor Emphasis)

Template gallery. You'll interact with templates during setup and rarely after. Your contacts interact with the receiving experience. Template count doesn't predict receiving quality.

The number of supported social links. Most recipients tap one or two. Whether the platform supports 50 icons or 15 is not a meaningful differentiator.

NFC chips sold by the vendor. A great NFC tap experience with a broken Android receiving page still fails at the moment that matters. Worth knowing: you can write any digital card's URL onto a cheap blank NFC tag — you don't need the vendor to sell you hardware to make NFC work.

The demo video. Filmed on iOS, clean phone, staged recipient. Not predictive of real-world performance. Ask for unedited screen recordings from a stranger's device in real conditions. Most vendors won't provide them.

Privacy and Compliance

In jurisdictions with active data enforcement — the EU, UK, California, Brazil — this matters more than most buyers assume.

Check specifically:
- Are recipients silently subscribed to the vendor's marketing list when they view your card?
- Are scan events shared with third parties for advertising?
- Can you delete all contact data on request (right to erasure under GDPR)?
- Is the vendor registered as a data processor in your jurisdiction?

Ambiguous language in the privacy policy is itself a signal. A platform that handles your contacts' data responsibly will be specific about what they collect, why, and for how long. "We may share data with trusted partners" without elaboration is not specific.

Common Buyer Mistakes

Buying based on app store reviews. Reviews are almost entirely from cardholders, not recipients. You need to evaluate the recipient experience. These are different products in practice.

Trusting the pricing page feature list at face value. "Frictionless contact save" can mean different things to different vendors. Test it — don't read about it.

Ignoring data portability. Three years from now, if you've collected 400 networking contacts on a platform that doesn't export, you don't own that network. You're renting it. Find the export function before you need it.

Testing only on iOS. Roughly half of smartphones globally run Android. iOS-only testing is the single most common evaluation mistake in this category.

Frequently Asked Questions

Should I just use Apple Wallet or Google Wallet?

You can, and both work well for their respective platforms. Apple Wallet is excellent for iOS recipients; Google Wallet covers Android. The challenge is maintaining separate passes for each ecosystem, or accepting that half your contacts get a degraded experience. If your network is genuinely platform-homogeneous, wallet passes are excellent — friction-free, offline-capable, and updatable over the air. For mixed iOS/Android audiences, a web-based receiving page that achieves one-tap contact save on both platforms is more practical.

How long does an NFC business card actually last?

Four to seven years for polycarbonate cards from reputable manufacturers. The NXP NTAG chips have no moving parts and are rated for tens of thousands of read cycles. Failure is almost always the card body cracking, not the chip.

What's vCard 4.0 and why does it matter?

RFC 6350 defines the vCard 4.0 format — a structured text file that address book apps on every platform understand natively. When a platform says it lets your contacts "save your info," the underlying mechanism is almost always a .vcf file served at a URL. Platforms that host this server-side and regenerate it dynamically are updatable. Platforms that bake the vCard at creation time are frozen.

What about platforms that have since shut down or pivoted?

It happens. Linq — once a notable name in the digital business card space — pivoted away from the market in early 2025. If you've built a significant contact collection on a platform, check regularly that it's still actively maintained. Data portability (above) is your safety net.

The Conclusion I Should Have Given Six Months Earlier

When that junior associate finally switched platforms, she chose BizBuzz Cards. Six months later, she sent an email I've since shared — with her permission — with about a dozen other clients.

Her card had accumulated 47 contact saves from firm events. Three had turned into actual referrals: a partner-track lateral candidate, a procurement contact at a multinational she'd been pursuing for two years, and a legal tech introduction that led to a panel invitation. The previous platform had produced none in twice the time.

The difference wasn't the card design. It was the architecture: no registration gate, her branding unobscured, a clean one-tap save on Android. Each card also came with a mini-site — a real, indexed web page with her name and practice area — that she genuinely owned rather than renting from the vendor. And when she wanted to reconnect with someone she'd met at a conference three months earlier, BizBuzz's AI-powered contact search let her find them by describing the conversation rather than scrolling through a list.

She wrote that she hadn't realized how much the previous platform was costing her. Not in money. In conversion.

Test the receiving end first. Everything else follows from that.

---

Alex Morrison — digital networking consultant, Amsterdam

Sources

• RFC 6350, The vCard Format Specification (vCard 4.0): https://datatracker.ietf.org/doc/html/rfc6350
• NXP NTAG 213/215/216 product page: https://www.nxp.com/products/NTAG213_215_216
• Linq platform exit coverage: https://wavecnct.com/blogs/news/best-linq-alternative
• BizBuzz Cards: https://bizbuzz.cards