../../Personas/Mike learns about a new app, and wants to install it.

Primary story

1. ../../Personas/Mike opens the Dash to search, and enters the first part of the app's name, "foo". The Dash is already showing a list of results, which includes the app that ../../Personas/Mike is looking for.

   • The Dash queries the package index using ../../Interfaces/ClickPackageIndex. Query results include URLs for icons, but icons are fetched separately.

     • Are package descriptions actually needed in these results?

2. ../../Personas/Mike taps the app to preview it.

   • The Dash fetches package details using ../../Interfaces/ClickPackageIndex, which inludes the sames information as query results.

   • Ratings and reviews are fetched from where?

3. Seeing that it is well-rated and free, ../../Personas/Mike taps the Install button.

   • The Dash gives the package name to the package downloader (how?).

4. While the app is downloaded and installed to the device, the screen updates to show progress, then finally an Open button.
   • The downloader fetches the package in the background and then installs it.

   • The Dash monitors download and installation progress how?

Variation: Recommended app

Instead of searching in the Dash, Mike sees an interesting app recommended to him in the App Lense.

Variation: Paid app

The app costs money, but the amount is reasonable. ../../Personas/Mike taps the Install button, and then what?

Variation: Double-tap from results, free app

The screen updates to show progress and completion, but no open button in the current view.

Variation: Double-tap from results, paid app

What happens?

Variation: 3rd-party app

../../Personas/Mike downloads or copies a click-package to his device, and then....