BoviNest: Building a Production RFID Workflow for Mobile One of the most interesting parts of bui...BoviNest: Building a Production RFID Workflow for Mobile One of the most interesting parts of bui...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Ing. Gael de Nicodemo's avatar
Gitbon-Labs logo
Ing. Gael de Nicodemo Serrano Hernandez
pro
• Aug 26
BoviNest: Building a Production RFID Workflow for Mobile
One of the most interesting parts of building BoviNest has been integrating physical RFID hardware into a mobile application without making the hardware feel like a separate system.
The goal was simple:
Scan an animal → identify it immediately → continue with the correct workflow.
The implementation was not quite as simple.
>> The Core Architecture
Each animal has two important identifiers:
- A stable UUID that represents the animal record.
- A 15-digit FDX-B RFID identifier that can be associated with that animal.
This distinction is important because the RFID tag is an attribute of the animal, while the UUID represents the actual database record.
That allows the system to preserve the animal's clinical and operational history even when its RFID relationship changes.
>> Three Ways to Enter an RFID
The application supports a common processing pipeline regardless of how the RFID arrives.
1. HID RFID Readers
Many physical readers behave like a keyboard.
BoviNest captures the incoming digit sequence, recognizes a valid 15-digit RFID, and routes it into the same scanner workflow used by other input methods.
This was especially useful because it avoids requiring a dedicated Bluetooth workflow for compatible HID readers.
2. BLE
The application also contains a BLE integration layer capable of receiving RFID data from compatible hardware.
The BLE path is currently prepared for future hardware workflows while the production configuration prioritizes the HID approach.
3. Manual Input
Users can also enter an RFID manually.
This is important for field operations because hardware should never become a single point of failure.
All three paths ultimately converge into the same application flow.
>> The Important Part: Normalization
A hardware reader can send the same RFID several times in a fraction of a second.
So the application doesn't simply react to every incoming value.
The central scanner pipeline:
- Receives the identifier
- Validates the 15-digit format
- Debounces duplicate reads
- Resolves the animal
- Opens the appropriate workflow
There is also an important UX rule:
If the user is actively typing into another field, the global RFID listener must not consume those digits.
That prevents a hardware integration from interfering with completely unrelated forms such as weights, capacities, or other numeric inputs.
Small detail, but extremely important in a real field application.
>> Online + Offline
BoviNest is designed for ranch environments where connectivity cannot be assumed.
When online, RFID resolution uses the backend.
When offline, the application can resolve previously synchronized animals from its local cache.
The RFID workflow therefore remains useful even when the ranch temporarily loses connectivity.
>> RFID Is Not the Identity of the Animal
Another important business rule is handling animals imported without RFID.
Those records can initially use a temporary visual identifier.
When the physical RFID is eventually assigned, the system links the RFID to the existing animal record instead of creating a duplicate animal.
This preserves:
- Clinical history
- Movements
- Weight records
- Events
- Existing relationships
The RFID relationship is also audited so changes remain traceable.
>> Hardware → Mobile → Backend
The final architecture looks roughly like this:
RFID Reader ↓ HID / BLE / Manual Input ↓ Central RFID Pipeline ↓ Validation + Debounce ↓ Scanner Workflow ↓ Local Cache / Backend ↓ Animal Record ↓ Clinical / Operational Actions
The important design decision was not simply making the reader work.
It was making the hardware integration transparent to the rest of the application.
The user scans an animal and BoviNest takes care of the rest.
That is the kind of hardware/software integration I enjoy building: physical devices feeding into a reliable software workflow without forcing the user to think about the complexity underneath.
>> Tech Stack
- Flutter
- Dart
- Riverpod
- GoRouter
- Supabase
- PostgreSQL
- FastAPI
- BLE
- Bluetooth HID
- SQLite
- Firebase
Building software for the field means designing for unreliable connectivity, imperfect hardware, and real users—not just ideal conditions.
® BoviNest is a product of GitbonNest.
FlutterSupabasesaasapp
Post image
Post image
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started