Kevin Barry, the founder and sole remaining developer of Nova Launcher, has left Branch Metrics after being told to halt work on making the launcher open source, leaving one of Android’s most iconic customization apps in an uncertain limbo. The departure, confirmed in September 2025, punctuates a steady erosion of the third-party launcher landscape, where once-essential power-user tools now face headwinds from platform improvements, corporate reprioritization, and a shifting definition of what a home screen should do.

Kevin Barry’s Abrupt Exit and the Open-Source Conundrum

Nova Launcher’s journey under Branch Metrics began with fanfare and promises. Branch, a mobile analytics company, acquired the app on July 19, 2022, with then-CEO Alex Austin publicly committing that Nova would continue under its original vision and that, should Barry ever leave, the code would be handed to the community. Those words are now a central point of contention.

In August 2024, Branch implemented sweeping layoffs that gutted the Nova team, leaving Barry as the lone full-time developer. Despite efforts to maintain updates, the situation was fragile. By September 2025, Barry announced he had left the company entirely. In a farewell post, he detailed months of preparation for an open-source release—cleaning the codebase, reviewing licenses, replacing proprietary components, and coordinating with legal—only to be told to stop all work. Branch, now under different leadership, has remained silent on whether the original open-source pledge holds any weight.

A Change.org petition demanding Branch open-source Nova had amassed just over 3,000 signatures at the time of reporting, but momentum is far from guaranteed. The public statements from 2022 exist, yet without a legally binding contract, the community’s only leverage is pressure and hope. As one forum discussion notes, treating the “contractual promise” framing as definitive is premature; the reality may be governed by corporate calculus, not old blog posts.

What Nova’s Stasis Means Technically

Nova wasn’t just a launcher; it was a de facto standard for granular customization. Its gesture engine, icon pack framework, grid controls, and performance tuning shaped Android power-user expectations for a decade. Without active maintenance, the app faces a slow decay:

  • Android platform changes (Android 15 and 16) can introduce compatibility breaks requiring code patches.
  • Security and third-party API updates (weather widgets, calendar access) will go unaddressed.
  • OEM and Google tweaks to system animations and integration points can erode the smooth experience Nova was known for.

Users can continue running the current build, but the clock is ticking. The risk isn’t an overnight failure; it’s a gradual bitrot that silently degrades reliability, especially when new Android versions roll out.

Microsoft Launcher: Copilot and Stagnation

While Nova’s drama plays out on center stage, Microsoft Launcher has quietly settled into a maintenance coma. The app still appears in the Play Store, still receives occasional minor patches—a small update landed on July 22, 2025—but its feature trajectory has flatlined.

The most notable addition in recent years is Copilot integration, rolled out to beta in 2024. A swipe-right now summons Microsoft’s AI assistant, mirroring a strategy that injects AI everywhere from Windows 11 Notepad to Edge. But as the Windows Central editorial team and community discussants alike observe, the addition feels bolted on rather than transformative. A launcher’s core job—speed, predictability, and low overhead—can clash with an always-ready AI pane that pulls in permissions, potential latency, and privacy baggage. For minimalists, it’s a non-essential; for many others, it’s just one more thing to dismiss.

Microsoft Launcher was once a compelling productivity hub, tightly integrating Microsoft 365 services, a clean feed, and Surface Duo optimizations. Today, it lacks dedicated support for modern foldables like Samsung’s Galaxy Z Flip and Fold series. The update cadence has slowed to a crawl, prompting Windows Central’s own editor to uninstall it for the first time in years in favor of a device’s stock launcher.

Officially, Microsoft says the launcher is still supported. But in the eyes of many power users, “supported” and “actively developed” are not the same. The app hasn’t gotten a meaningful feature update in months, and its roadmap is opaque. For those who once relied on its deep Microsoft ecosystem weave, the current state feels like a silent retreat.

The Shifting Third-Party Launcher Landscape in 2025

To understand the weight of these developments, it’s necessary to step back and examine why launchers once mattered so much—and why their importance has contracted.

Why Launchers Were Essential

  • Customization: Granular control over icons, gestures, app drawer behavior, and grid layouts that stock launchers didn’t offer.
  • Power Features: Shortcut macros, gesture chains, advanced folder behaviors, and per-icon swipe actions.
  • Community Ecosystems: Plugin and theme markets that spawned entire forums and Discords.
  • Performance Tuning: Nova and others optimized for smoothness and battery efficiency, often outpacing bloated OEM launchers.

Why Their Importance Has Narrowed

  • First-Party Launchers Have Caught Up: Google’s Pixel Launcher and Samsung’s One UI Home now include deep customization options. Samsung’s Good Lock modules, for instance, deliver near-Nova levels of control natively.
  • Foldable and OEM Optimizations: Devices like the Galaxy Z Fold and Flip demand launchers tailored to hinge, multi-window, and cover-screen interactions. The factory launcher is often the only one that gets this fully right.
  • Google’s Platform Moves: In 2025, Google delivered concrete fixes for third-party launcher animation and transition glitches on Pixel phones, closing some performance gaps—but simultaneously demonstrating how dependent third-party launchers are on the platform vendor’s goodwill.
  • Mainstream User Needs Evolved: For many, the out-of-box experience is now good enough. The urge to root, theme, and hyper-customize has faded as Android matured.

Where Third-Party Launchers Still Shine

Despite the contraction, niches persist. Minimalist designs like Niagara Launcher’s list-first interface remain actively updated with theming and Android 15 support, catering to one-hand usability devotees. Lawnchair forks capture the Pixel aesthetic with Nova-esque customization baked in. For users whose muscle memory depends on custom gestures and fine-grained layout control, no stock launcher yet matches what third-party options offer.

