Implement consumer app detail page

RESOLVED FIXED in 6.4.8

Status

defect
P1
normal
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: clouserw, Assigned: potch)

Tracking

unspecified
6.4.8
Dependency tree / graph

Details

Attachments

(2 attachments, 2 obsolete attachments)

more details on monday!
Posted image details-page-phone (obsolete) —
Posted image details-page-tablet (obsolete) —
Comment on attachment 604558 [details]
details-page-tablet

Looking good! I do like these designs. I have a few questions that need to be addressed before we begin implementation:

* The pages will be designed responsively that's a given. But is the Tablet design intended to also be the Desktop design? Are there any other considerations we need to make for Desktop?
* Is only Category allowed per app?
* Where do we show Weekly Downloads?
* Reviews/Ratings: Are we not showing these for this iteration of the design?
* Does the Developer / Organization link to the Developer Profile and/or User Profile?
* There is a Description but not Summary. ("description" is a field in the manifest but summary [a 250-characters-or-fewer description] is not.) Are we forgoing the Summary, or are they the same thing now?
* How do we determine the order of the screenshots & videos? Screenshots first then videos, or vice-versa? Or do we offer some way to list the order from the management pages? (Currently, Screenshots and Videos are two different groups of form fields in the Edit Listing pages.)
* If I'm the developer of this app, where is there a button to "Manage My App"?
* We have a field for Developer Comments ("Why did you make this app?" and "What's next for this app?"). Is that used anywhere on this page?
* There are links for App Support and App Homepage.
    - Privacy Policy is a required field, so should we add a link to that in this Developer Contact Information section?
    - Support Email Address is an optional field during submission/management. Should we add that here as well?
