Open Bug 1032516 Opened 10 years ago Updated 9 years ago

[project] Developer Submission improvements on Platform/Paid selections (first page)

Categories

(Tracking :: User Story, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: dbialer, Unassigned)

References

()

Details

Attachments

(1 file)

Attached image dev-sub-flow.jpg (deleted) —
Improve the rate of submission successes. Currently about 94% of people who enter the dev submission page exit it without submitting an app. We don't know why, but we do know from developer testing it is confusion. The project is to fix the submission page
Depends on: 969242
I would like to see the problems discovered in Oct 2013 in the Usertesting submission flow fixed. I would like to see our current app submission fixed. I believe we still need to maintain and improve the identified problems. Specifically in the 3-D choice between Free/Paid&In-app, platform selector, form factor selector. The Usertesting.com report completed last October in 2013 clearly illustrated the problem - where developers typically make incorrect choices and spend 5 - 10 minutes (sometimes) trying to figure this out. Can we please fix the current self-service submission flow in the short term. Specifically, remove the Tab-based UI for the mutual exclusivity between Free/Paid, and remove the In-App and Paid from the same choice as in-App may be with BOTH free and Paid apps. So, for instance, the app may be Free OR Paid. Then the app may include or not include In-app payments. Also the packaged/hosted interface is confusing with the tab interface. My understanding of best practices for tab interfaces is to use them to divide content into meaningful sections rather than as a mutually exclusive selector (which is more like a radio button type of selector). So I think the selection process should be: a) select a form factors (multiple select) b) based on above, select platforms (fxos, android, desktop) - multiple select c) select packaged or hosted (mutually exclusive selector) I think this is more straightforward and could save the developer from making incorrect choices. Thanks, David
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: