Confusion about "missing trips" from the "To Label" screen

[shankari]

Report from a user:

I just found another problem: the return part of the trip at 5:00 below is not showing up.
Update: I found that the return trip does appear in the trip diary and under "all trips" on the labels screen. Sorry for the false alarm. Probably there was just a high enough certainty of the labels that it wasn't shown on the "to label" screen. Unfortunately, all of the inferred labels were incorrect. :(

Reported by other users as well; one of them saw only the "red trips" in the "to label" screen and thought that the auto-labeling was not working; when they saw "all trips" ~ 50% of their trips were auto-labeled.

@GabrielKS, I think this one is yours as well

[GabrielKS]

Yeah, I have Thoughts on this one.

What I see going on here is that

1. Existing users have become accustomed to all of their trips appearing in the default Label view because that has been the case up until now
2. Now that they're only seeing the ones they're expected to label, they think trips are missing
3. As soon as someone shows them the other two tabs and they see the "missing" trips there, they understand what's going on and no longer perceive a problem

Correspondingly, there are three ways to fix this:

1. Don't get users accustomed to seeing all of their trips in the default Label view — not possible for existing users, but if my new UI is universally adopted, this will automatically be the case for all new users after this summer
2. Put all trips in the default view, so the user's learned expectation is not broken
3. Communicate clearly to every user who has developed this expectation that things have changed, they should no longer expect to see every trip on the default view, and if they want to see every trip there's a way to do that

A principle underlying my design has been "by default, only show the user what they need to be shown." I can't think of a way to implement solution 2 above without breaking this principle and requiring a significant redesign. Moreover, we're hoping to get to a point with our inference algorithms where the user maybe only needs to label one trip every few days, at least in relaxed mode. I think having a screen that displays only those trips that the user needs to interact with is the correct choice, and I think that having that screen be the default screen is also the correct choice, at least in the long term.

So I propose we go with solution 3 for now until we have gotten to every user who has developed the now-problematic assumption, at which point solution 1 will take over.

[shankari]

I am definitely not a UX designer, but I wonder if including an in-screen "walkthrough" to show "here's where all the trips are" the first few times would be helpful. We do have ngWalkthrough integrated into the UI.

e.g.
https://github.com/e-mission/e-mission-phone/blob/066dc51dd175fae446e82d7d53717a8ae5d1f7b2/www/js/diary/infinite_scroll_list.js#L536

You have to define steps and change the "DONE" condition
https://github.com/e-mission/e-mission-phone/blob/066dc51dd175fae446e82d7d53717a8ae5d1f7b2/www/js/diary/infinite_scroll_list.js#L550

[shankari]

I just double-checked this by clicking on the ? button on the main diary page, and it seems to work.

[shankari]

@GabrielKS after watching my daughter label trips today, I think that part of the reason for this confusion is that people using temporal "linkages" between trips to figure out the label. So she expected to two trips today, one to school and one from school. But she only saw one. So she felt like she had to open up the map to figure out which one it was, while if there had been two, she would have been able to know which one was which just by looking at the ordering.

BTW, are you able to add the walkthrough before the deployment?