Closed Bug 818588 Opened 12 years ago Closed 12 years ago

Reduce number of steps and swap placeholders for visuals

Categories

(Firefox OS Graveyard :: Gaia::First Time Experience, defect, P1)

Product:
Firefox OS Graveyard
Component:
Gaia::First Time Experience
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: hello, Unassigned)

References

Details

(Whiteboard: interaction, UX-P2) 

The current tutorial has 11 steps. Let's try to bring it down to 5:

* Swipe left to browse your apps
* Swipe right to discover new apps
* Tap and hold on an icon to delete or move it
* Swipe down the status bar to access recent notifications, credit information and settings.
* Tap and hold the home button to browse and close recent apps

Also, it should be noted that the current design only allows for two lines of text. That might be fine for English, but I find that extremely optimistic in Spanish and Brazilian. There should be enough space for a third line.

I understand this might not be the final version, but it'll be a great improvement over the current one.

Victoria, can you point to the assets?
Flags: needinfo?(vpg)
Sure.
Rafa,
The adjustments to the design allow 3 lines, as you saw the 3 in one screen, so that point is solved. 
This is the link to the screens so layout is followed and correct implemented:
https://www.dropbox.com/sh/9ficu2avv3fu14c/CPnrW39SmF

This is the link to the assets, is there is something needed in a different way please do not hesitate:
https://www.dropbox.com/sh/4zeb4gxfprzhyqu/q25zUbDqcm

The progress indicator at the top is a white dinamic width rectangle with 3px height.
Flags: needinfo?(vpg)
Thanks Rafa for refining this. I like the reduced set. 

Regarding the text of the first two items—"Swipe left to browse your apps". Reading that, even as a tech savy person, I think the text is telling me that my apps are to the left. When in fact they are on the right, and the tutorial text is just being very literal about the direction of the user gesture.

It's late any my brain is starting to get fuzzy, but I'd suggest we think about tweaking the language to be more intuitive. What do you think?
Whiteboard: interaction, UX-P2
Thanks, Vicky :)

