TNB
cf1e09e1c4
Update product naming in docs, marketing, architecture, use cases, and capabilities materials. Rename related notes, screenshot folder, and marketing image filenames. Keep git/repo identifiers (e.g. tallyflow-iot) and generic industry IoT language unchanged.
33 lines
1.1 KiB
Markdown
33 lines
1.1 KiB
Markdown
# TallyFlow Edge Review (repo: tallyflow-iot)
|
|
|
|
**Tech Stack:** Rust (Cargo workspace) + Leptos (web UI)
|
|
|
|
## Structure
|
|
- `core/`: Main service/library
|
|
- RFID drivers (Impinj, Zebra, ATID ATF862 / Invengo XC-RF861 — same reader rebranded)
|
|
- Barcode support (Zebra, SNAPI)
|
|
- REST API v1
|
|
- Real-time tag streaming
|
|
- Reader config/control
|
|
- Runs as an always-on Windows or Linux service
|
|
- `web/`: Leptos CSR web interface
|
|
- Reader health monitoring
|
|
- Live tag streaming with filtering
|
|
- Start/stop controls
|
|
- Imports types directly from `core` (no duplication)
|
|
|
|
## Key Capabilities
|
|
- Hardware abstraction for multiple RFID vendors
|
|
- Real-time data pipeline from readers → REST → web UI
|
|
- Designed for always-on Edge deployment
|
|
- Strong documentation (REST_API.md, LIBRARY.md, etc.)
|
|
|
|
## Relevance to TallyFlow Platform
|
|
- Primary ingestion layer for RFID/Edge data
|
|
- Feeds the web app, reporting, and exception systems
|
|
- Complements tallyflow-web (which consumes the data)
|
|
|
|
## Next Steps for Review
|
|
- Inspect `core/src/` for reader driver implementations
|
|
- Review REST API endpoints in REST_API.md
|
|
- Check web/ Leptos components for UI patterns |