Optimizing Android PopupWindow and Snackbar UI Thread to Prevent Frame Drops

Background: a SDK's PopupWindow with animation may cause frame drops when the app also runs animations simultaneously, due to both being drawn on the main thread.

Root cause: uncontrolled animation conflict + time‑consuming operations (popup instantiation, view inflate) executed on the UI thread.

Goal: find a solution that allows the popup to be prepared off the UI thread while keeping UI updates thread‑consistent.

Optimization measures:

Method 1 – dynamically delay the popup instantiation and display time to avoid overlapping with business animations. (Result: feasible but not elegant; fallback solution.)

Method 2 – move time‑consuming operations (instantiation, inflate) to a background thread and only call show() on the UI thread. The view is not attached yet, so no UI thread check is triggered.

Method 3 – run the whole PopupWindow (including show/dismiss) on a dedicated UI thread created with a HandlerThread . This isolates the popup’s UI work from the app’s main thread.

Principle analysis:

Explains main‑thread vs UI‑thread, ViewRootImpl, CalledFromWrongThreadException , attachInfo, invalidate flow, Choreographer, Looper, etc. Includes code snippets such as:

// ViewRootImpl.java
void checkThread() {
    if (mThread != Thread.currentThread()) {
        throw new CalledFromWrongThreadException(
                "Only the original thread that created a view hierarchy can touch its views.");
    }
}

Shows that the thread stored in ViewRootImpl is the thread that created the view hierarchy, not necessarily the process main thread.

Shows how WindowManager#addView creates a new ViewRootImpl, which inherits the current thread’s Looper, allowing a separate UI thread.

Implementation example of a custom UI thread for Snackbar:

public class SnackBarPopWinManager {
    private static SnackBarPopWinManager instance;
    private final Handler h; // UI thread handler

    private SnackBarPopWinManager() {
        HandlerThread ht = new HandlerThread("snackbar-ui-thread");
        ht.start();
        h = new Handler(ht.getLooper());
    }

    public void presentPopWin(final SnackBarPopWin snackBarPopWin) {
        h.post(new SafeRunnable() {
            @Override
            public void safeRun() {
                snackBarPopWin.getPopWin().showAtLocation(...);
                snackBarPopWin.dismissAfter(5000);
            }
        });
    }
    // dismissPopWin omitted for brevity
}

Verification: screenshots (GIFs) show that the popup animates smoothly even when the app is performing other animations, and click events are handled on the custom UI thread.

Summary: The UI thread that draws a view must be the same thread that creates the view hierarchy, but it does not have to be the application’s main thread. For isolated UI components such as pop‑ups, creating a dedicated UI thread can eliminate frame drops without breaking Android’s thread‑checking rules, while still respecting constraints (e.g., WebView must stay on the main thread).