Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Route Schedules View - Responsive Design Issues and UX Improvements #164

Open
tarunsinghofficial opened this issue Jan 15, 2025 · 2 comments · May be fixed by #169
Open

Route Schedules View - Responsive Design Issues and UX Improvements #164

tarunsinghofficial opened this issue Jan 15, 2025 · 2 comments · May be fixed by #169
Assignees

Comments

@tarunsinghofficial
Copy link
Collaborator

Issue

There are two main concerns in the Route Schedules view:

  1. Responsiveness Issues:
  • The time display in the schedule table shows awkward spacing ("02 , 33")
  • The layout may not be optimally using the available space
  1. UI/UX Concern:
    Currently implementing both "Show All Routes" and "Collapse All Routes" as separate buttons, which may not be the most efficient UI pattern.

Expected Behavior

Responsiveness:

  • Time/minutes should be properly formatted without extra spacing
  • Layout should adapt smoothly to different screen sizes

UI Controls:
Recommend switching to a single toggle button that:

  • Shows "Show All Routes" when routes are collapsed
  • Changes to "Collapse All Routes" when routes are expanded
  • Reduces visual clutter
  • Makes the interaction more intuitive

Screenshots:

image

image

@tarunsinghofficial tarunsinghofficial self-assigned this Jan 15, 2025
@yuvraajnarula
Copy link

yuvraajnarula commented Jan 19, 2025

@tarunsinghofficial can I help in this issue as well(or #163)?

@tarunsinghofficial
Copy link
Collaborator Author

@tarunsinghofficial can I help in this issue as well(or #163)?

Hi @yuvraajnarula, Thanks for the help! But the work is already in progress :)

@tarunsinghofficial tarunsinghofficial linked a pull request Jan 21, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants