Sending event with Google Analytics for Firebase to support data-based decision-making

When operating an app service, it is important to properly send events such as user operations and screen transitions, and to have a system in place to analyze data. However, we must be careful when implementing event sending. If implemented improperly, necessary data for analysis may be lost, making effective decision-making difficult. This session will explain the following to Android engineers who are starting to develop new Android apps or who want to strengthen their data analysis in the future. Specifically the technologies covered will be Google Analytics for Firebase and BigQuery. Through this session, I aim to increase the number of Android engineers who can accelerate business contributions from the perspective of data analysis. - Explain as preliminary knowledge how events are stored in BigQuery and what SQL and tools can be used to analyze them - Make combinations with back-end data possible by properly setting the user ID associated with events at user registration, login, logout, and account deletion - How to send screen transition events for each screen transition methods - Activity, Jetpack Navigation, and Compose Navigation - Put in place a system to match event names on iOS and Android (introduction to a solution using code standardization and automatic code generation with Kotlin Multiplatform). - Create a mechanism to prevent event sending implementation from being omitted (introducing a solution using Konsist and detekt). - Build a structure for communication about data analysis methods with non-mobile engineers such as PdM. (Translated by the DroidKaigi Committee)

• 

  Haruhiko Takada 株式会社Kyash, Androidエンジニア