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 display redesign, don't reload entire page on earlier/later #254

Open
Bertware opened this issue Dec 6, 2016 · 2 comments
Open

Route display redesign, don't reload entire page on earlier/later #254

Bertware opened this issue Dec 6, 2016 · 2 comments

Comments

@Bertware
Copy link
Member

Bertware commented Dec 6, 2016

Current situation:

  • Search for a route
  • Press the earlier/later button to load earlier/later trains

Result:

  • The whole page changes into a loading indicator and refreshes the entire search result

Possible improvement:

  • Only add the new trains before/after the current results instead of refreshing everything.

Furthermore, the earlier/later buttons could be put above and below the results. This way, if you scroll up or down to see more results, you reach the button (which would be as wide as a result). Another option is to append the results with later trains when the bottom of the page is reached.
If desired, the earliest/latest buttons could be kept, or they could be dropped in favor of simplicity.

The free space at the side (were the earlier/later buttons were) could now be used for the route planner input. This way, it could scroll along when you browse the results.

@xavez this is your field of expertise

@Bertware Bertware changed the title Earlier / Later: add new trains instead of reloading the entire page Route display redesign, don't reload entire page on earlier/later Dec 14, 2016
@Bertware
Copy link
Member Author

Bertware commented Dec 14, 2016

Current:
Current
Suggested:
Suggested

On smaller screens, the planner would still be on top. Also, on smaller (smartphone) screens, the previous/later buttons would prove their value, as users would always have the buttons on screen when they need them. (when at the end of the results list)

Current mobile:
original mobile
Suggested mobile:
Suggested mobile

@pietercolpaert
Copy link
Member

Looks better imo!

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

No branches or pull requests

2 participants