What will be included in tooling sprint:

1. Initial Bitrise integration - get it ready to QA [carryover to following sprint Apr 26 - May 7 2021]
2. Sentry cleanup - prioritize top errors from Sentry (by how often it occurs, and people impacted) [some carryover to v2.3 release in sprint Apr 26 - May 7 2021]
3. Move to node 14.0 [completed; part of v2.3 release in sprint Apr 26 - May 7 2021]
4. User-facing development work: Only high priority bugs will qualify to enter this sprint, NO new feature development/enhancement.[some carryover to the next sprint Apr 26 - May 7 2021]

Detailed plan: https://docs.google.com/document/d/1m1jjCME7f_0j79RCwmRjUPGUb31wJmBBTswU7h0ffQw/edit#

Goals:

Network security fix
Analytics refactor
Swaps velocity, and estimate/project launch timeline

Design:
Review designs for incremental navigation improvements

Goal of MVP: an (internal) user should be able to do a token swap successfully.
https://www.figma.com/file/VVjoLHG6X74lXmh6CN3r7H/Swaps?node-id=608%3A1394

Once this MVP is ready, we'll QA the feature. And then do a second round with added details and improved UX (for which designs are ready)

Goals:

Release v.1.0.6
Send the security update to users in-app

Understand velocity on:
Start Swaps and analytics development
Progress on security PRs & respond to researcher

Design & define:
Kickoff & review design iterations hardware wallet support
Design iterations for incremental navigation improvements

Goals of this Analytics refactor

1. Our current analytics isn't able to give us insights into user flows, conversions, etc., largely due to limitations of the schema we currently have. This limits us in making useful and specific product decisions when looking into current data.
2. Our analytics system between extension and mobile are completely different, and we don't have a good way to compare performance of product across platform. We should also make it easier to maintain high privacy standards across MetaMask products.
3. Implementation is limited to specific platforms MixPanel, Matomo, which has let to lot of re-work (in case of Matomo). This should be made better for long-term.

Proposed solution

1. Proposing an updated schema along with new data architecture that sets good foundation for long-term data-driven product development
2. Segment will be used to gather all user data from various sources. E.g., the mobile application is the source for in-app usage data.
3. Setting up Segment once will be valuable long-term, should we decide to change our dashboard/analytics tool to be something different than MixPanel

Details on Segment setup:

• There are different types of events; screen, track, etc.
• Event data will be used to create dashboards, and metrics (computed from event data) in tools like MixPanel
• Mixpanel will become a tool to visualize and analyze the raw data coming through from Segment
• bigquery will be used as a data warehouse, which could connect data gathered from various sources, using user IDs (anonymously generated)

Project scope Q4 2020:

1. Migrate MixPanel analytics implementation to Segment
2. Update to schema events of priority P1
3. Implementation should be aligned with extension analytics

High level steps of this project:

• A dev to familiarize themselves with https://segment.com/docs/connections/sources/catalog/libraries/mobile/react-native/
• Update SDK of Mixpanel to work with Segment
• Implement Segment SDK
• Update events tracking / schema per https://docs.google.com/spreadsheets/d/1XYj78KAUytJQCKk1fD8pERxXsZRZ6aQhcMP5GJS5X8k/edit#gid=1600734785
• QA and testing