895394 - [Marketplace][User Story] Marketplace to enable devs to plainly state if an app works offline not counting on the existence of appcache manifest

Status: RESOLVED DUPLICATE of bug 834521

(Marketplace Graveyard :: Validation, defect)

Description

[Marcelino Veiga Tuimil [:sonmarce]]

As an app developer I want Marketplace to enable me to plainly state if an app works offline or not (perhaps in the manifest), independently of the existence of appcache manifest

Comment 1

[Wil Clouser [:clouserw]]

What is the end goal of this user story?  We don't show anything on the marketplace about offline capabilities so we've had no reason to track this.

Comment 2

[Matt Basta [:basta]]

What is this bug supposed to mean? What are we testing for, what are we reporting, and who are we reporting that information to?

Comment 3

[David Bialer [:dbialer]]

The goal of the end user story is to communicate to the Customer of the Marketplace a detail about the app as to whether it can work offline as determined by both an initial check of the manifest Bug 895391 and this bug.  This would create both automated checking with the ability of the Developer to say "you're wrong".

The end goal is to expose this information to end users.

We would like to expose to end users whether an app is available offline.  This is meant to be the dev side of the bug where:
1) app manifest is checked by validator for appcache.
- if used then it tells the developer and indicates that the app should work offline.
- if that is the case, developer can manually overide the default setting.
- if there is no appcache indicated in manifest,  we warn developers, and then have 'can be used offline' deselected. A developer can overide this setting.

2) On the end user side, Bug 861303 and Bug 870367 are filed (maybe Dupes) as they were filed in parralel.  But the intention is to indicate to user, based on 'can be used offline' flag, whether the app is good for offline usage before the user downloads it.  It could be in the app details page, or could be some sort of badge as suggested in Bug 861303.  Up to UX how to communicate this to the end user.

Hope this clarifies.  This is all tying back to Bug 861303 (which was already filed on this) and master theme bug 897779.

Comment 4

[Marcelino Veiga Tuimil [:sonmarce]]

Sorry, I did not see this needinfo because of an issue of my e-mail filter. Fortunately it was clearly explained in comment before. Just to say that it is mainly focussed in developer side.

Comment 5

[Matt Basta [:basta]]

Nothing in this bug that isn't already covered by bug 834521