Mark scan-and-print as shipped; add capabilities one-pager and refresh use cases

This commit is contained in:
TNB
2026-07-20 12:39:11 -04:00
parent 1bad1b340e
commit 005f7f7ad3
5 changed files with 101 additions and 20 deletions
@@ -70,7 +70,7 @@ Operator → TallyFlow Print app → Print API → Print worker → Zebra printe
*Source: Direct clarification from Todd B*
## Roadmap / Integration Opportunities
- **Mobile (Assets) integration** for Scan-and-Print workflows — Allow the mobile app to trigger print jobs (e.g., reprint, on-demand encoding during field scans or enrollment). Closes the gap between mobile asset management and the Print pillar.
- ~~**Mobile (Assets) integration** for Scan-and-Print~~ — **Shipped:** mobile can trigger print jobs (reprint, on-demand encoding during field scans or enrollment).
- **IoT integration** — Expose print job status/events and printer health to TallyFlow IoT for unified dashboards and alerts.
## Recent Changes (develop branch pull - July 2026)
@@ -16,7 +16,7 @@ This repo represents the **mobile pillar** of TallyFlow, distinct from the web,
## Status
Initial structure review complete.
## Roadmap / Integration Opportunities
- Integration with **TallyFlow Print** for Scan-and-Print workflows (scan existing asset or during enrollment → trigger print job for new/replacement labels directly from mobile). Would unify field operations across Assets (Mobile) and Print components.
- ~~Integration with **TallyFlow Print** for Scan-and-Print~~ — **Shipped:** scan existing asset or enroll → trigger print job for new/replacement labels from mobile.
- Integration with **TallyFlow IoT** for real-time location, sensor data, and zone-based workflows directly in the mobile Assets app.
## UX Design