[music] Using content-hub or url-handler on first run causes the walkthrough issues

[Andrew Hayzen]

Steps:
1) Ensure your config is clear
2) Start the music-app via url-handler (via music scope) or content-hub (web download)
3) Notice that the walkthrough page loads and then the now playing appears ontop of the walkthrough

Note if you restart the app the walkthrough will be shown again (as it was never completed)

Solutions
1) Don't start playing the audio and showing the now playing page until the walkthrough is completed
2) Only show the walkthrough on a firstRun that doesn't include content-hub/urlhandler
3) Assume that the user has figured out how to get music on their device and dismiss walkthrough if content-hub/urlhandler are called
4) Show the walkthrough ontop of the now playing page

Issues:
1) Delays starting of audio
2) Could be difficult technically to stop the walkthrough flashing up
3) The user may have only figured out one way to get music onto their device and not all of the ways that the walkthrough describes
4) User cannot easily stop/control the music until the walkthrough is dismissed

---------------------------------------------------

from design: Desired solution is #1

[Andrew Hayzen (ahayzen)]

I vote for solution 1) :)

Adding ubuntu-ux as also affects for design input.

[Alan Pope 🍺🐧🐱 🦄 (popey)]

I see no reason to skip the walkthrough.

[Andrew Hayzen (ahayzen)]

UX have agreed with solution 1)

[Victor Thompson (vthompson)]

I think the only reasonable solutions are either #1 or #2 listed above. However, I think it needs to be said that #1 has the drawback of preventing/delaying the user from accomplishing the task they are attempting to complete. If the device comes with some music on it and the user selects a song from the scope, one could reasonably expect the app to play said content without presenting the user with a walkthrough they most likely will not read. So, in my opinion task oriented operations (opening from the scope, importing via content hub) would provide the best experience to the user if they were not interrupted, while non-task oriented operations, such as simply opening the app, would be better served if they did show the walkthrough. That being said, most apps that have a welcome screen do #1 from above, I just don't think it provides the best user experience.

[Andrew Hayzen (ahayzen)]

I agree that #1 does block the user from performing the action instantly, however I fear #2 would be tricky to implement without the walkthrough flickering up as the app starts.

Furthermore if the user wants to quickly play a track then can select "Skip" in the walkthrough. I've used this quite a few times now and the workflow/ux doesn't feel too bad.

[Olga Kemmet (olga-kemmet)]

Design thinks #1 solution is desired.

[Ubuntu Phone Apps Jenkins Bot (ubuntu-phone-apps-jenkins-bot)]

Fix committed into lp:music-app at revision 855, scheduled for release in music-app, milestone music-app-14.10-week-40

[Ubuntu Phone Apps Jenkins Bot (ubuntu-phone-apps-jenkins-bot)]

Fix committed into lp:music-app/refactor at revision 851, scheduled for release in music-app, milestone 3.0