Slow and glitching App Performance on Android Devices

Hi , could you please add a video here or send it to support@bravostudio.app with the performance issues you are mentioning? Apart from that, 408 errors are not device-related: they are "request timeout" errors, so it must be something with your backend

your requests take too long to complete. There's a timeout limit of 3 seconds and that's why you get 408 errors. Regarding the pagination, it's the same issue. Your request to get the next page takes too long, and that's why the loading appears until the request finishes, or it times out. I'll see what can be done in these situations so that we don't show the custom error page when refreshing, but I'm afraid there's not much else we can do if the request is that slow

Could you please send me your Bravo project URL? I will investigate in case there's any issue

I just tested on iOS and as I said earlier, it is not a problem of the platform: you can see in the video that it takes a long time to open your home page, and to refresh that same page. Actually I got 408 errors as well in my first tests with the iOS simulator. Your request takes between 7 and 12 seconds to complete, sometimes even longer. I've taken a look at your app, and in your home screen, you have 9 different requests, so that's the main problem. My recommendation is to try to unify your calls in one, if possible, since you have control of the data you are using. You should notice how everything goes way faster. Another option is to try to split your designs in several pages, since it's not a good approach to show too many data in the same screen anyway.

▶ Video: Simulator Screen Recording - iPhone 14 Pro - 2023-06-08 at 11.29.18.mp4

I had to test in iOS because you told me in this thread, as well as my colleagues in support, that the problem was only on Android and was not happening on iOS. Once I confirmed that the problem happens in both platforms, I explained what the issue was in my previous message: your home page is using 9 different requests in the same page. My recommendation is to try to unify your calls in one call, if possible, since you have control of the data you are using. You should notice how everything goes way faster. Another option is to try to split your designs in several pages, so that there's not that many requests in the same page.

As already tried to explain, the issue is not specific to the platform but due to the page architecture used and this is affecting the whole page performance: to fulfill all data required and render your page, all the requests needs to be processed correctly, if 1 gives an error or experiment any slowness issue the whole page returns in an error.  
Also, bear in mind that even if requests are executed in parallel whenever possible, the whole page performance is affected and also because you will have more points of failure. 
So, short answer "Multiple requests" is a great feature but is good practice and common sense to use secondary requests only when is not possible to unify them (eg. having requests from different api servers, or if one request returns paginated data).