See bugs 738832 and bug 738816. This idea thrown around is to allow the web runtime on fennec native to allow for a special "marketplace mode" to enable operations against the mozApps API to install open web apps. That way, bug 738816 could be successful as an open web application to allow installing of a marketplace application on our platform on android. Additionally, other groups could easily create their own "market" apps to fit their specific needs (e.g. Atlantic Records Web App Store).

This kinda sounds like bug 697309. How much overlap is there?

bug 697309 lands features for the basic app lifecycle similar to web apps integration into desktop. However, I am not sure that the implementation of bug 697309 would allow you to do mozApps API interactions within open web app. For desktop at least, I know that there needs to be additional implementation for this (e.g. special permission and API). Likely by correlation, I'd expect mobile to have a similar requirement. The use case I am thinking about is this: 1. Go to marketplace.mozilla.org on fennec native 2. Select "Install as Open Web App" 3. Launch marketplace open web app on fennec native 4. Search for basecamp in marketplace open web app 5. Install basecamp through marketplace open web app

Myk - Knowing that the proof of concept for Mozilla Marketplace App using WebRT desktop is on the table now, how is this bug affected then for mobile? In other words, if we plan to have a proof of concept marketplace app for desktop, how should the corresponding mobile code handle this?

(In reply to Jason Smith from comment #3) > Myk - Knowing that the proof of concept for Mozilla Marketplace App using > WebRT desktop is on the table now, how is this bug affected then for mobile? > In other words, if we plan to have a proof of concept marketplace app for > desktop, how should the corresponding mobile code handle this? I would treat Marketplace App for WebRT Desktop and Marketplace App For WebRT Android as separate projects. We may end up prioritizing both at the same time, but they are relatively discrete engineering efforts that we can choose to prioritize and develop independently.

Important to note this feature occurs while chromeless is active.

How is this different from bug 738832?

(In reply to Chris Van Wiemeersch [:cvan] from comment #6) > How is this different from bug 738832? Probably should re-word the title. This bug targets fennec native support, the other one targets desktop firefox.

Nominating for k9o - Falls under this user story - https://wiki.mozilla.org/Kilimanjaro/ProductDraft#Mozilla_will_deliver_a_compelling_device.2Fsystem_un-boxing_experience

Myk will figure out what should happen with this.

Jason, Jen, and I discussed this, and it's actually more of a requirement for a part of the runtime that we haven't speced and built yet, so it doesn't make sense to track it as a bug. We'll add to the requirements as we define them and track it as part of one or more feature/enhancement implementation bugs.