What problems or consequences may arise when performing a long-running operation inside an event handler?

Performing a long operation inside an event handler in Android can lead to several issues:

• Blocking the UI thread: Event handlers usually run on the main (UI) thread. If the operation takes a long time, the interface will become unresponsive, degrading the user experience.

• ANR (Application Not Responding): If the UI thread is blocked for more than 5 seconds, the Android system will show an ANR dialog, prompting the user to close the app.

• Loss of responsiveness: The user might think the app has frozen or crashed.

To avoid these problems, long operations should be performed in a background thread, for example, using AsyncTask (deprecated), HandlerThread, ExecutorService, or modern approaches with Coroutines or WorkManager.

Example using ExecutorService:

button.setOnClickListener(v -> {
    Executors.newSingleThreadExecutor().execute(() -> {
        // Long operation
        performLongTask();
        // Update UI on the main thread
        runOnUiThread(() -> {
            // Update interface
        });
    });
});