Skip to content

Near Field

Utility / Mobile

Android alarm clock that only dismisses when you tap a registered NFC tag - Flutter UI over a native Kotlin alarm engine via Pigeon.

Near Field

In progress

An Android-only Flutter alarm clock that can only be dismissed by tapping a registered NFC tag. Flutter owns alarm and tag configuration; native Android owns persistence, exact scheduling, reboot recovery, and the full-screen ringing flow.

Background

The point of an alarm is to get you out of bed - but a swipe-to-dismiss alarm is too easy to beat half-asleep. Near Field forces you to physically walk to a registered NFC tag and tap it to stop the alarm. That requirement pushed the hard parts into native Android: exact scheduling that survives deep sleep and reboot, a full-screen ringing flow over the lock screen, and tag validation. Flutter handles configuration while a typed Pigeon bridge carries the contract between Dart and Kotlin. The app deliberately skips a state-management package - constructor injection and ListenableBuilder are enough for its small state surface.

What it has to get right

Getting an alarm to fire after deep sleep and reboot, appear over the lock screen, and dismiss only on a registered NFC tag - across the Flutter and Android boundary and OEM battery-optimisation policies.

Solution

Split the app so Android owns alarm lifecycle, exact scheduling, reboot recovery, and the full-screen ringing flow, while Flutter owns configuration - connected by a typed Pigeon bridge. Tag dismissal validates registered NTAG215 tags and resets progress after snooze.

Tech Stack

FlutterDartKotlinAndroidNFCPigeon

Related Service

Near Field pushes alarm scheduling, reboot recovery, and the lock-screen flow into native Android behind a typed Pigeon bridge. When a mobile app needs a platform capability the framework will not give you, this is that work.

See Offline-First & Field Applications

Project Profile

2026
Mobile Developer
Ongoing

Evidence

Dismissal
Tap of a registered NTAG215 tag
Native bridge
Pigeon between Dart and Kotlin
Scheduling
Exact alarms re-registered after reboot
No label
An implementation fact: this exists in the system.

Interested in building something similar?

Get in touch