1040278 - Expose a postMessage based API to allow app management to trusted 3rd party apps.

Status: RESOLVED FIXED

(Marketplace Graveyard :: General, defect, P1)

Description

[Fernando Jiménez Moreno [:ferjm]]

The rationale for this request can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=1008990#c28 and following comments.

Basically, we need the Marketplace to expose an embeddable page probably for certain white listed origins where a postMessage based API can be used to check an app installation and allow the installation of the app if it is not already installed.

Comment 1

[Wil Clouser [:clouserw]]

Please specify the whitelist (including any dev/stage options you'll need). Thanks!

Comment 2

[Mathieu Pillard [:mat]]

We already have something like this: https://marketplace.firefox.com/iframe-install.html (also available on dev/stage) - we'd just need to whitelist another origin.

Comment 3

[Fernando Jiménez Moreno [:ferjm]]

That's excellent news!

I'll defer to Tarek and/or Dan in order to provide the Loop client (standalone UI) URLs.

Comment 4

[Tarek Ziadé (:tarek)]

Marketplace updates occur on Tuesdays - we will provide Wil/Mat the URLs this week so they are added in the train. 

Dan do you mind providing the exact links here ? thx

Comment 5

[Tarek Ziadé (:tarek)]

< clouserw> tarek: freezes happen on friday though, so we'll need the link by then please!

Comment 6

[Dan Mosedale (:dmosedale, :dmose)]

I think this depends on how we end up serving the static content pages in our regular deployment process (eg do we continue to use two separate servers and a redirect?).  My assumption was that this hadn't really been decided, and was actually likely to come up at the meeting on Monday to discuss bug 1042528.  Adding ckarloff for his thoughts here...

Comment 7

[Chris Karlof [:ckarlof]]

Who is in charge of the product production URIs, in particular for the Loop web client? It doesn't matter much how it's deployed.

Comment 8

[Dan Mosedale (:dmosedale, :dmose)]

Some combination of :abr and :RT, I suspect.

Comment 9

[Dan Mosedale (:dmosedale, :dmose)]

To clarify, I think the info needed here is, who owns the "how the production URLs for the standalone link clicker code should look", and what does that owner think they should look like.

After chatting with :ckarlof, his suggestion was that we simply get a judgement call made on this, and then services can figure out how to do the routing as necessary.

Comment 10

[Romain Testard [:RT]]

We discussed this with Aracadio and once we reach Beta (I think before Beta won't apply to this bug) the URL format for link clickers should be implemented as described on https://bugzilla.mozilla.org/show_bug.cgi?id=1046114

Comment 11

[Adam Roach [:abr]]

Clearing my flag here -- this is a PM (RT) and Marketing (Arcadio) decision.

Comment 12

[Dan Mosedale (:dmosedale, :dmose)]

So it sounds like https://hello.firefox.com/ and https://call.firefox.com/ are the origins to whitelist.

Comment 13

[Mathieu Pillard [:mat]]

Added those 2 origins to the whitelist in https://github.com/mozilla/zamboni/commit/f1d77ff5a7e05486d7a929cd66caaa48c0447d53

We'll cherry-pick that into the tag for tomorrow's push.