Rework the copy in the 'Customize' slide in the first-run tour to include a possible option for customization. Feedback suggests that people didn't know they could change their search engine, so this could be a good candidate as an option for customizing. Darrin, Matej - looking to you both for reworking the copy a little to reflect this option (Darrin is on point). (very much) desired for 1.1 and would need this locked down for a string freeze soon.
Pre-landing strings here https://github.com/mozilla/firefox-ios/pull/1069
Not completely sure what the ask is here. Let's sync up tomorrow to hash this out.
Flags: needinfo?(alam) → needinfo?(dhenein)
^ Although I did just go through the commit log and update the copy in my design (posted in bug 1203563 before reading this bug).
Anthony - can you add the full flow maybe to this bug so we can see it holistically, based on the three dependent bugs? In the attachment in bug 1203563, it didn't include an update to the 'customize' and I want to ensure we get this included :). Maybe we can now use this bug for tweaking the final, end-to-end flow? It's looking really good, in my opinion! One tweak I would suggest (but not enforce) would be to also include the Firefox logo on all the screens on the 'sync' page. I'm just trying to make it super obvious what needs to be done here.
I landed a new string for the customize page "Personalize things like your default search engine in Settings."... maybe thats all that we needed for this bug?
Yep, I remembered you thinking along those lines but hadn't seen it show up yet in mocks. Yay!
Created attachment 8662462 [details] Screen Shot 2015-09-17 at 9.23.02 AM.png done!
Created attachment 8662491 [details] prev_FR_V2.zip Continuing the discussion from bug 1203563 here. I've attached all 5 screens in this package. It should contain all the changes from feedback :) thoughts?
Attachment #8662462 - Attachment is obsolete: true
I like it. Ship it ;)
I'm liking this as well! My only 'nit' would be to say 'Personalize your experience like ...' instead of 'Personalize things like...' just to make it a bit more clear and less informal / colloquial.
(In reply to Karen Rudnitski [:kar] from comment #10) > I'm liking this as well! > > My only 'nit' would be to say 'Personalize your experience like ...' instead > of 'Personalize things like...' just to make it a bit more clear and less > informal / colloquial. I think if we want to add "experience" then we need to rework this a bit as "Personalize your experience like your default search engine in Settings" doesn't flow that well. It could simply be "Personalize your browsing experience in Settings." Or if we want to call out search, then I would suggest something like "Change your default search engine and other options in Settings."
calling our search is deffo our intention based on feedback from our user research. I'm not married to 'experience' but it just felt that 'things' was very informal. What about 'Make it yours like choosing your default search engine in Settings'? Or I stop wordsmithing and leave it up to your fine minds!
(In reply to Karen Rudnitski [:kar] from comment #12) > calling our search is deffo our intention based on feedback from our user > research. I'm not married to 'experience' but it just felt that 'things' was > very informal. > > What about 'Make it yours like choosing your default search engine in > Settings'? Or I stop wordsmithing and leave it up to your fine minds! How about: Personalize your default search engine and more in Settings.
Going to make an executive decision based on string freeze being today and all the fine feedback we've receieved, thanks all! Going to ship 1.1 with "Personalize your default search engine and more in Settings."
"Sync Your Devices." string has inaccurate localization comment.
Follow-up or new bug is required
Whiteboard: [needs strings]
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
The following text is displayed in the Customize panel "Personalize your default search engine and more in Settings." Verifying as fixed on Beta 1111
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.