Once we move to a real packaged app (not a packaged iframe), we'll lock down the API to v1. We'll then start iterating versions of the API and fireplace will push out new versions and its all good. Apart from those people who never ever upgrade the marketplace. Eventually we'll want to block those people from using v1. We currently send a deprecation notice in the http headers, http://firefox-marketplace-api.readthedocs.org/en/latest/topics/overview.html#versions Ideally we want: * fireplace to warn users that their version is out of date and needs updating * fireplace to stop working and force an update for users whose version of the marketplace is using APIs that aren't just deprecated, but dead. At this time the API could return a specific HTTP status code for all old responses.

I think there's two things that need to be done: 1. Add a requests.js hook which looks for deprecation headers or deprecation codes and add a handler in marketplace.js for them. 2. When the hook is triggered, divert the user to a deprecation page with instructions on upgrading. The deprecation page can be improved over time, but v1 should provide instructions. A v2 can offer hooks into mozApps to trigger an upgrade.

I added the hook in requests.js. We just need to implement the hook and create the view. The view's creation will likely go hand-in-hand with bug 895474 since it's very much along the same lines.

https://github.com/mozilla/fireplace/commit/3486bdb11f3b1221a0d04327375ea9f04cb884c3 This should trigger a screen asking the user to update. The builder is aborted with a script error and the user is diverted to the "deprecated" view. There is an option to update. 1. If the user is in yule log or in the browser, the button will trigger a refresh. 2. If the user is in a packaged app, the button will trigger a web activity that opens the Settings app to the About page where updates can be done.