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

Make Map view optional #504

Open
3 of 4 tasks
Matthias84 opened this issue Aug 11, 2018 · 6 comments
Open
3 of 4 tasks

Make Map view optional #504

Matthias84 opened this issue Aug 11, 2018 · 6 comments
Labels
enhancement 🏗️ A functional improvement.

Comments

@Matthias84
Copy link

Acknowledgments
Please check the following boxes with an x if they apply:

  • The feature I want to propose would be useful for the majority of users, not only for me personally.
  • I am aware that Transportr is mostly developed by one person in their unpaid spare time.
  • I can help myself to get this feature implemented or know someone who wants to do it.
  • If I want to add support for a new region or country, I checked that this is already available in public-transport-enabler and know the process described on the Transportr homepage.

Is your feature request related to a problem? Please describe.
The new introduced map widget uses a lot of space on on the screen and consumes a lot of extra traffic. This results in more clicks (e.g. find stops and then in extramenu setup day, time, reverse, ...) and lot of network requests (initiated when I change every setting of the trip step by step.

Describe the solution you'd like
Let users disable the map view at the settings, so the dialog has more space again. Add an search button, so users fireup requests manually again.

Describe alternatives you've considered

Additional context
I tested the new design for some weeks, to see if I benefit from the new UI design. To sad, my UX is more frustrating 😢
I use the App usually for short inter-city rides (when does Bus 123 leaf from XYZ, ...) or to manage bigger rides (riding hours in trains). In the first scenario, I know the location already and at the second one this information aren't usefull because I'm interested at the plan of my hops and I don't have to leave the trainstation etc.

@TheLastProject
Copy link
Contributor

Does #462 (comment) solve your issue?

@grote grote added the duplicate ➿ This ticket already exists. label Aug 11, 2018
@grote
Copy link
Owner

grote commented Aug 11, 2018

I'd say this is a duplicate of #462 and it sounds like #485 should resolve most of the described issues.

Add an search button, so users fireup requests manually again.

How would this help? You have been complaining about too many clicks. This would add another click that was saved in the new UI.

The new introduced map widget [...] consumes a lot of extra traffic

You seem to know how much it is. Could you please let me know how much it is for your typical usage of the app and how much percent that is of your total data usage?

at the second one this information aren't usefull because I'm interested at the plan of my hops and I don't have to leave the trainstation etc.

You never have to change transports and need to check how far along the trip you are?

@grote grote closed this as completed Aug 11, 2018
@ialokim
Copy link
Collaborator

ialokim commented Sep 6, 2020

Two other things to consider here:

for phones with low GPU/memory loading any map it is a struggle. And if the first interaction with the app is slow, then the user will definitely assume app is bad. (You may ignore ratings as you do it for your own fun/satisfaction but this leads to assumption on the app quality). In the old GUI, I never ever even used the map (also my friends). We used 'transportr' as it was lightweight for older phones with low data usage.

originally posted by @ort163 in #462 (comment)

And there's still the issue on Replicant #496.

I'm going to reopen this issue for this specific suggestion to be able to close the very general #462.

@ialokim ialokim reopened this Sep 6, 2020
@ialokim ialokim added enhancement 🏗️ A functional improvement. and removed duplicate ➿ This ticket already exists. labels Sep 8, 2020
@weeman1337
Copy link

weeman1337 commented Jul 2, 2021

@grote would you be fine having a new setting choosing whether to start directly from the search view?

The initial screen/flow is really bugging me:

  • Start Transportr
  • Trained from the "standards" (1) I always start typing my starting position into the first input on the screen
  • The map scrolls around - takes time and I don't care - I just want to get the timetable
  • Tap the navigate button
  • New screen appears - uff
  • What I have typed into the input turns out to be the destination
  • Tap the swap button
  • Input the destination
  • Finally: The timetable appears 👯‍♀️

With the setting this could become easier:

  • Start Transportr
  • Fill in start and destination
  • The timetable appears 🎉

If that setting is an option I could implement it.

(1) The standards: A form with "start" and "destination" fields

@ialokim
Copy link
Collaborator

ialokim commented Jul 2, 2021

Hi @weeman1337, perhaps the directions shortcut (see here) would already solve your use-case?

@weeman1337
Copy link

Thanks @ialokim that is what I have been looking for. While I would say I am an advanced user this was actually non-existing for me in that place. :/ Anyway offtopic here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement 🏗️ A functional improvement.
Projects
None yet
Development

No branches or pull requests

5 participants