The Google Pixel Launcher is better than ever, but it's still missing 5 big features

The Pixel Launcher's Evolutionary Path: Better Than Ever. Yet Still Missing Key Features

For years, the Google Pixel Launcher has walked a fine line between being the purest expression of Android and a walled garden that refuses to let its users fully tend the soil. It delivers smooth animations, flawless At a Glance integration. And the fastest Circle to Search implementation on any device. The Pixel Launcher is better than ever in raw performance. Yet it's still missing features that power users and senior engineers have requested for generations. As a senior Android engineer who has spent countless hours profiling launcher performance on AOSP, I've watched the Pixel Launcher pick up features that should have been baseline years ago-long‑requested conveniences like app search filters and material‑you color theming that finally arrived in Android 14 and 15. But that progress only highlights what remains absent. Five big features remain missing, and their absence isn't just a cosmetic grievance; it's a product‑engineering decision that affects how we think about platform flexibility, resource management. And the developer-user contract. The Pixel Launcher is the best it's ever been. But five missing features reveal a fundamental tension between google's vision of simplicity and the customization power users expect from a modern mobile OS. In this deep dive, we'll examine each missing feature through the lens of system architecture, API limitations. And what they say about Google's long‑term strategy for Android's launcher layer. This article draws on insights from Android Authority and other trusted sources to ground the analysis in verifiable facts.

Recent Improvements: What Google Got Right in 2024-2025

Starting with Android 14 QPR2, Google introduced support for themed app icons-a Material You pillar that third‑party launchers like Nova had offered for years. In 2024, the launcher gained the ability to search for specific app shortcuts directly from the app drawer search bar, reducing the number of taps needed to launch, say, a specific Google Keep note from a widget. The introduction of "Notification history" integration inside the launcher (via a long‑press on the At a Glance widget) represents a smart use of the "notification listener" service architecture. These aren't trivial changes; they required modifications to the Launcher3Quickstep pipeline and deeper hooks into NotificationManager. Still, they feel like table stakes rather than innovation. The Pixel Launcher is undeniably faster and more responsive with each release. But the feature gap relative to third‑party alternatives remains stark. From a platform engineering perspective, Google's focus on performance over customization is a deliberate trade‑off that shapes the entire Android ecosystem's trajectory.

Dynamic Theming: A Step Forward With Hidden Costs

From an engineering perspective, the biggest win came with Android 15's dynamic theming engine. The Pixel Launcher now generates up to seven accent color variations from wallpaper colors using a K‑means clustering algorithm in the WallpaperColors API. But even this has a downside: the theme options are locked to Google's predefined palette, meaning developers can't programmatically set app icon tinting features. For senior engineers working on custom launchers for enterprise tablets, this lack of API exposure forces us to rely on accessibility‑service workarounds that degrade battery life. The improvements are real. But they also reveal how Google's platform controls restrict the very flexibility that power users crave. The dynamic theming engine in Android 15 is technically impressive, but its closed nature means that developers building for the Pixel Launcher can't extend or override the color extraction logic. This limits the ability to create branded experiences for enterprise deployments. Where consistent color schemes across apps are critical. The trade‑off is clear: Google prioritizes visual consistency over developer flexibility. And the launcher is the tool for enforcing that consistency.

Missing Feature #1: Customizable Home Screen Grid Sizes

The Pixel Launcher ships with a fixed 5×5 grid for the home screen and a 4×4 grid for the app drawer. No options exist to increase the grid density to 6×5 or 5×7 on larger screens like the Pixel 9 Pro XL or the Pixel Fold. This isn't a technical limitation-the AOSP Launcher3 supports resizable grids via the config_grid overlay. Google intentionally removed that flexibility to maintain visual consistency. For a developer, this feels like low‑hanging fruit: the grid layout is simply a RecyclerView with a GridLayoutManager. Changing the span count requires updating the ItemInfo's cell coordinates. Which is already handled in the database schema, and so why doesn't Google ship it