* Do we allow developers to access this details page even if his/her app is pending approval to the Marketplace? And if so, how do we make that clear to the end user? (A proposal for implementing this on AMO can be found here: https://bugzilla.mozilla.org/show_bug.cgi?id=720898#c10)
* What about Version Number, Date Submitted, or Date Updated? Do we care about listing these?
* Where are there links to Report Abuse for an app?
* What about App Statistics? Is this in scope for the launch, and if so where do we expose a link to view stats?
* Is there such thing as a "Featured" App? And if so, how do we denote that on this page?

Global Layout:
* Where is there an option to switch my language?
* Where are there links to View My Purchases, Log Out, Edit User Profile/Account Settings, Change Password - or access Admin Tools or Editor Tools?
* The Developer/Organization for this app is a company/person name (e.g., "Electronique Arts") but the user is shown to be "appuser@example.com". Are we forgoing usernames? Or are we requiring a company/person name (and email) for every (developer) account?
* The "Tabzilla" Mozilla logo should be at the top of the page. (See bug 726853 for details or view it on marketplace.m.o) Did we want to hide this on Mobile/Tablet?
* Is the site search based on autocompletion?
(In reply to Chris Van Wiemeersch [:cvan] from comment #3)

> * We have a field for Developer Comments ("Why did you make this app?" and
> "What's next for this app?"). Is that used anywhere on this page?

To clarify, these are Developer Comments: https://addons.mozilla.org/en-US/firefox/addon/flashblock/#developer-comments

And this is a Developer Profile: https://addons.mozilla.org/en-US/firefox/addon/flashblock/developers
We're going to talk about it on Monday.  Good notes though. :)
We also need a way to show if the user is logged-in or not (cvan mentions this under 'Global layout'  mentions this but I just wanted to be sure we don't forget it).
If the app is part of Collection/Magazine, do we indicate that in the detail page in any way?
Depends on: 721931
http://clarkbw.net/tmp/bootstrap2/apps/details.html is the hi-fi look/feel we're aiming for
awesome comments! I'll try to address issues here and then will update the ia design

(In reply to Chris Van Wiemeersch [:cvan] from comment #3)
> Comment on attachment 604558 [details]
> details-page-tablet
> 
> Looking good! I do like these designs. I have a few questions that need to
> be addressed before we begin implementation:
> 
> * The pages will be designed responsively that's a given. But is the Tablet
> design intended to also be the Desktop design? Are there any other
> considerations we need to make for Desktop?

Right now we're going to keep using the tablet UI for the Desktop version and as it makes sense we'll start developing a better version of that

> * Is only Category allowed per app?

I'm not sure about this.  But it does look like we left out the app category from this view.

> * Where do we show Weekly Downloads?

We're leaving that piece out for now but will likely add it in later.

> * Reviews/Ratings: Are we not showing these for this iteration of the design?

No not yet.  This is just about the purchase and install flow for users.

> * Does the Developer / Organization link to the Developer Profile and/or
> User Profile?

We wanted to link to the Developer web page and possibly the contact data for that developer.  Not linking to the internal developer page.

> * There is a Description but not Summary. ("description" is a field in the
> manifest but summary [a 250-characters-or-fewer description] is not.) Are we
> forgoing the Summary, or are they the same thing now?

Yes, we're forgoing the summary for now and just going with the description field.  Also cutting it off to about 280 characters and creating a (v) read more button for expanding that.

> * How do we determine the order of the screenshots & videos? Screenshots
> first then videos, or vice-versa? Or do we offer some way to list the order
> from the management pages? (Currently, Screenshots and Videos are two
> different groups of form fields in the Edit Listing pages.)

Videos first, then screenshots though we need to limit the numbers on these.  1 or 2 videos might be the max and then some set of screenshots.

> * If I'm the developer of this app, where is there a button to "Manage My
> App"?

We don't have that yet but I'll look into some way of handling that.

> * We have a field for Developer Comments ("Why did you make this app?" and
> "What's next for this app?"). Is that used anywhere on this page?

This could live under the "read more" link that expands the description field but we're trying to limit the initial space needed for a phone.

> * There are links for App Support and App Homepage.
>     - Privacy Policy is a required field, so should we add a link to that in
> this Developer Contact Information section?

Yes, that makes sense to me.

>     - Support Email Address is an optional field during
> submission/management. Should we add that here as well?

Yes!

> * Do we allow developers to access this details page even if his/her app is
> pending approval to the Marketplace? And if so, how do we make that clear to
> the end user? (A proposal for implementing this on AMO can be found here:
> https://bugzilla.mozilla.org/show_bug.cgi?id=720898#c10)

I'll take a look at that and get back to you.

> * What about Version Number, Date Submitted, or Date Updated? Do we care
> about listing these?

Not version number or updated date.

Submitted date could possibly make an appearance at the end by the support links. I'll look into it.

> * Where are there links to Report Abuse for an app?

We should likely put that with the support links.

> * What about App Statistics? Is this in scope for the launch, and if so
> where do we expose a link to view stats?

Not yet, we're focused solely on the flows for app purchase, install, uninstall, and refund  right now.  This details page actually only handles "purchase/install" as if you just arrived from any direction and wanted to purchase/install it.  We'll likely want to add these other points you have when we're focused on app browsing flows.

> * Is there such thing as a "Featured" App? And if so, how do we denote that
> on this page?

Yes, another good point.  We don't show that on the apps detail page right now but again when we're going through the featured page flow we'll need to add that.

> Global Layout:
> * Where is there an option to switch my language?

Will be at the bottom.  I'll get back to this.

> * Where are there links to View My Purchases, Log Out, Edit User
> Profile/Account Settings, Change Password - or access Admin Tools or Editor
> Tools?

Many of those will likely be at the bottom.  I'll start adding them as they are a part of the flow we're working on.

> * The Developer/Organization for this app is a company/person name (e.g.,
> "Electronique Arts") but the user is shown to be "appuser@example.com". Are
> we forgoing usernames? Or are we requiring a company/person name (and email)
> for every (developer) account?

Good question.  I was assuming that every organization had some main email address contact point.  I could use some pointers on what kind of information we have about that.

> * The "Tabzilla" Mozilla logo should be at the top of the page. (See bug
> 726853 for details or view it on marketplace.m.o) Did we want to hide this
> on Mobile/Tablet?

Yeah, it's too much for the mobile phone.  Might be possible on the Tablet.  bug 725068 shows a lighter version of tabzilla we might use.

> * Is the site search based on autocompletion?

Yes, I assume so.  What are the implications you're thinking of there?  For mobile phones we're planning to take you to the search results page to show suggestions; possibly similar for tablets.

(In reply to krupa raj 82[:krupa] from comment #6)
> We also need a way to show if the user is logged-in or not (cvan mentions
> this under 'Global layout'  mentions this but I just wanted to be sure we
> don't forget it).

Right, this will be part of the footer area.  When running inside the Platform (WebRT) it's assumed you'll be signed in already so it's not so much of an issue.  When the site is running in a browser we can try to evaluate other ways to make it more obvious for developers.


(In reply to krupa raj 82[:krupa] from comment #7)
> If the app is part of Collection/Magazine, do we indicate that in the detail
> page in any way?

Yes, we'd indicate that on this page but AFAIK we're pushing collections back in priority to finish just the purchase and install flow first.
Gotta start somewhere...

https://github.com/mozilla/zamboni/commit/0816388
Posted image details-phone
Bryan updated the mockups for the feedback here.  Minor changes, so I'm adding them to this bug.  If you can't get them in this week focus on what you can from the old mocks still.
Attachment #604557 - Attachment is obsolete: true
Posted image details-tablet
Attachment #604558 - Attachment is obsolete: true
Depends on: 736190
Depends on: 736256
Depends on: 736257
Bryan, on the footer of every page on AMO/Marketplace we have links to Privacy Policy, Terms of Use, and Report Trademark Abuse. Are we going to have links to these for the mobile, tablet, and desktop views? And if so, where?
Depends on: 736621
Target Milestone: 6.4.6 → 6.4.7
Depends on: 738088
(In reply to Chris Van Wiemeersch [:cvan] from comment #13)
> Bryan, on the footer of every page on AMO/Marketplace we have links to
> Privacy Policy, Terms of Use, and Report Trademark Abuse. Are we going to
> have links to these for the mobile, tablet, and desktop views? And if so,
> where?

Yeah. we'll probably need to have them in the footer again.
Depends on: 738707
Target Milestone: 6.4.7 → 6.4.8
Implementation for this page is done, waiting on final visual designs for snazzification
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Depends on: 742902
Depends on: 742905
Depends on: 744641
No longer depends on: 744641
Depends on: 745332
No longer depends on: 745332
Depends on: 745338
Depends on: 745346
Depends on: 746402
Depends on: 748287
No longer depends on: 742902
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.