NFC apps: tap instead of type

Practically every current mid-range and flagship Android phone, and iPhones from the iPhone 7 onwards. On iOS, however, what can be read in the background differs from what requires the app to be open – we check that up front for your target devices.

On Android, yes: host card emulation lets the app present itself as a card. On iOS this remains limited and conditional. If your use case depends on it, we say so before the project starts – not afterwards.

The short range alone is not security. Security comes from the scheme: AES-backed cards, keys that do not sit in the app, revocation lists and server-side verification. Treating a bare card number as an entitlement is the most common flaw we find in existing systems.

Yes. The tag carries its own data and reading it needs no network. Only the synchronisation of rights and logs runs online – we build it to survive outages and catch up afterwards.

The price depends less on NFC itself than on everything around it: the card scheme, backend, rights management and the number of edge cases. So we start small with feasibility and a prototype, and only quote the rest once the number is dependable.

Usually yes. In Flutter apps we bind the native interfaces through our own bridges, in native apps directly. The effort rarely sits in the reading itself, but in fitting it cleanly into existing flows and permissions.