833273 - [Marketplace] Size of downloaded apps not displayed in market place

Status: RESOLVED INVALID

(Firefox OS Graveyard :: Gaia, defect)

Description

[Leo]

1. Title : Size of downloaded apps not displayed in market place
2. Precondition : Wifi connect
3. Tester's Action : Idle - Marketplace - Select business -   Download  Wified.com App - Displey "Install  wified .com  ? Pop-up"
4. Detailed Symptom (ENG.) : When the permission poup displays, the size will be displayed as "Unknown".
5. Gaia Source Version : a03f7b532e9998e646d55f93a0fc03a04d7ca7d9
6. Expected : The size of the application should be displayed.
7.Reproducibility: Y
1)Frequency Rate : 100%
8.Comparison Results : 
1)Model Comparing : 
9. Attached files: 
1)Log : 
2)Test Contents : 
3)Video file :

Comment 1

[Jason Smith [:jsmith]]

Invalid. That's expected behavior. When we don't know the size of what we're downloading, we list unknown. That will happen with apps that are hosted or packaged apps when there's no size specified.

Comment 2

[Leo]

In case if size is unknown, shouldn't we remove the size field from the display. It doesnt make any sense to display the size as unknown.

Please know your opinion.

Comment 3

[Leo]

My suggestion is in case of hosted applications. In that case the size field is not mandatory. Hence cann't we display or hide the size field in the confirmation popup depending upon the presence of the field in the manifest file.

IMO displaying the size field as "unknown" to end user is not a good option.

Comment 4

[Jason Smith [:jsmith]]

Redirecting to Josh on that one.

Comment 5

[Josh Carpenter [:jcarpenter]]

(In reply to leo.bugzilla.gaia from comment #3)
> My suggestion is in case of hosted applications. In that case the size field
> is not mandatory. Hence cann't we display or hide the size field in the
> confirmation popup depending upon the presence of the field in the manifest
> file.
> 
> IMO displaying the size field as "unknown" to end user is not a good option.

"Unknown" was indeed specified in the original specs, but we also said "verbiage to be decided", so we were never very strongly attached to it. I agree that the word "unknown" could create a negative impression in the of the user, potentially discouraging them from completing their install. I'm fine with hiding the field when we don't know the size.

Comment 6

[Jason Smith [:jsmith]]

Fair enough, sounds like this is a valid bug then.

Comment 7

[Wayne Chang [:wchang]]

Triage 4/12 - leaving Leo? as probably not part of the build but is a concern from the end user experience.

Comment 8

[Jason Smith [:jsmith]]

(In reply to Wayne Chang [:wchang] from comment #7)
> Triage 4/12 - leaving Leo? as probably not part of the build but is a
> concern from the end user experience.

No, this is part of the build. What this bug is about is basically requiring that in the case of installing an app where we do not know the size, we shouldn't display unknown - we display nothing.

FWIW, I do not think this blocks either unless UX thinks otherwise. This is polishing the UX here and not a critical UX fix either.

Comment 9

[Lukas Blakk [:lsblakk] use ?needinfo]

No matter whether 'unknown' or nothing displayed, this is not a blocker, but in triage we had a discussion about needing to be careful with these types of decisions - if we want the user to know there *is* a cost to an action, the original plan to show an "unknown" meets that better than absolute silence.

Comment 10

[Jason Smith [:jsmith]]

(In reply to [e-mail] from comment #9)
> No matter whether 'unknown' or nothing displayed, this is not a blocker, but
> in triage we had a discussion about needing to be careful with these types
> of decisions - if we want the user to know there *is* a cost to an action,
> the original plan to show an "unknown" meets that better than absolute
> silence.

Correct. That might have been the original rationale for keeping "unknown" displayed here.

Comment 11

[Dylan Oliver [:doliver]]

Leo, please see comment #9 for reasoning on why we think it is not a good idea to remove the size value. Does this make sense?

Comment 12

[Leo]

Dylan, The reasoning completely make sense for using "unknown" as the size for hosted applications. I agree using the same in case of unspecified size in manifests.

Thanks for responses.