Android Central Lays Off Its Full-Time Staff, but Future Says the Site Will Stay Open

All remaining full-time staff at Android Central were laid off on Oct. 1, 2026. Owner Future told The Verge it will continue to publish the Android-focused blog. The Verge

Confirmation came from the staff, not the owner. Managing editor Derrek Lee and senior content producer Nicholas Sutrich confirmed that all remaining staff were laid off. Four of the six people listed on the staff page posted publicly: editor-in-chief Shruti Shekar, Lee, Senior Editor Harish Jonnalagadda, who oversees mobile coverage, and Sutrich. Shekar confirmed she had been laid off. The Verge

At first, staff did not know whether the site would close. Future spokesperson Nicole Martineau told The Verge that Future will continue to publish Android Central and will share more information in due course. The site stayed live. New posts after the layoffs came from freelance contributors, not former full-time staff. The Verge

The cuts went beyond one title. Android Police, which is owned by Valnet, laid off at least two staffers. The Verge

Future describes the site as providing honest opinions, trustworthy advice and recommendations. Future Its corporate team page lists Shekar as Managing Editor, Android Central, covering big tech, AI, Google, Android and Apple. Future Its U.S. tech network, which includes Android Central alongside Tom's Guide, TechRadar, iMore and Windows Central, reported 19% audience growth year over year in a December 2021 company update. Future

The broader context here is structural, not only editorial. A full-time beat builds working knowledge that is hard to replace article by article. That includes phone-maker release schedules, carrier testing quirks, update policies, and how software features behave across many Android versions still in use. It is like following the same car model across several model years. You learn which rattles matter. Freelance contributors can file solid reviews and news reports. What is harder to sustain is continuity, noticing when a vendor quietly changes a setting, brings back an old bug, or rewrites help documents without notice.

Looking at what this means for technology workers who use enthusiast press as a second set of eyes, the change affects workflow more than headlines. Many engineers, product managers and support teams scan these sites for early warnings. They look for bugs that return after an update, battery and heat complaints, Bluetooth and Wi-Fi faults between devices, and gaps between what release notes claim and what users see. That value depends on hands-on testing and on reporters staying on a beat long enough to separate one-off noise from a pattern.

In my view, the optimistic case is still intact, though narrower. Publishing tools are cheap, distribution is open, and specialist knowledge still finds readers. A lean, freelance-led Android Central can keep serving that role if Future keeps editorial standards and funds hands-on testing. The risk is a slower feedback loop, with fewer people to follow up, reproduce problems and press vendors for answers. For readers who build on Android, the practical step is to pay closer attention to bylines and test methods and to check field reports against more than one independent source.