Why Grid Customization Matters for Enterprise Deployments

The answer likely lies in QA complexity. Allowing dynamic grid sizes would break the "At a Glance" widget's positioning, force wallpaper alignment recalculations. And require re‑testing against every possible screen size. In a production environment with millions of devices, every pixel of rendering inconsistency becomes a support ticket. Still, competitors like OnePlus's Shelf launcher and Samsung's One UI Home offer grid customization without notable issues. For engineers building custom launchers for industrial devices, this lack of flexibility forces us to either fork Launcher3 or rely on root‑level overlay modules (like Substratum)-neither of which is sustainable for enterprise deployment. In enterprise settings where devices are used for kiosk or point‑of‑sale applications, the ability to configure grid density directly impacts usability and brand consistency. A fixed grid forces developers to either compress UI elements or accept wasted screen space. The Pixel Launcher's rigidity here is a clear signal that Google's target audience is consumers, not the enterprise market that Android theoretically serves alongside solutions from Android Authority and other industry observers.

Missing Feature #2: Scrollable Dock or Multiple Dock Pages

The current Pixel Launcher dock supports a fixed set of icons-five on most devices, six on the Pixel Fold when unfolded-and there's no option to swipe the dock horizontally to reveal additional apps, nor does it support multiple dock pages. This is a glaring omission for users who rely on the dock as their primary app launcher. From a software architecture standpoint, adding a scrollable dock requires implementing a horizontal ViewPager2 inside the Hotseat layout. The Launcher3 codebase actually includes experimental branches for this (look at the custom_workspace commit history). So why isn't it enabled?

Business Incentives Behind the Static Dock

One plausible reason is battery optimization: a scrollable dock would require the launcher to keep more memory‑resident references to app icons and shortcuts, slightly increasing wake‑up time. More likely, Google views the dock as a static navigation anchor. If users could hide their most‑used apps in a second dock page, they might never discover the app drawer's search functionality-reducing the value of Google's paid app discovery integrations. For developers, this is a reminder that software engineering decisions are often subordinated to business incentives. On custom ROMs like LineageOS, we've implemented scrolling docks with SpringAnimator‑based overscroll effects in under 200 lines of Kotlin. It's not hard; it's just not a priority for the Pixel Launcher team.

Missing Feature #3: Full Icon Pack Support Beyond Themed Icons

Themed icons in the Pixel Launcher only adapt to material‑you colors if the app developer provides a monochrome icon in the adaptive icon bundle. Apps without a monochrome layer remain unchanged, creating an inconsistent visual landscape. True icon pack support-where the launcher can apply a custom icon pack and override all app icons-is notably absent. Technically, this requires implementing an IconCache that resolves package names to drawable resources from a third‑party APK. The LauncherAppWidgetHost already supports dynamic drawable loading; the missing piece is a permission system to read icon packages safely.

Security Versus Flexibility: The Icon Pack Dilemma

Google's caution here stems from security and performance. A rogue icon pack could inject bitmap‑based icons that delay the launcher's startup time or, worse, contain accessibility‑service‑abusing overlay code. Yet the Android ecosystem has supported icon packs for over a decade without systemic issues. The real reason may be that themed icons act as a retention mechanism for Google's Material Design guidelines: if every app looks uniform, developers are pressured to adopt Monochrome icons, ensuring a consistent brand for Android. For engineers, this is an example of platform policy enforcement via technical omission-a softer approach than forbidding icon packs outright, but one that nonetheless limits user agency. Google's security argument against icon packs is technically valid. But it ignores the fact that the Android permission model already provides mechanisms for safe third‑party resource loading. The PackageManager API, for example, can verify the signature of an icon pack APK before allowing it to be used as a drawable source. The omission of such a system in the Pixel Launcher suggests that Google is more concerned with preserving the visual brand of Material You than with enabling user choice.

Missing Feature #4: Notification Badges Without Granular Control

