Closed Bug 870374 Opened 11 years ago Closed 9 years ago

[Everything.me][User Story] Everything.me could provide some statistics about apps using app cache

Categories

(Firefox OS Graveyard :: Gaia::Everything.me, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: noemi, Assigned: joey)

References

Details

(Keywords: feature)

As an OWD developer I want everything.me statistics about apps using app cache, so that we can evaluate what we should focus on

Acceptance Criteria: 
*For example, it could be via a web portal or by sending a periodic e-mail with the statistics
Blocks: 870362
Keywords: feature
Flags: needinfo?(ran)
Hey Noemi, our DB has an enormous amount of apps indexed and most are from the wild.
A few of them though, mostly html5 games we've helped develop, use appcache and we can list them for you.

IS it still relevant?
Flags: needinfo?(ran)
Yes, thanks, if you can provide a way we can see these data, it would be helpful for us
As far as I know, we are using some apps that have appcache, like wikipedia or accuweather. So, do you mean everything.me search does not look for apps with appcache (or do not care)?

We need the statistics to know if appcache usage is spread widely enough to dedicate more effort improving this kind of apps.
We have a special system that probes mobile web apps and sites and collects signals, which include app cache support. 

When we ran it on the top 1 million websites the % of sites supporting app cache was negligible. We also ran it on e.me index and the results weren't promising there as well. 

I can try and look the data up, if that can be helpful.
It would be useful if you can share with us the numbers, both percentage & absolute numbers. Thanks!
Assignee: nobody → joey
Mass update: Resolve/Wontfix all existing collections bugs as this feature is now removed.

Please re-open or file a new bug if you feel that this bug still exists in master.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.