Privacy-conscious options that eschew telemetry and ads also fill a void OEMs often ignore. And the community-driven ingenuity—when projects are healthy—can still outpace corporate roadmaps.

Practical Guidance: Navigating Home Screen Transitions

If you’re one of the millions who’ve relied on Nova or Microsoft Launcher, now is the time to act. Here’s a systematic approach distilled from community wisdom and technical realities.

1. Inventory Your Dependencies

List every gesture, widget, icon pack, backup routine, and automation that’s launcher-specific. Export or screenshot settings where possible. Nova allows backup files; save them.

2. Prioritize Your Replacement

Rank what matters most: customization depth, performance, minimalism, ecosystem integration, or stability on your device form factor. Then match alternatives:

  • Performance & Power User: Lawnchair forks or Lawnchair-style projects offer Pixel-like fluidity with heavy customization.
  • Minimalist & One-Hand Use: Niagara Launcher’s active development and Android 15 support make it a modern, focused choice.
  • Feature Parity with Nova: Lawnchair forks and other open-source endeavors often mimic Nova’s options; check active development status before committing.
  • Ecosystem Integration: If you’re tied to Microsoft services, Microsoft Launcher still works but accept its slower pace; alternatively, combine a stock launcher with Microsoft 365 widgets.
  • Foldable Users: Stick with the OEM launcher unless a third-party option explicitly states foldable optimization (most don’t).

3. Test Safely

Set up the replacement on a secondary device or a clean user profile first. This prevents losing your daily driver’s layout if the new launcher misbehaves or lacks critical features.

4. Automate Backups

Once you settle, export your home-screen layout, icon pack choices, and widget settings regularly. Store copies in cloud storage or locally. Launcher-hopping becomes less painful with a backup routine.

5. Watch the Open-Source Horizon

If Branch eventually complies with community pressure and releases Nova’s code, community forks will likely appear. Before adopting any fork, scrutinize its code quality, update cadence, and security hygiene. Remember, an abandoned fork is no better than an abandoned official app.

Checklist: Which Launcher Suits You?

  • Deep widget control? → Launcher with widget stacks and strong APIs (e.g., Lawnchair forks).
  • Gesture first, aesthetics second? → Launcher that exposes detailed gesture customization (Niagara, Smart Launcher).
  • Foldable device? → OEM launcher for optimal multi-window behavior; test third-party launchers extensively if you insist.
  • Privacy non-negotiable? → Search for actively maintained open-source launchers with clear no-telemetry policies.

Risks and Community Considerations

Fragmentation Risk

If Nova’s code never sees the light, no legal fork can evolve it. Users will be forced to migrate, losing years of muscle memory and setup. The community has successfully sustained Lawnchair and others, but each project requires a committed maintainer—something Nova currently lacks.

Security Concerns with Abandoned Apps

Unmaintained launchers become attack surfaces. Any vulnerability in widget handling, weather data retrieval, or gesture processing goes unpatched. Treat an abandoned launcher like any deprecated software: phase it out before it becomes a liability.

Ecosystem Lock-In

The pain of switching launchers goes beyond installing an APK. Some widgets, custom icon solutions, and automation setups (Tasker integrations, for example) are deeply tied to the launcher. Budget hours, not minutes, for reconfiguration. The forum advice to inventory dependencies first is not optional—it’s survival.

Corporate Manageability

Enterprises that allowed custom launchers on managed devices must re-evaluate. An unmaintained launcher with community plugins can complicate compliance. Audit your fleet’s launcher inventory and push approved, updated alternatives.

The Long View: Do Launchers Still Matter?

Yes—but their role has shrunk and specialized. Third-party launchers remain the fastest route to expressive customization and alternative navigation paradigms. For users who prize control, accessibility, or a distinct aesthetic, they are still uniquely valuable. But platform vendors and OEMs have closed so many gaps that the urgency for mainstream users to install a third-party launcher has all but evaporated.

Google’s 2025 animation fixes for third-party launchers on Pixel devices exemplify the dynamic: the platform can choose to accommodate third parties, but it can also shift the baseline at any time. Native launchers are now better optimized for new hardware and new Android APIs, from foldable hinges to Live Updates. That’s a net win for most consumers, but it also means that third-party launchers operate in a narrower niche.

Nova’s saga is a cautionary tale about stewardship. An app that defined a generation of Android power users now teeters because of a corporate acquisition and absent leadership. The open-source promise, once a comforting safety net, now hangs on the goodwill of a company that may not even remember making it. For any software beloved by a community, the true insurance is a living, breathing open-source fork with multiple maintainers—and that requires a legal handoff that Branch still refuses to make.

Where Android Home Screens Go from Here

If you depend on Nova or Microsoft Launcher for productivity or a deeply customized workflow, this moment is an inflection point. Document your setup, export what you can, and start evaluating alternatives now rather than scrambling when a forced migration becomes critical. For most everyday users, the stock launcher is sufficient and often preferable for stability—especially on foldables and recent Pixel devices. But if customization, aesthetics, or experimental UX models matter to you, third-party launchers still deliver distinct value, provided they remain actively maintained.

The Android launcher story isn’t over, but it has changed forever. Where code is left to the community and actively maintained, innovation will continue. Where corporate strategy shifts, even the most beloved apps can drift into maintenance limbo. Power users who care about their home screen should treat launcher choice as a dynamic decision, not a set-it-and-forget-it preference. In 2025, the smartest launcher is the one that will still be standing when the next Android version arrives.