Ticket #1543 (closed enhancement: duplicate)

Opened 7 years ago

Last modified 6 years ago

First boot user experience

Reported by: Zack Owned by: kimquirk
Priority: normal Milestone: 8.2.0 (was Update.2)
Component: interface-design Version: Build 406
Keywords: Cc: kimquirk, eben, Zack, rebecca, cscott
Action Needed: Verified: no
Deployments affected: Blocked By:
Blocking:

Description

When sugar is first booted, the user is asked to enter her name, and pick a color (really colors). I find myself clicking through lots and lots of combinations until I find one I like; but if I click too fast, I'll run right over the one I like. I'd like to be able to go "back" - maybe by right-clicking?

It would actually be nice to have a color chooser to select colors manually instead of "rolling dice", but I guess that's a separate issue :)

Attachments

intro_sequence.zip (264.2 kB) - added by Eben 7 years ago.

Change History

Changed 7 years ago by Eben

  • owner changed from Eben to marco
  • component changed from interface-design to sugar
  • summary changed from First-boot color chooser should allow going "back" to First boot user

The sequence currently in place is just a placeholder. The attached screenshots specify a much cleaner user experience and should eliminate the problem as reported. This sequence is specifically designed to function seamlessly with the general startup sequence specified in #692 and #534 and the home screen which appears thereafter.

Changed 7 years ago by Eben

  • summary changed from First boot user to First boot user experience

Oops...summary now accurate.

Changed 7 years ago by jg

  • cc eben added
  • owner changed from marco to Eben
  • milestone changed from Untriaged to Trial-2

Changed 7 years ago by Eben

  • owner changed from Eben to marco

I'm not sure why this bumped back to me; The design is complete and awaiting implementation.

Changed 7 years ago by marco

  • cc kim added

Kim, Eben how much priority should this have for trial-2? There is substantial work to do here so I'd need to start on this asap if we want it.

Changed 7 years ago by marco

  • cc kimquirk added; kim removed

Damn got Kim nick wrong.

Changed 7 years ago by jg

  • priority changed from normal to low

This seems to be pretty low to me, for Trial-2.

Changed 7 years ago by marco

  • milestone changed from Trial-2 to FRS

Moving to FRS then.

Changed 7 years ago by marco

  • milestone changed from FRS to Trial-3

Changed 7 years ago by coderanger

Adding reporter to CC list

Changed 7 years ago by coderanger

  • cc Zack added

Adding reporter to CC list

Changed 7 years ago by Eben

The spec for the color chooser portion of the intro sequence is now detailed in #2336.

Changed 7 years ago by Eben

Changed 7 years ago by Eben

  • cc rebecca, cscott added

I've updated the intro sequence with a revised design which takes into account the new color chooser and Rebecca's designs for the animation. (I don't presume that the designs in my screens will match exactly what Rebecca will provide; I was just attempting to indicate the presence of this animation and the "in to" and "out of" screens that will make the sequence seamless) This intro sequence can be broken down into the following segments:

00 - 01 : initialization of every boot 02 - 03 : activation sequence; skipped completely when activation is immediately verified 04 - 10 : first boot only sequence for assigning name, colors, photo, etc. 11 - 13 : loading animation that occurs every boot, transitioning to Home screen when complete.

Thus, the average boot will skip directly from frame 01 to frame 11. Scott, can you comment on the various phases indicated here and make sure they match up reasonably from a technical perspective?

Changed 7 years ago by Eben

(Sorry, forgot the "almost-wiki formatting" rules...)

I've updated the intro sequence with a revised design which takes into account the new color chooser and Rebecca's designs for the animation. (I don't presume that the designs in my screens will match exactly what Rebecca will provide; I was just attempting to indicate the presence of this animation and the "in to" and "out of" screens that will make the sequence seamless) This intro sequence can be broken down into the following segments:

  • 00 - 01 : initialization of every boot
  • 02 - 03 : activation sequence; skipped completely when activation is immediately verified
  • 04 - 10 : first boot only sequence for assigning name, colors, photo, etc.
  • 11 - 13 : loading animation that occurs every boot, transitioning to Home screen when complete.

Thus, the average boot will skip directly from frame 01 to frame 11. Scott, can you comment on the various phases indicated here and make sure they match up reasonably from a technical perspective?

Changed 7 years ago by marco

I don't think *all* of this is going to make Trial-3. Let's keep it as a tracker since it contains the design spec. But please file separate tickets if there are parts of it that you think must happen for Trial-3.

Changed 7 years ago by marco

  • owner changed from marco to Eben
  • component changed from sugar to interface-design
  • milestone changed from Trial-3 to Untriaged

We should just move the spec on the Wiki and file separate bugs about the parts we want to get fixed on the short time (we already have a ticket for color chooser).

Changed 7 years ago by kimquirk

  • priority changed from low to normal
  • milestone changed from Untriaged to First Deployment, V1.0

I'm moving this to first deployment since the color chooser is a separate ticket, which can be done for trial-3 (hopefully).

Changed 7 years ago by cscott

Kim, marco's point was that we can't do *all* of this. We need to split it into separate tickets, some pieces of which can be done for Trial-3, First Deployment, or post-FRS.

Changed 7 years ago by kimquirk

  • owner changed from Eben to cscott

I agree that it needs to be broken up; and it turns out that the first piece, the color changer, didn't even make it into Trial-3... so we'll have to give something higher priorities. I found that bug and made it high priority for FRS.

It is very difficult for me to know which pieces of this spec are difficult to implement. I think it would be good for a developer to come up with the separate items and then Jim and I can prioritize them. Can you do that, cscott?

Changed 7 years ago by cscott

Startup design is now documented at http://wiki.laptop.org/go/Startup_Sequence which links to bugs for the various components. In particular, see trac bugs #543, #1328, #3296, #2336, #3297, #3299, #3295, and #692.

Changed 7 years ago by cscott

Whoops: bug #543 should be bug #534 above. Bug #3300 is also part of the startup design.

Changed 7 years ago by cscott

  • owner changed from cscott to kimquirk

Reassigning to kim. This bug should probably be closed, in favor of the specific bugs linked from the wiki page above.

Changed 6 years ago by Eben

  • status changed from new to closed
  • resolution set to duplicate

This seems adequately covered by a variety of tickets, linked above and also linked on the wiki.

Note: See TracTickets for help on using tickets.