In the Firebase Analytics library, the recommended debugging method is to set a property with ADB to log all the events to logcat. Luckily, most analytics libraries (including Firebase) have different solutions for this problem. However, when implementing these client events, it’s often helpful to have a quick feedback loop to ensure that the event and associated payload are correct, without having to check an analytics dashboard (which can often take some time to refresh). In order to measure that, we often turn to analytics libraries (like Firebase Analytics) to handle this in-app behavior reporting. The ProblemĪs most apps grow, there becomes a need to measure app usage and engagement to better understand user behavior. As an example, I’d like to go through building a custom plugin for Flipper, similar to one that I’ve used on my own projects, that demonstrates how easy it is to get started building these tools. However, there are often times that you’ll need a tool more specific to your own workflow that Android Studio doesn’t provide, and that’s exactly where Flipper’s extensibility really shines. Since then, Android Studio has come a long way adding tons of features like a new Logcat and Layout Inspector. A long, long time ago, I wrote a blog post about how I was using Flipper as one of my favorite development tools.
0 kommentar(er)
