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.
25 lines
972 B
Markdown
25 lines
972 B
Markdown
# tallyflow_mobile Review
|
|
|
|
**Tech Stack:** Flutter (iOS + Android)
|
|
|
|
## Purpose
|
|
Dedicated mobile application for TallyFlow.
|
|
|
|
## Key Observations
|
|
- Separate Flutter project from `tallyflow-decode`
|
|
- Full mobile app structure (android, ios, lib, assets)
|
|
- Appears to be the primary/official TallyFlow mobile client
|
|
|
|
## Relevance to Platform
|
|
This repo represents the **mobile pillar** of TallyFlow, distinct from the web, Edge, print, and capture components.
|
|
|
|
## Status
|
|
Initial structure review complete.
|
|
## Roadmap / Integration Opportunities
|
|
- ~~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 Edge** for real-time location, sensor data, and zone-based workflows directly in the mobile Assets app.
|
|
|
|
## UX Design
|
|
- Built with **Material 3**
|
|
- Large buttons prioritized for industrial/glove-friendly use in harsh environments
|