907418 - [story] - app devs (for preloads) need to sign an additional TOS as part of the online experience

Status: RESOLVED FIXED

(Tracking :: User Story, defect)

Description

[Caitlin Galimidi [:c8o]]

i am an appdev who is submitting an app for consideration to be a preloaded app. i need a way to sign an additional TOS with mozilla

Comment 2

[Caitlin Galimidi [:c8o]]

Karen - 
Do we have the additional TOS form / copy etc?
Can you refer us to it?

Comment 3

[Wil Clouser [:clouserw]]

This is blocking the preloading project

Comment 4

[Christopher Van Wiemeersch [:cvan]]

Can we get an update here? We need some copy.

Comment 5

[Karen Ward [:kward]]

Attachment: Draft language/terms and conditions for an app to be a candidate for pre-loading on a FFOS device.

Comment 6

[Karen Ward [:kward]]

Draft language attached.  Assigning to Mika for review.

Comment 7

[Mika]

(In reply to Caitlin Galimidi from comment #0)
> i am an appdev who is submitting an app for consideration to be a preloaded
> app. i need a way to sign an additional TOS with mozilla

Question on this use case -- in this situation, is the app being submitted for preload directly from the Developer Portal by a developer who has no prior contact with Mozilla? Or has this app developer had prior contact with Mozilla BD, and the preload discussion is occurring in a partnership context.

Comment 8

[David Almström]

Bertand,
can you spread some light of the BD approach to app developers to be preloaded?

Comment 9

[Karen Ward [:kward]]

(In reply to Mika from comment #7)
> (In reply to Caitlin Galimidi from comment #0)
> > i am an appdev who is submitting an app for consideration to be a preloaded
> > app. i need a way to sign an additional TOS with mozilla
> 
> Question on this use case -- in this situation, is the app being submitted
> for preload directly from the Developer Portal by a developer who has no
> prior contact with Mozilla? Or has this app developer had prior contact with
> Mozilla BD, and the preload discussion is occurring in a partnership context.

It could be either.  This is intended to cover both scenarios.  Please share what is driving this question.

Comment 10

[Kevin Ngo [:ngoke]]

The TOS has been merged into the Marketplace repositories.

https://github.com/mozilla/zamboni/pull/1490
https://github.com/mozilla/marketplace-docs/pull/3

Edits and revisions can be made at:

https://github.com/mozilla/marketplace-docs/blob/master/docs/preloaded_apps_terms/en-US.md

Comment 11

[Mika]

Kevin or Wil - Is it possible to collect metrics on how many developers accept the click through Preload terms?  This would be helpful to know on something like a quarterly basis.

Comment 12

[Kevin Ngo [:ngoke]]

The Preload Terms are part of the Preload Submission page. That is, accepting the Terms (a checkbox) is done at the same time as uploading the Test Template and hitting Submit.

https://f.cloud.github.com/assets/674727/1669998/70637f06-5c88-11e3-855e-9b8e6c9084ba.png

With this page, it would be difficult to calculate how many developers stop after reading the Terms. And putting on the Terms on its own page as a separate step may reduce the number of submissions. Is the goal to realize how much friction the Terms cause?

Comment 13

[Mika]

Even though we can't calculate how many developers stop, it sounds like it is possible to track how many developers hit "submit".  Is that true?  This number will be helpful to understand engagement with the program.

Comment 14

[Kevin Ngo [:ngoke]]

Yes, we will have the numbers of submissions on hand.

Though, I think we may have Google Analytics to see the whole flow. Currently, it's multi-step.

1. Click to "Learn about getting your app pre-loaded...".
2. Download a Test Template.
3. Agree to Terms + submit the Test Template.

That may be valuable information as well.

Comment 15

[Mika]

Awesome, this all sounds like good information!

I'm closing this bug since the docs were launched.  It would be cool to revisit in a few months to see how developers are interacting with the automated preload process.

Comment 16

[Mika]

Reopening this to review again.