A modern programming language that makes developers happier.

kotlinlang

In my app, users perform filtering by tapping a button from a list screen, which presents a modal bottom sheet, inside that bottom sheet is the main filter screen, the user then chooses the category they want to filter by which then transitions the user to that respective screen. Currently we're implementing this by having the bottom sheet have it's own navhost and navcontroller to navigate within the bottom sheet. But I've been wondering if it would be simpler and easier to reason with if this was instead implemented using a pager. All of these nested screens are already sharing a view model in order for changes from screen B to also apply to screen A. Seems like using pager could make sense in this situation, just not sure of the disadvantages.