Do hotwire native android apps typically freeze when there are connection issues?

[ibrahima]

Hi! I'm developing hotwire native iOS and Android apps for my company (though funnily for me as a Linux/Android user, we're focused on the iOS app because it's a bigger market in our area - the Android app I have right now is just for my own convenience).

In my experience it seems like the Android app freezes quite a lot when there are network troubles and I end up having to restart it often to get it to respond again. For example, if I navigate back to a view that was previously loaded and my network is spotty, the previous screen is shown but frozen and I can't interact with it, including to pull to refresh. Sometimes I can just hit back again and if the Internet is back the previous view might work.

I don't experience this on iOS. Though my android app is a debug build so maybe that's related? But it feels like regardless, if there is a snapshot of a previous view it should at least be interactive while we check if there's a new version of the page or something.

The other possible confounding factor is that I mostly use the Android app on transit where network cuts in and out on my phone, and since my primary device is Android I haven't used the iOS app under the same conditions. So maybe a similar issue exists there. But either way it feels like a very inconvenient experience and not what I would expect based on how hotwire native shapshots previous views. Though we might have some headers preventing caching some pages so I don't know if that's also related.