1109426 - Server side Dashboard for FxOS User to view most used Apps in their country

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[Ravi Dandu]

Create a server side page that shows the most used apps in the user’s geographic area / locale. The apps will be sorted in decreasing usage order, with the most used app at the top.

This will be integrated into FxOS Device side. Corresponding device bug is 1109422.

Comment 1

[Ravi Dandu]

Andy McKay (Marketplace), Dave Zeber(Metrics), Marshall Culpepper (FxOS device), can you discuss and  recommended way to display a link to Most Used Apps. This link will enable end user to be able to access a list of most used apps in their country, and locale. Options:
  a) Link on the device in the privacy description on device
  b) Link on server, in the privacy page description on server
It might be easier for User to access if the link is on device. I'm ok to have it on server if it results in an acceptable user experience, and is easier to maintain, and can make it to 2.2 release.

Comment 2

[Ravi Dandu]

Andy McKay (Marketplace), Dave Zeber(Metrics), Marshall Culpepper (FxOS device), can you discuss and  recommended way to display a link to Most Used Apps. This link will enable end user to be able to access a list of most used apps in their country, and locale. Options:
  a) Link on the device in the privacy description on device
  b) Link on server, in the privacy page description on server
My suggestion is to have the link on device for ease of User access. I'm ok to have it on server if it results in an acceptable user experience, and is easier to maintain, and can make it to 2.2 release.

Comment 3

[Ravi Dandu]

Kevin, Please include into 2.2. This is server side dashboard for Most Used Apps. This server side work provides the User value to ensure Default On for 1109422 (AppUsage Metric collection enhancements for MonthlyActiveUsers computation). Since it is server side, there is more flexibility on the timing.

Comment 4

[Marshall Culpepper [:marshall_law]]

The discussion from today's Metrics meeting concluded in the decision that we're going to use a WebActivity link in Privacy Settings to launch the 'App Stats' view in Marketplace. Andy has filed Bug 1130013, which we'll use for tracking the device side implementation in 2.2.

Dave and Andy have also synced up separately and decided how data will get from the Telemetry backend into Marketplace..

Comment 5

[Michael:mtreese]

added: "blocks: 1131315: to enable tracking on 2.2 dashboard (https://wiki.mozilla.org/Firefox_OS/TwoDotTwoTracking/Dashboard#FxOS_Metrics_.28Michael_Treese.29)

Comment 6

[Hema Koka [:hema]]

Any update on this?

Comment 7

[Ravi Dandu]

The Server side Marketplace requirements have been split up into needs for FL, FC, CC. (Cut and pasted below from the doc https://docs.google.com/a/mozilla.com/document/d/1MwSwXydxRNyZlYe5e45nhZOvVc0EZJBXRZYGlRUhWu0/edit#heading=h.uewz7yqvkqs)

1) For FL Feb 23: 
   Requirement: Create a placeholder app statistics page that echoes back the UA region / locale.
   Status: Screen shot in 1130013. Completed. 
2) For FC April 6th:
   Requirement: Manually generate the list of most used apps for a region with data that was collected between FC and FL on the telemetry server.
   Status: Marketplace team investigating
3) For CC May 18th:
   Requirement: Automatically generate the list of most used apps daily
   Status: Marketplace team investigating.

Stephanie, can you update on the FC and CC request status.

Comment 8

[Caitlin Galimidi [:c8o]]

Ravi - 

2) This is owned by David Zeber on the metrics team, who will work with Marshall to ensure the data from the client is being reflected accurately


3) Marketplace owns the responsibility of building the interface so users can see app usage data. When is the device in market?

Comment 9

[Michael:mtreese]

Removing 2.2+ blocking and moving to backlog per Caitlin's response.

Comment 10

[Caitlin Galimidi [:c8o]]

Notes from our meeting (Treese, Galimidi, Dandu, Culpepper, Hills)


2) David Zeber will work with Marshall C to check that the data from the device into Telemetry is accurate  and geotagged, and that geolocation is sent to page. 

2.1) Marketplace (Stephanie / Andy) will review the data to ensure Marketplace will be able to access / use region and geolocation data 

3) Marketplace to build the interface so users can see app usage data. 
Target date for this work will be determined once the in-market launch date is confirmed: Marketplace does not currently expect to prioritize this work in Q1-2.


If this bug is for the server-side work, should it be assigned to the team who is delivering it and not to Firefox OS? We could reassign to Product : Marketplace, Component : General...

Comment 11

[Shing Lyu [:shinglyu]]

Hi Ravi,

How will the user's geolocation be determined? Will the marketplace page request for user's permission for geolocation data when it opens? Or will it be determined using other methods?

I need this information because we might need an additional step to allow geolocation in test cases. 

Thanks.

Comment 12

[Marshall Culpepper [:marshall_law]]

I think Andy might know more specifics about how Marketplace determines user location / locale.. tagging him

Comment 13

[Andy McKay]

(In reply to Shing Lyu [:slyu] from comment #11)
> Hi Ravi,
> 
> How will the user's geolocation be determined? Will the marketplace page
> request for user's permission for geolocation data when it opens? Or will it
> be determined using other methods?
> 
> I need this information because we might need an additional step to allow
> geolocation in test cases. 

First we look up mcc and mnc to determine their region and carrier. Second we do geoip on incoming requests to figure out the users country. Finally you can fake it by (I believe) passing ?mcc=..&mnc=... on requests, or by typing :debug into the search box (which takes you to https://marketplace.firefox.com/debug) and entering a new region That determines the region. Locale is determined from the HTTP headers.

Since the page doesn't do a whole lot until the data starts coming in, I'm not sure what those tests would look like yet. If you have more questions on that, I'll probably redirect you over the to the WebQA team who would know about faking this to stuff out.

Comment 14

[Shing Lyu [:shinglyu]]

(In reply to Andy McKay [:andym] from comment #13)
Great! Thanks!

Comment 15

[Caitlin Galimidi [:c8o]]

Oops! I moved someone else's cheese! Returning to it's place. 
Please reference bug

Comment 16

[BMO Automation]

Firefox OS is not being worked on