tblumer/obsidian
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: TallyFlow Scout marketing + Edge/Print/Capture feature refresh

Browse Source 
Review tallyflow-assets-iot (TallyFlow Scout v0.5.3): Collect, Verify,
Locate with Edge remote reader / offline CSV locate. Clarify Scout does
not replace Core Assets. Refresh Edge, Print parent-container and multi-
unit identity notes, Capture share/offline/barcode notes, architecture,
use cases, capabilities, and website drafts after src/ repo pulls.
This commit is contained in:
TNB
2026-07-27 15:59:32 -04:00
parent cf1e09e1c4
commit 8f4ed8a306
23 changed files with 292 additions and 151 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TallyFlow/Marketing/Product Strategy/TallyFlow Assets for Edge.md
-59
View File
@@ -1,59 +0,0 @@
# TallyFlow Assets for Edge
**Status:** New component (v0.1.0+1)
**Primary Mobile App:** `tallyflow_mobile` remains the main TallyFlow Assets experience
**Role:** Companion / specialized app for Edge remote reader workflows
## Overview
TallyFlow Assets for Edge is a Flutter-based mobile and desktop application that submits barcode and RFID tag reads directly to the TallyFlow Edge service using the remote reader API.
It is designed for scenarios where tag data needs to be delivered to a local or on-premise TallyFlow Edge instance rather than going through the main TallyFlow Core mobile app.
## Key Positioning
- **Complementary to `tallyflow_mobile`** — Not a replacement. `tallyflow_mobile` remains the primary app for general asset capture, enrollment, and mobile workflows.
- **Edge-focused** — Optimized for pushing reads to the TallyFlow Edge remote reader endpoint.
- **Hardware + Simulation** — Full hardware scanner support on Android; simulation mode on desktop for testing and demo purposes.
## Target Use Cases
- Fixed or semi-fixed Edge reader workflows where a mobile device acts as a remote reader
- Environments with local TallyFlow Edge deployments (on-prem or edge)
- Testing and validation of remote reader configurations
- Desktop-based simulation and automation of tag submissions during development or demos
## Core Features
- Hardware barcode and RFID scanning on Android (via `flutter_hardware_scanner`)
- Camera barcode fallback using ML Kit
- Barcode / RFID mode switching
- Local scan list with send status and retry
- Manual or automatic submission to TallyFlow Edge
- Edge service health monitoring with offline banner
- Desktop simulator with JSON tag group loading and automation
## Technical Notes
- Connects to TallyFlow Edge remote reader endpoints (`/reader/barcode` and `/reader/rfid`)
- Requires configuration of Base URL, Remote Reader Name, and optional API key
- Android builds require vendor AAR files for hardware scanner support
- Desktop platforms always run in simulation mode
## Marketing Angle
- Positions TallyFlow as having flexible ingestion paths (mobile app + dedicated Edge remote reader app)
- Supports both field mobility (`tallyflow_mobile`) and Edge integration scenarios
- Simulation mode lowers the barrier for prospects and partners to test Edge connectivity without hardware
## Related Components
- `tallyflow-iot` (backend service; **product name: TallyFlow Edge**)
- `tallyflow_mobile` (primary mobile app)
- `flutter_hardware_scanner` (shared scanning library)
## Next Steps / Open Questions
- How is this app discovered / distributed to customers?
- Is there overlap with existing remote reader support in `tallyflow_mobile`?
- Should this app eventually be merged, or does it serve a permanently distinct workflow?
TallyFlow/Marketing/Product Strategy/TallyFlow Scout.md
+63
View File
@@ -0,0 +1,63 @@
# TallyFlow Scout
**Status:** Active product (app v0.5.3+10 as of July 2026 review)
**Repo:** `tallyflow-assets-iot` (package `tallyflow_scout`)
**Pairs with:** **TallyFlow Edge** (repo `tallyflow-iot`)
**Does not replace:** **TallyFlow Assets** (`tallyflow_mobile`) — the Core-connected mobile app for enrollment, inventory, zone moves, seek-and-find, and scan-and-print
## Overview
**TallyFlow Scout** is a Flutter handheld (and desktop demo) app for barcode and RFID work on the floor **with TallyFlow Edge**. Operators use three destinations:
| Section | What it does |
|---------|----------------|
| **Collect** | Scan barcode/RFID; submit reads to Edge as a **remote reader**, or **export CSV** when Edge is offline / not configured |
| **Verify** | Scan a GS1 barcode, then RFID tags; show whether each EPC encodes the **same GS1 identity key** (SGTIN / SSCC / GRAI / GIAI interoperability). Optional auto-confirm countdown when all match |
| **Locate** | Seek-and-find by EPC hex, GTIN/GS1, or Internal part number with RSSI / geiger feedback — **works fully offline** (no Edge required) |
Scout is the mobile companion for **Edge site deployments** (docks, tunnels, on-prem readers). It is **not** the full asset system of record app: enrollment, zones, Core sync, and scan-and-print remain **TallyFlow Assets**.
## Positioning (marketing truth)
- **Edge path, not Core path** — Scout talks to Edge remote-reader REST (`/api/v1/reader/barcode`, `/api/v1/reader/rfid`, `/health`). Assets talks to Core.
- **Complementary** — Sell Scout with Edge for handheld collect / verify / locate at the reader edge. Sell Assets with Core for asset lifecycle and inventory programs.
- **Offline-capable floor tool** — Collect list + CSV export + Locate work without a live Edge server; submit when online.
- **Hardware-real** — Android industrial scanners via `flutter_hardware_scanner` (e.g. Janam XR2, ATID, SEUIC, URFID stacks); camera barcode fallback on phones; desktop always in simulator mode for demos.
## Target use cases
- Handheld remote reader into a multi-reader Edge site (same feed as fixed Impinj/Zebra readers)
- GS1 barcode↔RFID **Verify** at encode/pack/ship (catch wrong EPC encoding before product leaves)
- Offline **Locate** / seek-and-find on the floor without Core
- CSV collect for demos, audits, or sites not yet wired to Edge submit
- SI / partner demos with desktop simulator (JSON tag groups, optional automation)
## Core features (from product review)
- Material 3 shell: **Collect / Verify / Locate** bottom navigation
- Collect: pending/sent/failed status, manual batch submit or auto-send, CSV share/save (including GS1 type-filter rollup mode)
- Verify: lists all RFID tags (no EPC soft-filter hiding mismatches); Confirm / Reset actions; swipe to Locate or delete
- Locate: EPC mask filters (GS1 / SDG RAIN / hex / part); power slider; geiger audio; handoff from Collect/Verify swipe
- Internal `part_serial` RFID settings aligned with **TallyFlow Print** (group Collect by part; Locate by part)
- Edge health banner; EN + ES localization
- Settings: base URL, remote reader name, optional API key, RFID power, scan beep, symbology filters, verify auto-confirm seconds
## Technical notes
- Android package path renamed toward Scout branding (`com.tallyflow.scout`)
- Vendor AARs for some handheld stacks live under `android/app/lib/` (see repo README); SEUIC uses on-device system libraries
- Desktop (macOS / Linux / Windows): simulation only — load JSON tag groups, send to Edge, add to list, or export CSV
- Service strings in code/README may still say “TallyFlow IoT”; **product name is TallyFlow Edge**
## Related components
- `tallyflow-iot` — **TallyFlow Edge** backend (remote reader + fixed readers + CSV/REST/AMQP egress)
- `tallyflow_mobile` — **TallyFlow Assets** (Core mobile; not replaced by Scout)
- `tallyflow-print` / Print UI — Internal EPC encodings Scout can decode/group
- `flutter_hardware_scanner` (+ XR2 / SEUIC / ATID device plugins)
## Open / watch
- Website and datasheets should say **Scout + Edge**, not “Assets for IoT”
- Distribution channel (Play / sideload / SI bundle) not fixed in vault
- Do not market Scout as Core enrollment or scan-and-print — those stay on Assets