Our Audience:

Our audience for the Manifest Builder is not the expert developer. Though experts could use the Manifest Builder, they're more likely to have their own processes/tools and be comfortable with creating the manifest as a file.

 

We're focused on the developer with a bit of experience. For example, a

mobile developer who's starting to build Open Web Apps. These people

need more help and hand-holding to produce an accurate manifest file

that passes validation.

 

Two goals for this Manifest Builder:

1. Use pathing to display only the fields that are relevant to Hosting vs Privileged apps

2. Help developers understand the meaning and impact of Manifest fields. Hoping that the result is that more people use the fields relevant to their apps and avoid submission failures.

 

Keep these notes handy while reviewing the prototype.

Right button launches prototype in a new window.

If you get stuck somewhere and want to start over, click the Marketplace logo.

 

General

Hover over fields to see additional Help content.

 

Page 1

Choose Web or Privileged.

Launch Path is required for Privileged. All other fields are the same for both types.

128x128 icon is required for both. Other icon sizes can be added later.

Character counters and max char count alerts work on this page.

 

Page 2

Launch Path appears for Hosted, but not for Privileged (it was completed on Page 1).

Appcache appears for Hosted, but not for Privileged (it's not applicable).

Click + Another Location to see example of how to add multiples for a field.

 

Page 3

For Privileged, Origin appears on this page. It's not applicable to Hosted, so doesn't appear.

 

Page 4

Page only displays permissions applicable to the type (Hosted or Privileged). They are grouped logically. Wording of permissions is WIP - need to learn what each is/does to reco best language.

Click + Another Language to see another example of how to deal with multiples in a field.

 

Page 5 

Activities and Messages

 

Page 6

For Privileged, page displays Redirects, which are not shown for Hosted Apps (not applicable).

 

Page 7

Displays output of completed Manifest. Content here is just for show, so you may not see content/choices you made earlier in the prototype. But will see a difference between Hosted and Privileged.

 

User can edit here - will work out interaction later, but probably popup. On save, Manifest would be

re-generated and output again on Page 7.

 

Moving Forward

We're planning some testing to understand how this compares to the existing DIY manifest. Following that, this version can be built for use right now. Links to this tool would be placed in various areas on Devhub, e.g., on the 1st page of the submission flow, inside the App Details, etc.

 

As we work on/finalize the 2 new concepts, we'll be considering how this Manifest Builder could evolve. E.g., rather than downloading the file, the user could "submit" the file to Mozilla right then, and it would be stored somehow until the user officially submits the app for review.

 

 

Devhub Pages Redesign - Manifest Builder

Start Here