Discussion on Custom IO Screen Tracking and Navigation Improvement in Flutterflow
In this meeting, the State Changers participants primarily discuss integrating screen tracking to their application using "FlutterFlow" and "Dart" code. The main issue raised is the application not tracking screens and where exactly the Dart code should be situated.
The State Changers suggest two solutions: creating a custom action that runs upon page startup/load to manually record the screen or using the 'Route observer' for auto-tracking. The consideration here is that even though manually recording each page is not scalable, it helps provide a baseline for what success looks like. This baseline can then aid in monitoring how well the more automatic, scalable solution performs when implemented using the Route observer.
Furthermore, it's clarified that FlutterFlow uses the 'Go Router,' and the goal is to determine how well this can work with the 'Route observer'. The complexity of the problem indicates that it might require custom action, possibly tied to the application's lifecycle.
This meeting will be insightful to those interested in tracking screens in an application, working with custom I/O, Dart code, and using FlutterFlow and Go Router for app navigation optimization.