Skip to content

Latest commit

 

History

History
43 lines (41 loc) · 3.57 KB

TODO.md

File metadata and controls

43 lines (41 loc) · 3.57 KB

TA's Feedback:

  • Layout and Alignment: Requires improvement for better visual appeal and user experience.

Things Done:

  • Implement EN/FR translation
  • Implement a Emergency Exit that allows users to exit the app in case of an emergency (Home button)
  • Add a Full Schedule in the Route Information Screen
  • Add Home button to the homepage on all of the screen except the Homepage
  • Error notifications in the Refund screen
  • Move to Vite instead of CRA for faster development
  • Refund screen lacks an explanation of a why a refund fails
  • Change the "Next" button in Refund Screen to "Process Refund"
  • Add a refund button in the Payment Confirmation Screen
  • Implement a purchase ticket button in the Route Information Screen
  • Adding a Purchase Tickets button in the Route Information Screen
  • Missing a frequency of the bus in the More Information Screen-> want to only display two upcoming buses
  • Have the helpline details at the bottom of the screen since the Help Modal because the users may forgot about it
  • Implement if the Weather/Time are dynamically updated or not like a Last updated
  • "+" and "-" buttons in the Select Tickets Screen require headers or have helper text
  • Add a note in the Purchase Tickets that tickets are valid for 90 minutes
  • Payment Screen should incorporate a modal that when users attempt to cancel their purchase prompts them to confirm their decision to ensure that they do not accidentally cancel their purchase
  • Adding the route number, route name to the payment screen
  • Language Selection Button: Consider changing the style to make the selected language more obvious.
  • Refund Pages: Make the help button more prominent. Include contact numbers on the page if the return fails.
  • Purchase Successful and Refund Success: Standardize all screens to use the same heading style.
  • Purchase Successful Screen: Instead of just saying "tickets below," add a picture of an actual "ticket pocket" for user guidance.
  • Payment Screen: Add an "edit" or "back" button for user convenience. Clarify instructions like "Follow directions on the terminal."
  • Payment and Refund Screens: No indication of a transaction being processed after a user action, consider adding progress indicators or loading animations post-action.
  • Refund Screen: Position the Process Refund to web standards
  • Purchase Ticket Screen: The system does not clearly indicate which steps have been completed in the ticket purchasing process, consider adding a progress bar or a checklist.
  • Weather Tab Placement: Consider placing the weather tab in a separate side card since it's not immediately relevant to bus information.
  • Route Information Screen: Clarify how users access this screen. Consider moving the "number of stops" to more info and emphasizing bus interval.
  • Add a unsuccessful purchase screen to demo the error handling
  • Dashboard Screen: Display the user's current location.
  • Dashboard: Make the weather card stay open
  • All Pages: Make the non selected language button transparent
  • Route Information Screen: Emphasize the routes which are displayed in the dashboard
  • Route Information Screen: Add a back button to the route information screen
  • Make Payment Screen: Add the kiosk station and highlight the payment component of it in red
  • Purchase Successful Screen: Add the kiosk station and highlight the ticket collection component of it in red
  • Select Tickets Screen: Emphasize the routes which are displayed in the dashboard

Nice to haves: