dialogTest.kt

// we would be writing this reptitive code multiple times for similar dialogs 
MaterialAlertDialogBuilder(context)
            .setTitle(R.string.confirmation_dialog_title)
            .setMessage(R.string.confirmation_dialog_message)
            .setIcon(R.drawable.ic_feedback)
            .setPositiveButton("Okay") { _, _ ->
                deleteItem()
            }
            .setNegativeButton("Cancel", null)
            .setCancelable(false)
            .show()

// and for the dialog with delay we would also have to do this or create this in a function with delay logic, but if we 
// add this in function then we would have another function to maintain which we may forget later
MaterialAlertDialogBuilder(context)
            .setTitle(R.string.confirmation_survey_dialog_title)
            .setMessage(R.string.confirmation_survey_dialog_message)
            .setIcon(R.drawable.ic_feedback)
            .setPositiveButton("Okay") { _, _ ->
                deleteItem()
            }
            .setNegativeButton("Cancel", null)
            .setCancelable(false)
            .show()            


// much cleaner and also provides simple manageable functionality like delay
showSimpleAlertDialog {
    title = R.string.confirmation_dialog_title
    message = R.string.confirmation_dialog_message
    icon = R.drawable.feedback
    isCancellable = false
    delayMillis = 1000
    positiveButton("Okay") {
        deleteItem()
    }
    negativeButton("Cancel") {
            
    }
}