Dispatching events per page

[danieldanielecki]

Events could've been dispatched per each API's page for performance improvements.

A similar technique has been incorporated in dispatching Ticketmaster events per country: 57a01df. In that case, there are more "refreshes" on the maps while dispatching the events, and those are shown gradually, and the user isn't left with (more) empty maps. For the Ticketmaster events, it was about Europe being completely empty till all events were loaded from APIs. Instead, the maps refreshes per each country-loaded events.

[danieldanielecki]

Use https://github.com/bamlab/react-native-flipper-performance-monitor for monitoring performance and https://github.com/jhen0409/react-native-debugger for debugging while working on this story

[danieldanielecki]

Include also https://rnfirebase.io/perf/axios-integration while working on this story.

[danieldanielecki]

It'll be not done, because rendering is expensive, with splitting actions to separated files in 55e8f93 we gained lots of performance and it was the bottleneck.

[danieldanielecki]

Last piece of splitting actions to separated files improvement in ad566ad has been done.

[danieldanielecki]

Include also https://rnfirebase.io/perf/axios-integration while working on this story.

We don't need to add any extra interceptors because it's just for creating extra metric attributes.
We're good with the default ones, and we can see everything we need: duration, HTTP response codes, network, CPU, etc. in Firebase's Perfomance tab.

[danieldanielecki]

Regarding debugging, even with jhen0409/react-native-debugger#755 (comment) I had a blank screen, but once handling Hermes will be done it can be useful debugger, on top of already existing cmd+D developer tools. As of now, it looks like anything related to debugging in Chrome doesn't work.

Regarding https://github.com/bamlab/react-native-flipper-performance-monitor, little problem was clarified in bamlab/react-native-flipper-performance-monitor#84 (comment), but it wasn't possible to run it.

With those comments, there's nothing more to take a look in this issue. Maybe at some point, it could be helpful to debug, but for now changes related to 55e8f93 can help with performance improvements.