diff --git a/TallyFlow/Dashboard.md b/TallyFlow/Dashboard.md index 9902175..39e2192 100644 --- a/TallyFlow/Dashboard.md +++ b/TallyFlow/Dashboard.md @@ -17,4 +17,4 @@ All core repos reviewed and documented in `Product/Code Reviews/`. Key themes: - [[Product/Code Reviews/Code Review Notes]] - [[Marketing/Messaging/Positioning]] -_Last updated: 2026-06-18_ \ No newline at end of file +_Last updated: 2026-06-23_ \ No newline at end of file diff --git a/TallyFlow/Product/TallyFlow Clarifying Questions.md b/TallyFlow/Product/TallyFlow Clarifying Questions.md index d28921c..127c6de 100644 --- a/TallyFlow/Product/TallyFlow Clarifying Questions.md +++ b/TallyFlow/Product/TallyFlow Clarifying Questions.md @@ -47,5 +47,13 @@ **Source Code Review Note (2026-06-22):** Reviewed recent commits in tallyflow-web (v1.33.2 hotfixes for tags array conversion, duplicate handling, import startsWith fix; v1.33.1/1.33.0 with import-zone feature merged). Confirmed strong emphasis on zone/asset import, exception handling, and reporting. No changes to question needed; question seeks production details on search, RBAC, API surface, and dashboard customization not fully documented yet. +## Tuesday - Mobile App (Enroll, update, inventory, and locate) [June 23, 2026 Cycle] +**Question Asked:** Building on the high-level description of the Mobile App for field enrollment, scanning, updates, locate, and inventory, what specific details exist around the enrollment workflow (required/custom fields, support for bulk/rapid scanning, parent-child asset association during enrollment, photo attachments or condition logging, validation against duplicates or existing records), mobile UI/UX considerations for industrial environments (e.g., large buttons, glove-friendly, dark mode, offline-first design), integration points with TallyFlow Print (e.g., triggering print jobs from mobile during enrollment), TallyFlow Capture/IoT (real-time locate handoff), and Core (sync priorities, conflict resolution), and any support for advanced locate features like indoor positioning, asset history trails, or proximity alerts? + +**Context/Notes:** This new question avoids repeating the previous Tuesday focus on offline sync/locate limitations and instead targets enrollment details, industrial UX, cross-product integrations (Print, Capture, IoT, Core), and advanced locate capabilities to improve website feature descriptions, User's Guide depth (currently high-level), marketing for field operations in rail/manufacturing/waste management, and documentation gaps around mobile as the primary on-site tool. Addresses known emphasis on mobile enrollment/on-site workflows and potential for tighter product integration. + +**Date Asked:** Tuesday, June 23, 2026 + ## Other Days - Monday (Core): Question added June 22, 2026 (see above) +- Tuesday (Mobile App): New question added June 23, 2026 (see above)