Nova Launcher’s original developer has walked away, Microsoft Launcher feels all but idle, and the Android launcher landscape is quietly rearranging itself — but the idea of swapping your home screen still matters, just in different ways than it did a decade ago.
Third-party Android launchers once held an outsized influence on smartphone UX. Apps like Nova Launcher rewired expectations about gestures, icon packs, layout freedom, and performance; they were the playground where power users and themers pushed Android’s limits. Microsoft’s own effort — Microsoft Launcher (formerly Arrow Launcher) — carved out a niche by tying home‑screen productivity to Microsoft services and a polished feed experience.
Those histories matter because the most recent shakeups are not mere product updates: they’re signal events. Nova’s founder and last active developer, Kevin Barry, announced his departure and said he was asked to stop work — including preparations to release Nova as open source. That raised immediate questions about the app’s long‑term viability. Independent reporting and Barry’s own posts corroborate this timeline and the core claims. (theverge.com, 9to5google.com)
At the same time, Microsoft Launcher — once a go‑to option for people who wanted a Windows‑style, cross‑platform tie‑in on Android — has seen only modest updates. The biggest visible change was Copilot being integrated into the launcher feed, but that addition has done little to dispel the perception that the app hasn’t been prioritized. Play‑store and APK archives show sporadic releases in 2024–2025 and beta builds around mid‑2025, but no sustained product push that matches Microsoft’s other AI investments. (windowscentral.com, apkmirror.com)
APK archives and third‑party app indexes show releases in mid‑2025 (July), including beta builds — confirming the app hasn’t been abandoned in the strictest sense — but that update cadence doesn’t equate to an active product roadmap. If you want a launcher that will be aggressively forward‑compatible with new form factors (foldables, cover screens), Microsoft Launcher has lagged in optimizations for newer foldable designs compared with OEM launchers. Community posts and support threads show users encountering recurring bugs and inconsistent behavior across devices. (microsoft-arrow-launcher.en.uptodown.com, learn.microsoft.com)
Source: Windows Central Nova Launcher is drifting, Microsoft Launcher is stagnant. Do Android launchers still matter?
Background
Third-party Android launchers once held an outsized influence on smartphone UX. Apps like Nova Launcher rewired expectations about gestures, icon packs, layout freedom, and performance; they were the playground where power users and themers pushed Android’s limits. Microsoft’s own effort — Microsoft Launcher (formerly Arrow Launcher) — carved out a niche by tying home‑screen productivity to Microsoft services and a polished feed experience.Those histories matter because the most recent shakeups are not mere product updates: they’re signal events. Nova’s founder and last active developer, Kevin Barry, announced his departure and said he was asked to stop work — including preparations to release Nova as open source. That raised immediate questions about the app’s long‑term viability. Independent reporting and Barry’s own posts corroborate this timeline and the core claims. (theverge.com, 9to5google.com)
At the same time, Microsoft Launcher — once a go‑to option for people who wanted a Windows‑style, cross‑platform tie‑in on Android — has seen only modest updates. The biggest visible change was Copilot being integrated into the launcher feed, but that addition has done little to dispel the perception that the app hasn’t been prioritized. Play‑store and APK archives show sporadic releases in 2024–2025 and beta builds around mid‑2025, but no sustained product push that matches Microsoft’s other AI investments. (windowscentral.com, apkmirror.com)
What actually happened to Nova Launcher
Timeline in brief
- July 19, 2022 — Branch (Branch Metrics) acquired Nova Launcher; public posts at the time promised the project would continue under Nova’s original vision. (novalauncher.com)
- August 2024 — Branch implemented broad layoffs that dramatically reduced the Nova team, leaving Kevin Barry as the sole full‑time developer. Coverage from multiple outlets and community channels documented the departures. (9to5google.com, theverge.com)
- September 2025 — Kevin Barry announced he had left Branch and said he had been preparing Nova for an open‑source release but was told to stop; he explicitly said he is no longer involved. That announcement has been widely reported and is being discussed across the Android community. (theverge.com, 9to5google.com)
The open‑source promise: what’s verifiable and what isn’t
When Branch bought Nova, public statements by Branch’s then‑CEO suggested that if Barry left, the code would be handed to the community. That pledge came from an earlier leadership era and has become a focal point for the community’s demands now that Barry has departed. Multiple outlets reference those earlier commitments, but whether there is a legally binding contract obligating Branch to open‑source Nova is not publicly verifiable. Community petitions ask Branch to follow through; Branch’s official stance has been quiet in public. Readers should treat the “contractual promise” framing as an unconfirmed claim backed by public statements, rather than a guaranteed legal obligation. (theverge.com, 9to5google.com)Why this matters technically
Nova was not just another app — it was a de‑facto standard for advanced launcher features: gesture customization, grid and icon control, performance tuning, and compatibility tweaks across Android versions. If the project stops receiving maintenance, users will still be able to run the app for a while, but practical problems accumulate:- Android platform changes (e.g., Android 15/16 adjustments) can introduce compatibility issues that require active maintenance.
- Security and third‑party API updates (for weather widgets, calendar access) will need patches.
- Device OEMs (and the Pixel team) can change behaviors that affect third‑party launchers’ animations and system integrations.
Microsoft Launcher: alive, but drifting
Where Microsoft Launcher stands today
Microsoft Launcher is still published, still available on the Play Store, and still receiving updates — but the cadence and focus raise questions. The most notable recent change was adding Copilot into the feed, giving users a swipe‑right AI assistant integration. That’s a logical extension of Microsoft’s ecosystem play, but it’s also incremental relative to other areas where Microsoft is investing heavily (Windows Copilot, M365 Copilot, etc.). The Copilot feature arrived in beta in 2024 and was rolled into later releases, but users report intermittent bugs and a sense that the app is not receiving the same attention as Microsoft’s marquee services. (windowscentral.com, apkmirror.com)APK archives and third‑party app indexes show releases in mid‑2025 (July), including beta builds — confirming the app hasn’t been abandoned in the strictest sense — but that update cadence doesn’t equate to an active product roadmap. If you want a launcher that will be aggressively forward‑compatible with new form factors (foldables, cover screens), Microsoft Launcher has lagged in optimizations for newer foldable designs compared with OEM launchers. Community posts and support threads show users encountering recurring bugs and inconsistent behavior across devices. (microsoft-arrow-launcher.en.uptodown.com, learn.microsoft.com)
Why Copilot integration isn’t a panacea
Integrating AI into a launcher is a sensible strategy on paper: quick answers, image generation, content creation prompts — all accessible with a swipe. However, the launcher’s primary job is speed, predictability, and low overhead. Adding an always‑present AI module introduces:- Additional surface area for privacy and permissions questions.
- Potential performance overhead on low‑end devices.
- A mismatch between utility and core launcher values for users who prefer minimalism and reliability.
The changing role of third‑party launchers in 2025
Why launchers mattered historically
- Customization: deep control over icons, gestures, app drawer behavior, and grid layouts.
- Power features: shortcut macros, gesture chains, and advanced folder behaviors.
- Community extensions: plugin ecosystems and themes that proliferated through forums and Discords.
- Performance tuning: launchers like Nova optimized for smoothness and battery efficiency.
Why their importance is smaller now
- First‑party launchers have improved materially. Google’s Pixel Launcher gained visual and interaction tweaks in Android releases, and OEM launchers (Samsung One UI Home) have leaned into customization and Good Lock modules that give deep control for their hardware. These native launchers now solve many use cases that previously required a third party. (androidauthority.com, androidcentral.com)
- Platform compatibility and OEM optimizations favor the stock launcher. Newer devices, especially foldables, often ship with launchers and UI layers tailored for their unique hinge, multi‑window, and cover‑screen interactions. Using the manufacturer’s launcher frequently yields the best experience out of the box. (androidcentral.com)
- Google made concrete changes in 2025 to improve third‑party launcher behavior on Pixel phones (animation and transition fixes), narrowing some longstanding performance gaps — but that fix also underscored a reality: platform vendors can and will shift the experience toward their own launchers unless third‑party options remain freshly maintained. (androidauthority.com)
Where third‑party launchers still shine in 2025
- Unique design philosophies: minimal list‑first launchers (Niagara), macOS‑like docks, or radical one‑hand UIs. Niagara’s 2025 theming and Android‑15 support illustrate the continued innovation available in smaller projects. (medium.com, androidauthority.com)
- Speed and muscle memory for keyboard/power users: if you want custom gestures and fine control, third‑party launchers remain unmatched. Community ecosystems can still deliver creative automation and integration.
- Privacy and ad‑free policies: some launchers purposefully avoid telemetry and push a lightweight, ad‑free experience that OEMs don’t prioritize. (apkbros.com)
Practical advice: what to do if your launcher is drifting or gone
If you relied on Nova or Microsoft Launcher and are reconsidering, here’s a practical, prioritized approach to moving forward.- Inventory your dependencies.
- List the gestures, widgets, icon packs, and backup routines you rely on. Export or screenshot settings where possible.
- Choose replacement options by priority: performance, customization, or ecosystem.
- Performance & power user: consider Lawnchair variants or Lawnchair‑style forks.
- Minimalist & one‑hand use: try Niagara Launcher (actively updated in 2025).
- Feature parity with Nova: evaluate Lawnchair forks or other open projects that mimic Nova’s options. (lifewire.com, help.niagaralauncher.app)
- Test on a secondary device or create a clean profile before committing. This prevents losing your primary home‑screen if the replacement misbehaves.
- Automate backups. Export your home‑screen layout, icon pack choices, and widget settings where possible. Keep copies in cloud storage or as local backups.
- If you’re technically inclined and Nova is open‑sourced in the future, consider community forks — but evaluate code quality, update cadence, and security before adopting any third‑party fork.
- Do you need deep widget control? Choose launchers with widget stacks and strong widget APIs.
- Do you value gestures more than aesthetics? Pick a launcher that exposes gesture customization in the settings.
- Are you on a foldable? Prefer OEM launcher or test thoroughly for multi‑window quirks.
Alternatives worth trying (short list with notes)
- Niagara Launcher — Minimal, one‑hand friendly, actively updated with theming and Android‑15 support; excellent if you want a clean, modern alternative. (androidauthority.com, medium.com)
- Lawnchair / Lawnchair forks — Community‑driven efforts that emulate Pixel style while offering customization. Good Nova stand‑ins when tuned carefully. (alternativeto.net)
- Smart Launcher / Action Launcher — Feature heavy, with additional UI paradigms (app sorting, shutters, and unique widgets). Good for users who want advanced features out of the box. (lifewire.com)
- OEM launchers (Samsung One UI Home, Pixel Launcher) — Best for foldables and device‑specific optimizations. If stability and battery life on a new device matter most, start here. (androidcentral.com, androidauthority.com)
Risks and community considerations
- Fragmentation risk: If Nova is not open‑sourced, community forks cannot legally evolve the original code; users may be forced to migrate. Multiple outlets flagged this as a distinct possibility after Barry’s departure. (9to5google.com, theverge.com)
- Security concerns with abandoned apps: unattended dependencies can expose users to exploitable bugs. If a launcher isn’t getting security updates, it becomes an unnecessary attack surface. Treat abandoned apps like any deprecated software. (9to5google.com)
- Ecosystem lock‑in: moving between launchers is more than swapping an APK — some widgets, custom icon solutions, and automation setups are launcher‑specific. Users should budget time for reconfiguration.
- Corporate manageability: enterprises that allowed custom launchers on corporate devices should audit the security and update path of any third‑party launcher in use. Community plugin ecosystems can complicate compliance.
The long view: do launchers still matter?
Short answer: yes — but their role is narrower and more specialized than it used to be.- Launchers remain the fastest route to expressive customization and alternative navigation paradigms. For users who prize control, accessibility, or a particular aesthetic, third‑party launchers are still uniquely valuable. (help.niagaralauncher.app)
- However, platform vendors and OEMs have closed many gaps. Native launchers are better optimized for new hardware (foldables, cover screens) and new Android APIs; that reduces the urgency for many mainstream users to install third‑party launchers. Google’s work to improve third‑party launcher animations in 2025 shows that platform vendors will shape the experience in ways third parties must adapt to. (androidauthority.com)
- The Nova story is a cautionary tale: even iconic apps can be vulnerable to corporate reprioritization and staffing changes. Community stewardship and open‑source options remain the most reliable path for longevity, but those outcomes are never guaranteed without a clear legal and technical handoff. (theverge.com, 9to5google.com)
Closing analysis: what readers and power users should take away
- If you depend on Nova or Microsoft Launcher for productivity or a highly customized workflow, treat the current moment as an inflection point: document your setup, export what you can, and evaluate alternatives now rather than when a forced migration becomes urgent.
- For most everyday users, the stock launcher is sufficient and often preferable for stability — especially on foldables and newer Pixel devices. But if you value customization, aesthetics, or experimental UX models, third‑party launchers still provide distinct value and will continue to do so where they remain actively maintained. (lifewire.com, androidcentral.com)
Source: Windows Central Nova Launcher is drifting, Microsoft Launcher is stagnant. Do Android launchers still matter?