Looking at usage metrics for Announcement API calls, the Android app is making more than 6 times as many calls for Announcements, per user, compared to the legacy iOS app. When loading the screen that display Announcements, that component appears to flicker, presumably re-rendering multiple times, each times making an API call. The behavior doesn't seem to be completely consistent - an installation might make 2 or 3 calls, or up to 10 calls for Announcements within a few seconds.
Could we make sure that Announcement components are rendered once per screen, ultimately making one API call per screen? This will help us have a more consistent comparison of number of API calls between the Android and iOS app, which we can use to make assessment about the effectiveness of Announcements based on impression rate.
Looking at usage metrics for Announcement API calls, the Android app is making more than 6 times as many calls for Announcements, per user, compared to the legacy iOS app. When loading the screen that display Announcements, that component appears to flicker, presumably re-rendering multiple times, each times making an API call. The behavior doesn't seem to be completely consistent - an installation might make 2 or 3 calls, or up to 10 calls for Announcements within a few seconds.
Could we make sure that Announcement components are rendered once per screen, ultimately making one API call per screen? This will help us have a more consistent comparison of number of API calls between the Android and iOS app, which we can use to make assessment about the effectiveness of Announcements based on impression rate.