834794 - [Story] Master Tracker for Supporting Application Stubs

Status: RESOLVED FIXED

(Tracking :: User Story, defect)

Description

[David Bialer [:dbialer]]

Application stubs will be used as placeholders for uncompleted applications for B2G.  Their function is to save spot on the phone grid for the application and enable the application to update when an update becomes available.  They are essentially version 0 of an application and may be hosted or packaged.

These application stubs may never be used by the end user if the phone grabs the update during it scheduled update before the end user ever opens the app stub.

As a backup plan for a pre-loaded application that doesn’t make it into the shipping product, Mozilla should provide a stub application for each designated app that will behave as described in the stories.

Comment 1

[David Bialer [:dbialer]]

With these changes, the flow for a self-initiated stub update (with some additional detail about the interactions between the stub and the system that may be useful) would be:

    placeholder packaged stub app placed onto device at build time
    customer opens stub
    if network unavailable, stub prompts customer to connect (customer connects; device notifies stub about connection)
    stub triggers update check
    system initiates update check
    [Marketplace] serves minimanifest
    system downloads and processes minimanifest
    system notifies stub that update is available
    stub prompts customer to update (customer confirms)
    stub triggers download
    system initiates download
    [Marketplace] serves update
    system downloads update
    system notifies stub that update is downloaded
    stub quits
    system installs update
    system notifies customer that update is installed
    customer restarts app
    customer uses app


While the flow for a stub update initiated by the system would be something like (not sure of the details, especially around the customer prompts):

    placeholder packaged stub app placed onto device at build time
    system initiates update check
    [Marketplace] serves minimanifest
    system downloads and processes minimanifest
    system prompts customer to update (customer confirms)
    system initiates download
    [Marketplace] serves update
    system downloads update
    system installs update
    customer starts app
    customer uses app


-myk