From d070a5c4a954f5b19572e02b37b191b51db9b876 Mon Sep 17 00:00:00 2001 From: TNB Date: Tue, 16 Jun 2026 09:01:32 -0400 Subject: [PATCH] Add TallyFlow Clarifying Questions note for daily product research cycle (Tuesday: Mobile App focus) --- .../Product/TallyFlow Clarifying Questions.md | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 TallyFlow/Product/TallyFlow Clarifying Questions.md diff --git a/TallyFlow/Product/TallyFlow Clarifying Questions.md b/TallyFlow/Product/TallyFlow Clarifying Questions.md new file mode 100644 index 0000000..09373bf --- /dev/null +++ b/TallyFlow/Product/TallyFlow Clarifying Questions.md @@ -0,0 +1,20 @@ +# TallyFlow Clarifying Questions + +**Purpose:** Persistent record of clarifying questions asked during daily product research cycles to avoid repetition and build on prior knowledge. Questions are cycled by weekday product focus. + +## Previously Asked Questions + +*(No prior questions recorded as of start of cycle - June 2026)* + +## Tuesday - Mobile App (Enroll, update, inventory, and locate) +**Question Asked:** How does the Mobile App handle asset 'locate' and inventory updates in offline mode, including sync behavior upon reconnection, and are there any specific features or limitations for use in large-scale environments like rail yards or manufacturing facilities with intermittent connectivity? + +**Context/Notes:** This question builds on the brief mentions of offline sync and field operations in the User's Guide. It aims to clarify details for improving website content, documentation, and marketing around mobile reliability in challenging environments (e.g., rail, remote sites). Addresses potential gaps in integration with IoT/Capture for real-time locate. + +**Date Asked:** Tuesday, June 16, 2026 + +## Other Days +- Monday (Core): [To be added next cycle] +- Wednesday (Print): [To be added] +- Thursday (Capture): [To be added] +- Friday (IoT): [To be added]