| JTannerWMF | |
| Jun 29 2021, 4:36 PM |
| F34536340: Android_Notification_Prefs.png | |
| Jul 2 2021, 10:42 PM |
Background:
As detailed in T285775, we will establish a baseline for notification engagement in the Android app. Our existing schema has incomplete data, as seen in this spreadsheet.
In order to answer our research questions we need an updated schema that tracks both state and changes related to notifications.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Feature | JTannerWMF | T285765 [EPIC]Improve Notification Discoverability | ||
| Resolved | SNowick_WMF | T285775 Establish baseline for Q1 Notifications project metrics | |||
| Resolved | SNowick_WMF | T285779 Create new schema to track state and changes related to notifications | |||
| Resolved | SNowick_WMF | T286573 Update MobileWikiAppNotificationInteraction Schema to capture current notification event data/interactions |
Current schema MobileWikiAppNotificationPreferences is outdated and missing current Notification Preference options in tracking.
The proposed solution has 2 parts: 1. Implement a schema that tracks user preference change events and 2. Implement a user state schema (or add to existing schema) . This structure follows the iOS app data organization that uses 2 tables: MobileWikiAppiOSSettingAction and MobileWikiAppiOSUserHistory to track user state for all users and user change events. (See https://phabricator.wikimedia.org/T192819 for further documentation.) Will track decisions and next steps here. The first phase of this schema architecture will be for Notifications with the second phase moving all user Settings/Preference tracking to these schemas).
Current Notification Preference Settings (need to be added to new UserSetting schema):
UserSettings will track changes to these settings and UserState will track all users/setting states when user logs in/opens app.
