Get in touch
Back to products

From our studio · Case study

NFC & QR Utility

We built the NFC tool we kept reaching for. Then we made it simple enough for anyone.

A free app for Android and iOS that reads, writes and inspects NFC tags, from a link on a sticker to the raw memory of a MIFARE card. Designed and built in-house by Xerxes.

Platform
Android & iOS
Focus
NFC tags
Built with
React Native
Launched
October 2026
Price
Free
Built by
Xerxes, design & engineering

01Overview

Every NFC task, one tap from home.

The app reads and writes NFC tags, digs into their raw memory when you need it, and keeps a history of everything you've scanned. It all starts from one dashboard, where each task has its own clearly labelled tile.

NFC is the point of the app. It also scans and creates QR codes, because people who work with tags usually work with codes too, but that's a side door, not the front one.

ReadSee what a tag holds
WritePut what you need on it

02Why we built it

It started as our own toolbox.

NFC kept coming up in our client work, and so did the same three jobs. Instead of switching between tools for each one, we built a single app that does all three properly.

Test

Check a tag during a project. Is it readable, what does it hold, did the last write work?

Write

Put a link, text, contact card or Wi-Fi details on a tag, quickly and reliably.

Inspect

Pick up an unknown tag and see exactly what it is and what is stored on it.

03The principle

Tap. Connect. Stay ahead.

Every action should be easy to recognise, and every result should be clear before you act on it.

  1. TapHold the phone to a tag.
  2. ConnectSee what it is and what it holds, in plain words.
  3. Stay aheadWrite, edit or protect it, knowing what will happen.

04Goals

Four needs the app is built around.

Each card links to the chapter that shows how the app meets it.

05Approach

We started with a question, not a feature list.

How might the app help people find the right NFC action quickly, understand the result, and write to a tag with confidence?The design question

Three kinds of people pick up an NFC app, and the same screen has to work for all of them.

Everyday users

They tap a tag and want to know what it is.

People who write tags

Links on product stickers, contact cards, Wi-Fi details for guests.

Technical users

Developers, installers and testers who need the raw memory. People like us.

What the research says

Fewer choices, faster decisions.

The time it takes to choose grows with the number of options in front of you.1

NFC tools and QR tools sit in two short rows, not one long list.
Hide the rare, not the important.

Moving advanced features to a secondary screen makes an app easier to learn and less error-prone.2

Expert tools live behind a single Advanced tile.
Say what is happening.

People need timely feedback on what the system is doing, and protection from mistakes they can't undo.3

Status before every write, and a warning before anything permanent.

06What it reads

Four tag families, one app.

Most NFC apps stop at the standard format. Ours goes down to the chip, because that's where testing and inspecting actually happen.

Standard formatNDEF

The format most tags use for links, text and contacts.

Read and write records.
Stickers & cardsNTAG / Ultralight

The small, low-cost chips inside most NFC stickers, keyrings and cards.

Read, write, inspect in detail, erase and lock.
Access cardsMIFARE Classic

Common in older access cards and transport tickets.

Dump every sector and write individual blocks.Android only
Smart cardsISO-DEP

Smart cards that talk in raw commands rather than records.

Send commands from the APDU console.

Android and iPhone aren't equal here. Android gives apps deeper access to NFC hardware. Everyday reading and writing works on both, but some low-level tools are Android-only, and the app says so on screen instead of failing silently.

07How it evolved

From our own toolbox to both stores in under a month.

We already knew the problem from the inside. That made the scope easy to set, and the hard decision easy to spot.

  1. 2026 · The need

    Testing, writing, inspecting

    NFC kept coming up in client projects. We were checking, writing and inspecting tags with whatever tools were to hand, so we built the one we wanted.

  2. The hard call

    Expert tools for everyone?

    Memory dumps and raw block writes are expert territory, and they can do damage. We kept them, but one tap further in, behind a single Advanced tile, with permanent actions clearly marked.2

  3. The build

    One codebase, history that follows you

    React Native gives one codebase for Android and iOS. Sign in with Google and your tag history is saved to the cloud with Firebase, so it follows you to a new phone. Or carry on as a guest.

    React NativeFirebaseGoogle sign-in
  4. October 2026 · Live

    On both stores

    Under a month from first screen to launch, on the App Store and Google Play.

08Read a tag

2Answers goal 2

See what it is before you do anything.

Tap Scan Tag and hold the phone to a tag. Everything the app learns is laid out in plain view, and nothing happens until you choose.

  1. 1
    A clear confirmation

    “Tag read”, with one button to scan the next one.

  2. 2
    What the chip is

    Its unique ID, the technologies it speaks, its capacity and whether it can be written.

  3. 3
    What it holds

    Each NDEF record with its type, so you know a link is a link before you go near it. A blank tag says so, and points to the Advanced tools.

  4. 4
    Your next move

    Save the read to the cloud, or share the full dump with a colleague.

