As a product owner, I'd like the opportunity to convert a non-Firefox link clicker users to a Firefox browser download once they have ended a Loop call. As a user, I'd like to have the ability to generate video calls on Loop so that I can invite my connections to a video call

Hi Darrin, could you please confirm if this could be done in the call terminated/feedback form screen from a UX standpoint?

(In reply to alainez from comment #0) > As a user, I'd like to have the ability to generate video calls on Loop so > that I can invite my connections to a video call Sure, we could add a CTA in the call ended/feedback screen for link-clickers. Though, I'm not sure what the above story refers to... "generating video calls for my connections" seems unrelated?

I assume Arcadio meant to say that by downloading Firefox users have will have the ability to "generate a call-back URL" themselves

putting to mozilla35 until the User Story make sense - right now there are 2 user stories. Before putting back in mozilla34 ask Maire, Shell, or RT - both scenarios sound nice to have for Fx34 (after a good product experience).

> Component: Client Isn't this a server-side page? AFAIK there is no Loop client outside of Firefox so how could we provide such UI on a client we don't have code running on?

(In reply to Matthew N. [:MattN] from comment #5) > > Component: Client > > Isn't this a server-side page? AFAIK there is no Loop client outside of > Firefox so how could we provide such UI on a client we don't have code > running on? We have code that's called "Standalone Client" or "Link Clicker". Although this is a Web UI that is hosted, its code lives in browser/components/loop/standalone (and some in loop/content/shared). We're treating the desktop and standalone client bugs as belonging to the client product. The server code is the rendezvous server at https://github.com/mozilla-services/loop-server.

Considering features on the 35 list and design requirements already being considered (and the [loop-uplift] tagged work that is going into Fx34 Beta) - moving this out to at least Fx36 (requires design updates).

will reconsider when the language is here for what marketing would like - then can put up for UX design. until then putting on back-burner of backlog.

This is also being discussed on: https://bugzilla.mozilla.org/show_bug.cgi?id=1108884 Marking resolved for now.

Lets mark it as duplicate then - we didn't actually fix anything here.