Description
Based on the provided user flow diagram, we need to design low-fidelity wireframes for the landing page funnel. This funnel is the critical first touchpoint for the application and must seamlessly route our two primary personas—Route Managers and Drivers—into their specific workflows. Because the app is completely stateless and account-free, the funnel relies on file uploads (CSV, JSON save points, or route files) rather than user logins.
Scope
- In Scope: * Lo-fi wireframes for the initial landing screen (the "Drive Route vs. Manage Route" decision point).
- The Route Manager funnel: differentiating between "First Time" users (prompting manual entry or CSV upload) and returning users (prompting a JSON save point upload).
- The Driver funnel: the interface for uploading a finalized route file to access the Driver View.
- Mobile and desktop layouts.
- Out of Scope: * Lo-fi designs for the actual Edit Page or Result Page (handled in separate tasks).
- High-fidelity styling, colors, or branding.
Goal
To establish a clear, intuitive entry sequence that explains the tool's stateless nature through its UX (e.g., uploading a save state instead of logging in) and accurately directs users to the correct workspace based on their role.
Acceptance Criteria
Assignee
@eltouami
Description
Based on the provided user flow diagram, we need to design low-fidelity wireframes for the landing page funnel. This funnel is the critical first touchpoint for the application and must seamlessly route our two primary personas—Route Managers and Drivers—into their specific workflows. Because the app is completely stateless and account-free, the funnel relies on file uploads (CSV, JSON save points, or route files) rather than user logins.
Scope
Goal
To establish a clear, intuitive entry sequence that explains the tool's stateless nature through its UX (e.g., uploading a save state instead of logging in) and accurately directs users to the correct workspace based on their role.
Acceptance Criteria
Assignee
@eltouami