09Write a tag

3Answers goal 3

Five kinds of record, one clear outcome.

  1. 01

    Pick what goes on the tag

    Text, a link, Wi-Fi details, a contact card, or a custom record.

  2. 02

    Fill it in

    One field per kind of record, with a live status underneath. You see “ready to write” before you touch the tag.

  3. 03

    Hold it to the tag

    Write to tag stays disabled until there's something to write, so you can't send an empty record by accident.

  4. 04

    Format, erase or lock

    Housekeeping sits below the main action. Lock is in red, because it can't be undone.

Locking is permanent, so the app asks first. A locked tag can never be written again, so the action is marked in red and confirmed before it runs.3

10Advanced

Expert tools, one tap further in.

This was the hardest call in the project. Raw memory tools are what made the app useful to us, and they're exactly what can confuse or harm a tag in the wrong hands. So they're all here, but in one place, with plain explanations and no surprises.

MIFARE Classic · AndroidDump every sector

Reads each sector using the common factory keys. Sectors protected by a custom key are reported as locked rather than breaking the dump. You can also write a single 16-byte block.

NTAG / UltralightInspect in detail

A closer look at the chips found in most stickers and cards.

ISO-DEPAPDU console

Send raw commands to smart cards and read the responses.

The app explains what each tool does before you run it.

11The home screen

1Answers goal 1

One dashboard, read in a glance.

The home screen is where the “anyone can use it” promise is kept. Six tiles, two rows, every one labelled twice.

  1. 1
    A featured banner

    Write & Share leads, with more behind the carousel dots.

  2. 2
    The NFC row

    Scan Tag, Write Tag, Advanced: basic to expert, left to right.

  3. 3
    The second row

    Scan QR, Create QR and Tag History.

  4. 4
    Recent activity

    Your last scans, one tap from the full result. When it's empty, it tells you which tile to tap first.

  5. 5
    Four tabs

    Home, Scan, Write and Settings, with the active tab in orange.

Lead with the core actionNFC gets the top row and the banner.
Group by purposeNFC tools together, QR and history together.
Label everything twiceA name and a short description on every tile.
One accent colourOrange marks what you can tap, nothing else.
Teach from the empty stateNo blank lists: it tells you what to do first.

Answers goal 4 · Tag History

Every tag you've touched, filtered your way.

Scans and writes are kept together, with filters for each and the key facts on every row: UID, chip type, whether it held NDEF data, and when. Signed in, the history follows you to a new phone.

12Also does QR

Also does QR.

Scan a code with the camera, or create your own from text, a link, Wi-Fi details or a phone number, then save or share it. Same app, same simple layout.

Scan QRCreate QRSave to galleryShare

13Why it makes sense

Why this shape works.

  1. 1
    Fewer choices on screen means faster choices.

    Two short, grouped rows beat one long list.1 That's the dashboard.

  2. 2
    Expert tools stay safe when they're one step further in.

    Beginners never trip over them; experts are one tap away.2 That's the Advanced tile.

  3. 3
    Trust comes from honest feedback.

    Show what a tag holds, show the status before a write, and warn before anything permanent.3 That's the read, write and lock flows.

Simple jobs up front, expert tools one tap in, and no surprises. That's why it works for a first-time user, and for us.

14What we measure

Live now. Here's what we're watching.

The app has only just launched, so there are no results to report yet, and we won't invent any. These are the signals we track from day one.

Tracking since launch · October 2026
— —First scan completed

Can a new user read a tag without help?

— —Write success rate

Do writes finish, and on which chips do they fail?

— —Recovery after a failed write

Do people succeed on the second try?

— —Advanced use

How many people go beyond scan and write?

— —History revisits

Do people come back to past tags?

— —Crash-free users

Is the build solid across devices and NFC chipsets?

Next: testing permission, empty and unreadable-tag states on a wider range of real devices and chips.

15Try it

Try it, or build yours with us.

NFC & QR Utility is free on Android and iOS. If your product needs NFC, whether that's tags, cards or a custom app, the team that built this one can help.

Sources

  1. Hick, W. E. (1952). On the rate of gain of information. Quarterly Journal of Experimental Psychology, 4(1), 11–26.
  2. Nielsen, J. (2006). Progressive Disclosure. Nielsen Norman Group. NN/g
  3. Nielsen, J. (1994). 10 Usability Heuristics for User Interface Design: visibility of system status; error prevention. Nielsen Norman Group. Summary

Research is cited to explain design decisions, not as proof of this app's results. App screens show sample data.