Custom dialog takes time to show up

Question

When I implement a custom dialog by using AlertDialog.Builder or DialogFragment which has a fairly complex layout (like this one) the dialog takes time to show up. But when the dialog just contains a couple of editText or so... there is no issue in showing up of the dialog. Why is it so?

Is it that the AlertDialog framework is used to build dialogs that are used just to alert the users? (as the name implies.)

Are there some other frameworks that can be used to implement complex custom dialogs?

I have tried the following things to fix the issue:

Attempted to implement threading so that my dialog is ready in a background thread and show it when I want. But this is not allowed in general as any other thread except UI thread aren't supposed to touch UI related events.
Made the dialog a global variable, initialized it in onCreate and then show the dialog onButtonClick.
Switched to CONSTRAINT LAYOUT
Used an activity as a dialog by setting the dialog theme to the activity in the manifest file.

I am extending to this question. Any help would be highly appreciated, thanks in advance.

The layout is quite simple, it shouldn't be an issue. Do you have any logic to populate those spinners? Maybe share your xml — Maicon Hellmann, Aug 12 '20 at 09:39
@MaiconHellmann thanks for responding please see [this](https://stackoverflow.com/questions/63297031/dialog-pops-up-very-slow) question of mine. — Shreemaan Abhishek, Aug 12 '20 at 09:54
I have used ArrayAdapter (ArrayLists being fed into it) to populate the spinners — Shreemaan Abhishek, Aug 12 '20 at 09:55

Shreemaan Abhishek · Accepted Answer · 2020-11-30T17:34:51.973

AlertDialog and DialogFragment frameworks are slow because they need to some time to do calculations and fragment stuffs. So a solution to this problem is, using the Dialog framework straight away.

Use the Dialog framework's constructor to initialize a Dialog object like this:

Dialog dialog = new Dialog(context, R.style.Theme_AppCompat_Dialog);
// the second parameter is not compulsory and you can use other themes as well

Define the layout and then use dialog.setContentView(R.layout.name_of_layout).
Use dialog.findViewById(R.id.name_of_view) to reference views from the dialog's layout file

And then implement the logic just like anyone would do in an activity class. Find out the best implementation for your use case by reading the official documentation.

Custom dialog takes time to show up

1 Answers1