Josh, copy improvements more than welcome; those lines were never intended as final copy... I understand we have a couple of guys working on that.
Josh (or Rafa). can you point me to the ones working on the texts? I'm already working on reducing the steps and the new assets, and would like to do the localizing at the same time. No rush on it, cause we can do it later (late l10n) but think is better to do everything in one shot.
Flags: needinfo?(jcarpenter)
(In reply to Rafael Rebolleda [:rafaelrebolleda] from comment #0)
> The current tutorial has 11 steps. Let's try to bring it down to 5:
[...]
> * Swipe down the status bar to access recent notifications, credit
> information and settings.

Note that the current tutorial has a typo in this section, as described in bug 818350.  If this bug here is ripping out & replacing that text, let's be sure not to propagate that typo in the new text.  Thanks!  (I'm posting over here at fcampo's suggestion, per bug 818350 comment 9)
Hey Victoria, I think there's one image missing from the assets (step-5), can you check if I'm wrong?
Flags: needinfo?(vpg)
Also, it seems that the images have a shadow on the bottom that makes them look weird on the tutorial. Is this intended?
(In reply to Fernando Campo (:fcampo) from comment #4)
> Josh (or Rafa). can you point me to the ones working on the texts? I'm
> already working on reducing the steps and the new assets, and would like to
> do the localizing at the same time. No rush on it, cause we can do it later
> (late l10n) but think is better to do everything in one shot.

Stas (cc'd) is the guy to talk to for l10n. And Rafa worked on the most recent round of text revisions, I believe.
Flags: needinfo?(jcarpenter)
Assets are updated in the same place:
https://www.dropbox.com/sh/4zeb4gxfprzhyqu/q25zUbDqcm

Last step was missing since I thought the task switching was not available ;)

Thanks!
V
Flags: needinfo?(vpg)
Will get fixed when https://github.com/mozilla-b2g/gaia/pull/6999 gets approved (asking for revisions to the patch on https://bugzilla.mozilla.org/show_bug.cgi?id=820150
My immediate reaction was also that swipes would be the other way around.

The previous text has "swipe from left to right" instead of "swipe right" (and get to the thing on the left).

I wonder if Matej has some comments on the copy, the changes are at https://github.com/mozilla-b2g/gaia/pull/6999/files#L14L164
(In reply to Axel Hecht [:Pike] from comment #11)
> My immediate reaction was also that swipes would be the other way around.
> 
> The previous text has "swipe from left to right" instead of "swipe right"
> (and get to the thing on the left).
> 
> I wonder if Matej has some comments on the copy, the changes are at
> https://github.com/mozilla-b2g/gaia/pull/6999/files#L14L164

I definitely think this could create some confusion. "From left to right" (and "right to left") is clearer. I would recommend using that.

I also find this confusing: Swipe down the status bar to access recent notifications, credit information and settings.

I would say: Swipe down from the top of the screen to access recent notifications, credit information and settings.
Better yet: Swipe down to access recent notifications, credit information and settings.

These are accompanied by illustrations, so we should be able to err on the side of succinct for the captions.
I'm not english native speaker, but also thinks that referring to the origin and direction of the swipe is clearer for the user. Said that, just a reminder that due to current design, we should be focusing on keeping the texts on a max of three lines.

If we are unable to do so, some tweaks should be done on UX

My understanding is that the current propositions for the texts are:

- Swipe from right to left to browse your apps.

- Swipe from left to right to discover new apps.

- Tap and hold on an icon to delete or move it. [no changes]

- Swipe down from the top to access recent notifications, credit information and settings.

- Tap and hold the home button to browse and close recent apps. [no changes]

Note that Josh proposition is to remove the 'from the top' part, but I think that if we state the origin and direction when referring to the other swipes, we should do also in this one for consistency.

Other ideas? Objections? Corrections?
Blocks: 820150
This bug is blocking 820150 which is BB+ P1, so it should be BB+ in order to fix 820150 asap
blocking-basecamp: --- → ?
Rafa, Josh, Victoria... could you please answer Fernando?
Flags: needinfo?(jcarpenter)
Flags: needinfo?(hello)
Flags: needinfo?(vpg)
(In reply to Fernando Campo (:fcampo) from comment #14)
> I'm not english native speaker, but also thinks that referring to the origin
> and direction of the swipe is clearer for the user. Said that, just a
> reminder that due to current design, we should be focusing on keeping the
> texts on a max of three lines.
> 
> If we are unable to do so, some tweaks should be done on UX
> 
> My understanding is that the current propositions for the texts are:
> 
> - Swipe from right to left to browse your apps.
> 
> - Swipe from left to right to discover new apps.
> 
> - Tap and hold on an icon to delete or move it. [no changes]
> 
> - Swipe down from the top to access recent notifications, credit information
> and settings.
> 
> - Tap and hold the home button to browse and close recent apps. [no changes]
> 
> Note that Josh proposition is to remove the 'from the top' part, but I think
> that if we state the origin and direction when referring to the other
> swipes, we should do also in this one for consistency.
> 
> Other ideas? Objections? Corrections?

I agree with this recommendation. I like the simpler/shorter text and the image reinforces the idea we have it covered, BUT if you are already confused, let's avoid any confusion possibility by having this last strings as they are, a bit more descriptive.
Flags: needinfo?(vpg)
blocking-basecamp: ? → +
Priority: -- → P1
I'm still favor shorter messages. Consistency with the left-right messages is not important, in this case.
blocking-basecamp: + → ---
Flags: needinfo?(jcarpenter)
Josh, did you intentionally clear the blocking-basecamp flag?
Yes, per triage on Monday night. We're reevaluating in email thread now, however, so this may be flipped back.
Well, I still think this is a bb+ because it's blocking bug 820150,wich is bb+, so I am renominating.

Apart from that, my understanding is that we agree on most of the texts, only SwipeDown have comments, so need a decision on it.

Everyone ok if we take out 'from top' and we leave it as
- Swipe down to access recent notifications, credit information and settings.
???
blocking-basecamp: --- → ?
(In reply to Fernando Campo (:fcampo) from comment #21)

> Everyone ok if we take out 'from top' and we leave it as
> - Swipe down to access recent notifications, credit information and settings.
> ???

Josh, is it ok with you? We want to merge this ;)
Flags: needinfo?(jcarpenter)
Changed the relation Blocking / Depends as the dependents will solve this one.
No longer blocks: 820150
blocking-basecamp: ? → ---
Depends on: 820150
This bug will be fixed when bug 820150 (BB+) is landed
(In reply to Maria Angeles Oteo:oteo from comment #22)
> (In reply to Fernando Campo (:fcampo) from comment #21)
> 
> > Everyone ok if we take out 'from top' and we leave it as
> > - Swipe down to access recent notifications, credit information and settings.
> > ???
> 
> Josh, is it ok with you? We want to merge this ;)

Heh, it's what I've suggested twice now, so yes, I'm definitely okay with this ;)
Flags: needinfo?(jcarpenter)
Flags: needinfo?(hello) → needinfo?
Thanks Josh, I just needed confirmation that we all have an agreement on every string, so I can change them and ping :pike again.
Flags: needinfo?
Solved together with bug 820150 https://github.com/mozilla-b2g/gaia/commit/d85fdfc8cb9d70b264321e633a047f66dcbbcea2
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.