Material3 Full-Screen Dialogs

[eltos]

From the Material3 Design Guide:

Dialogs can require an action, communicate information, or help users accomplish a task. There are two types of dialogs: basic and full-screen.

Proposed method signatures

SimpleDialog.build()
            .title(R.string.hello)
            .msg(R.string.hello_world)
            .fullscreen() // or with true/false argument to en-/disable
            .show(Activity.this);

Links

• https://m3.material.io/components/dialogs/overview
• https://medium.com/alexander-schaefer/implementing-the-new-material-design-full-screen-dialog-for-android-e9dcc712cb38

[mtotschnig]

Shouldn't the argument default to false? For me, I am not sure if this adds value to this library, Given the requirement of a screen that should always appear fullscreen, I would probably not use a dialog fragment, but a standard fragment, or an activity.

[eltos]

I meant that .fullscreen() is equivalent to .fullscreen(true), of course the default without that call is a standard pop up dialog.

@mtotschnig So you don't think the simple API of this library and it's features like the form dialog would make using it preferable over designing and implementing a new fragment or activity from scratch?

[mtotschnig]

So you don't think the simple API of this library and it's features like the form dialog would make using it preferable over designing and implementing a new fragment or activity from scratch?

It probably depends on the use case. I think the simple API has its advantages for simple dialogs that I would want to render as a dialogue not full-screen. The advantage of using an activity is that the data can be passed in a type-safe way with Androidx Activity Result Contracts.