I’ve been doing this since the 80s, when “multitasking” meant switching between two DOS programs by typing ALT-TAB (if you were lucky). Today, we’ve got phones with screens bigger than some laptops, and yet—some of the most basic multitasking features feel like they’re stuck in the last decade. Back when we had to manually resize windows on Windows 95, we at least had the option to do it. Now? Some of Android’s “innovations” feel like they’re missing the point entirely.
Remember when OEMs like Samsung and Xiaomi were pioneering floating windows and resizable apps? Those were the golden days. Now, Google’s trying to catch up, but their half-measures are leaving power users scratching their heads. Let’s break down the features that should have been perfected by now—and why they’re still falling short.
Why Can’t I Control Volume Per App? It’s 2026!
I get it—Google’s finally adding per-app volume control in the beta. But why is Assistant getting its own slider while my music player is left in the dust? I’ve seen this request since before I joined the industry, and it’s still treated like an afterthought. Back when we had to manually adjust EQ settings in Winamp, at least we had some control. Now, some apps get priority while others are left to fight for space in the main volume mixer. It’s like giving a VIP pass to one app and making the rest stand in line.
The real kicker? OEMs like Xiaomi and Samsung have had this for years. Since Google added desktop mode, you’d think they’d prioritize this—especially for productivity. But nope. It’s still a “maybe someday” feature. I’ve been doing this since the days of Palm Pilots, and even those had per-app volume toggles. What’s taking so long?
Bubbles: The PiP That Never Grew Up
Google’s app bubbles sound great on paper—floating windows for multitasking. But compared to what Samsung and Honor offer, it’s like comparing a toy car to a Tesla. You can’t open apps from the recent apps screen as bubbles, and they’re stuck in one spot once expanded. It’s like they took picture-in-picture (PiP) from Android 15 and called it a day.
I’ve been using OneUI’s floating windows since the S10, and they’re actually useful. You can resize, move, stack, and even hide them partially off-screen. Google’s version? It’s like they watched a tutorial and then forgot half the steps. Even the ability to open bubbles from notifications—something that used to be standard—is missing. It’s not multitasking; it’s half-baked PiP with a fancy name.
Split Screen: Dead Before It Even Started
Remember when split-screen was actually useful? Android 7 had a better implementation than what we’ve got now. With app pairs, you’re forced to keep two apps locked together, and switching one means redoing the whole setup. I used to watch Twitch in the top half while browsing Reddit below—it worked perfectly. Now? It’s clunky, restrictive, and half the time, YouTube just jumps into PiP mode and breaks the pair.
Google’s response? “We’ve made progress.” Progress in what? Making it harder to do what we could already do? I’ve been doing this since the days of BlackBerry multitasking, and even those had better app switching. The fact that we’re arguing about basic window management in 2026 is embarrassing.
Floating Windows: The Missing Piece of the Puzzle
Some of you might be asking: “Why do we need floating windows when we have bubbles?” Because bubbles aren’t floating windows. They’re fixed, one-at-a-time placeholders. True floating windows—like what Samsung and Xiaomi offer—let you have multiple resizable apps side by side. You can drag them around, stack them, and even peek them from the edge of the screen. Google’s solution? It’s like they’re afraid of giving users too much freedom.
I’ve been using Honor’s floating windows for years, and they’re a game-changer. You can have a browser, a chat app, and a video player all at once, resized to your liking. Google’s version? It’s like they’re afraid of making Android too “complex.” Newsflash: power users want complexity—they want options.
The Beta Blues: Why Testing Feels Like a Gamble
Joining the Android beta used to mean testing new features without locking yourself into a never-ending cycle. Now? You sign up for one beta, and suddenly you’re enrolled in the QPR beta too. I’ve been doing this since the days of Android Beta 1, and the new system feels like a trap. Factory resetting isn’t an option for most people—so we just hold off on betas altogether. That’s not progress; that’s bad design.
And let’s talk about LDAC. It’s “almost there” in the beta, but at max quality, it still struggles. After all these years, we’re still arguing about basic audio codecs? It’s like we’re back in the days of MP3 vs. AAC, but now it’s LDAC vs. “good enough.”
Full-Screen Apps: The Elephant in the Room
One thing that still irks me—why aren’t fullscreen apps forced yet? I’ve been using iPhones too, and the edge-to-edge experience is night and day. On Android, you still get those annoying black bars. It’s not a “flagship” feel. We should be able to enjoy content on the whole screen, not just 80% of it. This isn’t a new complaint, but it’s still a valid one. When will we finally get there?
The Future of Multitasking: Where Do We Go From Here?
Here’s the truth: Android’s multitasking features have been in reverse for too long. We’re not asking for magic—we’re asking for the basics. Per-app volume, floating windows, and split-screen that doesn’t feel like a chore. I’ve seen it done right by OEMs, so why can’t Google catch up?
The next time you see a new “feature” in the beta, ask yourself: is this actually useful? Or is it just another half-baked attempt at catching up? Because if we keep settling for less, we’ll be stuck in this loop forever. And trust me—you don’t want to be here in 10 years, still arguing about the same problems.