Closed Bug 1351555 Opened 4 years ago Closed 4 years ago

PWA: Collect information on the number of progressive web apps that’s added to homescreen

Categories

(Firefox for Android Graveyard :: Metrics, enhancement, P1)

enhancement

Tracking

(firefox55 fixed)

RESOLVED FIXED
Firefox 55
Tracking Status
firefox55 --- fixed

People

(Reporter: wesley_huang, Assigned: cnevinchen)

References

Details

Attachments

(1 file)

No description provided.
Assignee: nobody → cnevinchen
Hi Joe
Please specify what kind of information do you want here.
Do you want to either:
1. When a user clicks "add to home screen", if the website has manifest and it's standalone mode, add the count to UI telemetry.
2. When a users launches a PWA from mobile launcher via shortcut, add the count to UI telemetry.

For 1, I'll wait for bug 1285858's implementation to see if it's possible.
For 2. This is a easier approach. But I guess all the PWA launches are from mobile launcher via shortcut. So I'll just specify the launched PWA is using display:standalone .

Hi Dale
Please correct me if I'm wrong. Thanks!
Flags: needinfo?(jcheng)
Flags: needinfo?(dale)
Comment on attachment 8854784 [details]
Bug 1351555 - PWA Collect information on the number of progressive web apps added to homescreen.

https://reviewboard.mozilla.org/r/126766/#review129412

Note sure if "CONTEXT_MENU" is the best method - Is there any context menu involved? Anyways, code is okay, so r+
Attachment #8854784 - Flags: review?(s.kaspari) → review+
Comment on attachment 8854784 [details]
Bug 1351555 - PWA Collect information on the number of progressive web apps added to homescreen.

I don't know telemetry very well and reusing CONTEXT_MENU seems inappropriate but thats the right place to be counting that, if Sebastian is happy I am.
Flags: needinfo?(dale)
Attachment #8854784 - Flags: review?(dale) → review+
Pushed by ryanvm@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/796b747e3efc
PWA Collect information on the number of progressive web apps added to homescreen. r=sebastian
Keywords: checkin-needed
Priority: -- → P1
https://hg.mozilla.org/mozilla-central/rev/796b747e3efc
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 55
i guess this is already resolved but similar to my comment on the other bug
what i think we can learn from with initial collection are 
- Collect information on the number of Firefox launches using PWA standalone mode
- Collect information on the number of progressive web apps that’s added to homescreen
- Collect information on the number of users using PWA

so it's actually both
1. When a user clicks "add to home screen", if the website has manifest and it's standalone mode, add the count to UI telemetry.
2. When a users launches a PWA from mobile launcher via shortcut, add the count to UI telemetry.

with 1. you can learn how many users add the PWA to home screen
with 2, you can learn how many users actually return to use the PWA
Flags: needinfo?(jcheng)
After landing this bug... there's a question in my head.
How can we separate different PWA users using different display mode when 
1. when they are adding the url to home screen and
2. when they are launcihng a full browser app?

I know we can track the PWA users using "standalone" mode now... 
What if we want to track the number of PWA users with "fullscrenn" mode or without "display" option?
Is there a spec to define "PWA users"?
Flags: needinfo?(s.kaspari)
Flags: needinfo?(dale)
I'm not sure about that. But I guess all of them will have some common entry point? Anyways, Dale will know better. :)
Flags: needinfo?(s.kaspari)
Yeh right now only display: standalone has a designated startup. If you really want to count things that have a manifest that is not standalone during launch. You will need to probably add some metadata into the bookmark around http://searchfox.org/mozilla-central/source/mobile/android/base/java/org/mozilla/gecko/GeckoApp.java#2033
Flags: needinfo?(dale)
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.