Pixel Launcher shows notification badges as small dots without a numeric count. While Android 15 introduced a numbered badge option inside the launcher settings (finally), the implementation is inconsistent. Some apps show the badge only if they support the ShortcutManager dynamic shortcuts API. And the count doesn't always sync with cleared notifications. For a developer, this is a classic case of relying on unreliable heuristics: the launcher reads the NotificationListenerService post‑filtered data. But if the app doesn't update its badge count via the NotificationChannel metadata, the launcher defaults to a generic dot.

Enterprise Impact of Inconsistent Badges

More importantly, the Pixel Launcher doesn't offer per‑app badge style customization. You can't disable badges for certain apps, change the dot color. Or set a maximum count threshold. In an enterprise environment where a single notification from a monitoring tool can trigger dozens of alerts, the lack of badge configurability leads to visual noise. Contrast this with the BadgeProvider in the Samsung One UI Home. Which exposes granular controls via ContentProvider. Google's stance seems to be "our heuristic is good enough"-but for engineers who need to triage alerts from multiple Slack workspaces, it's not. A related issue is the absence of per-app notification channel integration inside the launcher; users must look at system settings to customize badge behavior. This missing feature directly impacts productivity for technical users who rely on the Pixel Launcher as their primary interface.

Missing Feature #5: Native Unread Count Badges on Folders

When you organize apps into folders on the Pixel Launcher, folder badges aggregate all unread counts from each contained app into a single number. Sounds useful? The problem is that the badge only appears when the folder itself is the direct source of all notifications-which it isn't. The current logic uses a naive sum algorithm divorced from the actual notification state. For example, if you have Gmail (2 unread) and Slack (5 unread) in the same folder, the folder badge shows 7-even if you've already read all notifications in one of them except the last one the system cached.

Folder Badge Synchronization: A Small Bug With Big Implications

This bug stems from the BadgeInfo class in Launcher3. Which computes folder badges based on a "last seen" timestamp rather than a real‑time query to NotificationManager. Fixing it would require injecting a binder call per folder refresh,, and which could degrade scroll performanceYet other launchers-like Nova-implement folder badge syncing by caching notification data in a shareable SQLite database and updating it on each notification posted. The engineering effort is modest. The fact that Google hasn't addressed it suggests a philosophical choice: folders are meant for organization, not notification triage. For those of us who use folders as "workspaces"-a practice common in DevOps and engineering workflows-the current behavior is a constant source of false positives. This missing feature undermines the Pixel Launcher's utility for power users who need reliable badge aggregation across app groups.

Why These Gaps Persist: Platform Politics and Engineering Resources

Looking at these five missing features through an engineering lens, a pattern emerges: they're all features that require deeper integration with system services (Notifications, Wallpaper. Or Accessibility). Google's reluctance to open these APIs can be understood as a risk‑mitigation strategy. Every new API surface increases the attack surface and fragments the UX. However, for developers building custom launchers or enterprise‑managed devices, these gaps aren't just annoyances-they represent real productivity losses. In my own work deploying kiosk‑mode devices for a logistics firm, we spent three sprints building a custom launcher from the AOSP codebase just to get configurable grids and folder badge logic-that's engineering time that could have been spent on the core business logic.

Performance vs. Flexibility: A Conscious Trade-off

From a product management standpoint, Google's priorities are clear: the Pixel Launcher must be the fastest, most battery‑friendly launcher on the market. Features that introduce jank, memory leaks. Or inconsistent animations are sacrificed even if they're technically feasible. But as AMD and Apple have shown with their mobile GPU architectures, performance and flexibility aren't a zero‑sum game. It's possible to offer a "Developer mode" toggle that unlocks these customizations at the cost of a slight increase in memory pressure-something the Android team has done for other subsystems like the WebView debug flags. The absence of such a toggle in the launcher is a conscious choice to keep the codebase lean. Google's focus on smoothness and battery life has yielded measurable improvements: