A modern programming language that makes developers happier.

kotlinlang

Hi folks, have faced a problem with Binder transaction. Having a Single-Activity app entirely based on Compose and utilizing compose navigation, we have many destinations and quite complex screens. Naturally users can navigate between them as they like, even making loops. E.g. user searches for an item and navigates to its details, from where it is possible to navigate to another similar item or even trigger another search, making a back stack grow very fast.

The problem is that every screen has its state, which is saved in the Activity’s Bundle. While user explores the app state Bundle grows very fast beyond Binder’s transaction limit. As a consequence we have thousands of crashes.

As this use case seems to me quite natural, I wonder whether you have any experience dealing with such issue. Any help or advice is highly appreciated.