Mobile app vs. web app — which should you use?
Both run on the same account and the same backend — this isn’t a matter of picking one forever, just whichever fits the device in front of you right now.
When the native app makes more sense
An iPhone (NFC needs the native app there), or wanting a biometric app lock, or simply preferring an installed app you open with one tap.
When the web app makes more sense
A Chromebook, a shared staff desktop, or any device you don’t want to install anything on — or an Android phone in Chrome, where even NFC works without installing anything.
What works on which platform
My NFC Attendance ships as a native mobile app and as a browser-based web app on the same account and the same backend. Most capabilities match — a few depend on what the device and browser actually support, so here it is plainly rather than glossed over.
| Capability | Mobile app (iOS & Android) | Web app (browser) |
|---|---|---|
| NFC tap to mark attendance | Yes — iOS and Android | Android only, in Chrome or Edge — no browser exposes NFC to a website on iOS, Safari, Firefox, or desktop |
| QR code scanning | Yes | Yes, in any modern browser |
| Manual attendance marking | Yes | Yes |
| Bulk NFC tag writing for a class | Yes | Android only, in Chrome or Edge |
| Passwordless NFC tag login | Yes | Android only, in Chrome or Edge |
| Add pass to Apple Wallet | Yes — one tap, on iOS | Best-effort on iPhone Safari — opens a share sheet rather than a guaranteed one-tap install |
| Add pass to Google Wallet | Yes, on Android | Yes |
| Biometric app lock | Yes | Not applicable — browsers have no equivalent |
| Course, series & roster management | Yes | Yes |
| Excel import & catalog exports | Yes | Yes |
| Nothing to install | No — requires an app store install | Yes — open the URL in a browser; can also be installed as a Progressive Web App |