What is the equivalent to a JavaScript setInterval/setTimeout in Android/Java?

In-depth look at task timing

Running on the proper thread is like being in the right place at the right time. Your UI-associated tasks should stay on the main thread. Meanwhile, backend operations can take a snooze in the background thread.

Tool Time

Whether you're reaching for a Handler, Timer, ScheduledExecutorService, or AlarmManager, depends on what you're coding up today.

Handler & Runnable: PB&J of Android Timing

For all your UI-related timed operations, a Handler AND Runnable is the only PB to your J. If you're eyeing a one-off execution, opt for Handler.postDelayed(). For the recurring task folks, throw a boolean flag into the mix:

final Handler handler = new Handler(Looper.getMainLooper());
Runnable task = new Runnable() {
    @Override
    public void run() {
        if (shouldContinue) {
            // Repeating task, like deja vu but less eerie
            Log.i("RepeatingTask", "Main thread is doing its cardio.");
            handler.postDelayed(this, 1000);
        }
    }
};
handler.post(task);
// when `shouldContinue = false`, it's time to call it a day


This brings the power to stop the execution right at your fingertips, handy when a user exits a page or the app. Prevent excess resource consumption and those pesky memory leaks.

Timer & TimerTask: A Timeless Classic

For a delayed single task that's NOT UI-bound, new Timer().schedule(new TimerTask() {...}, delay) is your new best friend. Just remember, TimerTask gets a new thread to play solo, so it doesn't play well with the UI.

ScheduledExecutorService: Timing Tasks in Style

Java’s ScheduledExecutorService captures the balance between flexibility & robustness. You get to manage the thread pool size and task scheduling. Exercise control over delays and rates finer than a hipster's espresso grind.

AlarmManager: The Noisy Alarm

Tasks that wake up the phone and perform even when your app isn't running, raise your hand! AlarmManager handles duties even beyond app lifetime. Be mindful of its battery sipping habits and user impact. It's not cool to be that noisy neighbor at 3 a.m.

Handling background shenanigans

Background tasks that need to run regularly or sometime in the future will love WorkManager. Keep compatibility across versions and handle those system optimizations like Doze mode without a sweat.

Pros and cons: deciphering the tools

Each option has its strengths and quirks:

• Handler is friendly but married to the thread's Looper, normally the 'boring' main one.
• Timer can schedule a party but fails in grace while handling exceptions.
• ScheduledExecutorService is the master of flexibility and robustness but demands more attention.
• AlarmManager packs a punch in system-wide scheduling, use sparingly and respect your user's "quiet time".

Tips n' Tricks

• Holding strong references to handlers, tasks, and threads helps avoid premature garbage collection.
• Remember to cancel Handler actions or Timer tasks when done—they're not fans of overtime.