[victorvation]

In my opinion bottom sheets are actually a far superior experience to the previous pattern of dialogs/modals or push screens:

- The user doesn't lose their navigation stack because they can tell the bottom sheet can be dismissed, they know where they "came from"

- The user keeps visual context on whatever triggered the bottom sheet, because they can still see what's behind it

- The user doesn't get forcibly navigated away from whatever they were browsing, they know that once whatever they're doing in the sheet is done, they can "go back".

My only complaint is that Apple added them to stock apps in iOS 12, so many iOS users got used to the pattern, but didn't provide an easy way to give the same experience for developers which creating a need for libraries like this.

[cosmotic]

I'm not defending dialogs or modals, but at least with those (on a larger screen) you have control over what hey cover.

I suspect most users wouldn't even know the bottom sheet is there nor how to bring it up nor how to dismiss it had they brought it up.

The visual context on whatever is underneath is lost once the sheet is brought up.

The user absolutely get forcibly navigated away; their context is shifted to the new layer which is slapped on top of the other layer. I can't count the number of times I either accidentally activated the bottom sheet or used it then got lost.

Bottom sheets are like hamburger menus; they are rugs that UX designers sweep all their baggage underneath.