(both apps teams will need to agree on the instrument_name for this.)

let's use apps-open for the instrument name

@SNowick_WMF
Could we also be more precise about what we mean by "app open"? The app has a number of different screens, each of which handles different tasks, each of which can be "opened" independently of each other.
To run through a few examples:

• Reading articles: If the user is browsing the web in the Chrome app, then taps a Wikipedia link, which causes the app to launch and view the article, presumably that's an app_open? And then the user switches back to Chrome, putting our app in the background (but very much still running), then later taps another Wikipedia link, bringing our app back to the foreground, is that another app_open?
  • So then, are we saying that we should send an app_open event whenever we handle an incoming link from an external app?
• Widgets: Are we saying that we should send an app_open event whenever a widget causes the app to show a particular screen, regardless of which screen it is, and regardless if the app is already running?
  • Same for App Shortcuts.
• Notifications: Tapping on a push notification can open various screens of the app, depending on the type of notification. Is each of those a potential app_open?
• Home screen: Tapping on the actual app icon on your phone's launcher screen opens the Main screen. I'm guessing that's also an app_open.

....or are we talking about sending an app_open event whenever any screen of the app comes to the foreground, for any reason? If I'm reading an article, then switch over to TikTok, then switch back to our app, is that an app_open?

Thanks for feedback @Dbrant - added sources to main task

cooltey opened https://github.com/wikimedia/apps-android-wikipedia/pull/6576

Hi @SNowick_WMF

There's feedback from code review:

This one is kind of confusing: When exactly does this get fired? For what kinds of situations? If it gets fired whenever any activity receives a new Intent, then why is it called "background"?

Reading the task, it says the following for background:

If the user switches back to Chrome, putting our app in the background (but very much still running), then later taps another Wikipedia link, bringing our app back to the foreground that is another app_open.

...But isn't this already handled with the external_link event? What is this adding?

It looks like the background event is not clear in the app behavior. Do we want to only do for external_link when it's coming from the deeplinks? If we are also thinking about widgets or notifications, then we can keep this background event; if not, I would suggest removing this background event since it will be a duplicated event as the external_link.

dbrant closed https://github.com/wikimedia/apps-android-wikipedia/pull/6576

Hi @ABorbaWMF
Please set the Event Platform intake base URI to Beta and stream the following schema:
https://stream.wikimedia.beta.wmcloud.org/v2/ui/#/?streams=product_metrics.app_base