Ubuntu Wiki

• Launchpad Entry: lucid-ubuntu-one-musicstore

• Created:

• Contributors:

• Packages affected:

Summary Simple Music Store embedded in Rhythmbox / Banshee

Requirements

The Lucid music store project aims to deliver the ability to purchase music from within a desktop music player. The overriding requirement of the project is to minimise engineering effort. This will be achieved through the usage of off the shelf solutions with minimal modifications. Only changes classified as blockers will fall within scope of this project. No effort will be expended towards improving the user experience of the default off the shelf components.

Concept

1. Integrate a web browser engine into Rhythmbox (WebKitGtk+) or Banshee (Mono WebBrowser).

2. Add a link to the Ubuntu One music store into the music player (Rhythmbox or Banshee) library panel. When selected this link opens the Web Browser in the body area.
3. The Web Browser loads the music store into the body area of music player.
4. The music store is used almost as-is, including usage of the payments functionality. The only modifications to be made are listed in the sections below.
5. Any music purchased is downloaded to ~/Music. This directory is set as the default directory for the music player. Downloading new music from the store triggers a rescan.

Changes to the TBD store

1. Remove the Sign In / Sign Out options. The user is always automatically singed in by Ubuntu One. If the user is not signed into Ubuntu One a link to the desktop Ubuntu One Join/Logon dialogue is displayed.
2. Replace the music store logo for the Ubuntu One logo
3. Create an attractive error page for the user to view if the music player loses its internet connection.

Changes to the music player

1. Integrate a web browsing engine
2. Add a link to the Ubuntu One music store
3. Replicate the Play and Download functions from the Songbird store, tie the play function to the standard play/pause, next, previous, etc... controls

Important aspects of customization to consider

• How to initialize the store frame
• Failing quickly to the "cannot connect to store. [try again]" message. No extended timeout.
• Authenticate by injecting cookies into the web browser widget. Or other form of authentication.
• Use SSL.
• In the first iteration, use the music stores credit card processing for payments. Later, integrate with Ubuntu One payments.
• Downloads: Where does music get downloaded to? How are downloads managed from the purchases in the shopping cart? Custom native-widgets frame for managing downloads.
• How to set up a new account? Relationship to Ubuntu One account? Storing credentials locally. Extra terms and conditions?
• Playing previews of songs.

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.

Rationale

This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified.

User stories

Assumptions

Design

You can have subsections that better describe specific parts of the issue.

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

• data migration, if any
• redirects from old URLs to new ones, if any
• how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

CategorySpec