Modify the submission flow to match the unbucheted UI

RESOLVED FIXED in 2013-05-16

Status

Marketplace
Developer Pages
P1
normal
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: dbuc, Assigned: chuck)

Tracking

(Blocks: 1 bug)

2013-05-16
Points:
---
Dependency tree / graph

Details

(Whiteboard: p=3)

(Reporter)

Description

4 years ago
Tony and the UX folks have a new submission flow based on app profiling. Please transition the current submission flow to match what the UX team has specified.
(Reporter)

Comment 1

4 years ago
Tony, please link in the final UX/UI specs here.
Blocks: 858314
Priority: -- → P1
The prototype with notes is at http://people.mozilla.org/~asantos/devhubSubmission032013/

I'll have final mocks for the UI after I get back from the workweek, most likely mid-week the week of the 15th, but this should get you started as far as flow and functionality go. It's essentially going to look like the dashboard now, there are just a few layout things and the final icons in the validation and compatibility report that need to be taken care of in mocks.

Updated

4 years ago
Blocks: 862444

Comment 3

4 years ago
This bug encompases both Packaged and Hosted app submission.

https://etherpad.mozilla.org/mkt-buchets
Assignee: nobody → mattbasta
No longer blocks: 862444

Updated

4 years ago
Blocks: 862444
Assignee: mattbasta → dspasovski

Updated

4 years ago
Blocks: 862454
(Assignee)

Updated

4 years ago
Assignee: dspasovski → charmston
Status: NEW → ASSIGNED
(Assignee)

Updated

4 years ago
Whiteboard: p=3
One question that came up in a code review is how we handle app feature selection for packaged apps when the developer is uploading new versions?

If the app features are considered global for all versions developers would need to remember to update their required app features and update them *after* the version is approved or else they're changing the feature set of the currently approved version.

If we include the required app feature checklist during new version upload, we can tie the features to a version and "auto update" them when that version is approved. We can also pre-populate the checklist with the prior version's feature set.

Is this inline with the thinking and current mocks?

Comment 5

4 years ago
(In reply to Rob Hudson [:robhudson] from comment #4)
> One question that came up in a code review is how we handle app feature
> selection for packaged apps when the developer is uploading new versions?
> 
> If the app features are considered global for all versions developers would
> need to remember to update their required app features and update them
> *after* the version is approved or else they're changing the feature set of
> the currently approved version.
> 
> If we include the required app feature checklist during new version upload,
> we can tie the features to a version and "auto update" them when that
> version is approved. We can also pre-populate the checklist with the prior
> version's feature set.
> 
> Is this inline with the thinking and current mocks?

I'm under the understanding that the feature profile for an app is tied to specific versions and isn't global for the whole app. When a new version is submitted and the feature profile changes, the period between submission and approval is going to make it frustrating/impossible to cater to the appropriate users. I.e.: if the developer submits an app update that now requires a feature that many users might not have, they'll have to update their feature profile and exclude all of their current users from seeing their app even though the new version hasn't been approved yet.

Eventually we'll also want the reviewers to be able to modify the feature profile for a version, so that feature will depend on the profile being versioned.
(Reporter)

Comment 6

4 years ago
The profiles should be generated per version, and nothing about the new version and its profile (that may or may not be different) should affect other versions.
+1 to basta and dbuc's comments.
Ok great. I don't recall seeing any mocks changing the new version upload flow. And at the database level we are tracking this against versions so all good there.

Perhaps this is better discussed in bug 862444, which I just discovered.
(Assignee)

Comment 9

4 years ago
Landed behind a waffle switch that is currently enabled on marketplace-dev: https://github.com/mozilla/zamboni/commit/9f75f28d9286697a4980cc8f187b203bd6e2fb8c
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-05-16
(Assignee)

Comment 10

4 years ago
Correction: Queen Krupa is disabling the flag until after the 5/16 push.
Blocks: 875009
typo, obv.
Summary: Modify the submission flow to match the unbucketed UI → Modify the submission flow to match the unbucheted UI
You need to log in before you can comment on or make changes to this bug.