What is Near Field Communication (NFC)?

Near Field Communication (NFC) is a wireless technology that lets two devices exchange data when they are within a few centimeters of each other. You probably already use NFC every day — it powers contactless payments like Apple Pay and Google Pay.

NFC works at 13.56 MHz and transfers data at short range, typically 1 to 4 centimeters. This close range is a feature, not a limitation. It prevents accidental reads and makes NFC more secure than longer-range wireless technologies.

How traditional NFC tags work

A traditional NFC tag is a small chip with an antenna, often embedded in a sticker, card, or keychain. Here is the basic process:

  1. Power — The tag has no battery. When a phone (the reader) gets close, the reader’s NFC radio sends out an electromagnetic field. The tag’s antenna absorbs enough energy from that field to power up the chip.
  2. Data load — Once powered, the chip sends its stored data back to the reader through the same electromagnetic field.
  3. Action — The phone receives the data and acts on it. If the data is a URL, the phone opens a browser. If it is a phone number, it offers to dial.

With traditional NFC, the data is written directly to the tag’s chip. To change what the tag does, you need to physically reprogram it with an NFC writer app. This works for one or two tags, but it becomes impractical when you manage dozens or hundreds.

How Kitetags are different

Kitetags takes a different approach. Instead of storing your content on the tag itself, each Kitetag stores only a unique URL that points to the Kitetags cloud platform.

Here is what makes that powerful:

  • Pre-encoded at manufacturing — Every Kitetag leaves the factory with its URL already written to the chip. You never need an NFC writer app or any special hardware.
  • Cloud-managed — The URL on the tag never changes. Instead, you control what happens when that URL is opened by configuring your tag on the Kitetags platform. Change the response anytime from your dashboard.
  • No engineering needed — You set up tags through a visual web interface. No coding, no firmware, no mobile app development.

How phones, Kitetags, and the platform connect

The following diagram shows the relationship between the key technology components:

erDiagram
    SMARTPHONE ||--o{ NFC_KITETAG : "taps"
    NFC_KITETAG ||--|| KITETAGS_PLATFORM : "resolves via"
    KITETAGS_PLATFORM ||--o{ APP : "routes to"
    KITETAGS_PLATFORM ||--o{ KITETAG_GROUP : "organizes into"
    KITETAG_GROUP ||--|| KDS : "defines data with"
    KITETAG_GROUP ||--|| KI : "defines behavior with"

    NFC_KITETAG {
        string UID
        string callsign
        string encoded_URL
    }

    KITETAG_GROUP {
        string name
        string description
    }

    KDS {
        string field_name
        string field_type
        string field_value
    }

    KI {
        string app_type
        string configuration
    }

Text summary: A smartphone taps an NFC Kitetag, which resolves through the Kitetags platform. The platform organizes tags into Kitetag Groups. Each group has a Kitetag Data Structure (KDS) that defines the data fields and a Kitetag Interaction (KI) that defines the behavior. The platform routes each tap to the appropriate App, which produces the response.

What this means for you

With Kitetags, the physical tag is the simplest part of the system. All the intelligence lives in the cloud. You can:

  • Change a tag’s destination URL, vCard data, or webhook endpoint without touching the tag
  • Manage hundreds of tags from a single dashboard
  • Use built-in Apps for common actions like URL redirects, vCards, webhooks, and Zapier
  • Build custom workflows by combining Kitetag Data Structures and Kitetag Interactions

Next steps

Last updated 27 Mar 2026, 06:51 +0900 . history