Flipper Devices has responded to intense community backlash over perceptions that it had abandoned active development of the Flipper Zero firmware.

In a statement addressing the controversy, the company announced it will allocate dedicated resources to firmware maintenance while overhauling how it engages with contributors and feature requesters.

The Flipper Zero project launched via Kickstarter in 2020, raising over $5 million amid heavy public skepticism. The team faced post-COVID component shortages, supply chain disruptions, and sustained criticism while working to fulfill backer promises.

Despite these obstacles, Flipper Devices confirmed it delivered on every Kickstarter commitment, shipped all promised features, and built a hardware platform with supporting APIs and an SDK.

A key technical constraint shaped the firmware’s evolution: Flipper Zero has only 700 KB of flash memory available for firmware, quickly limiting the addition of new features. To address this, the team implemented dynamic app loading from microSD cards, moving core functions out of firmware and into modular apps.

This architecture became the foundation for stable firmware 1.0, released in 2024 alongside the official Apps Catalog. Following that release, the team narrowed its firmware focus to maintenance and critical bug fixes, shifting broader development attention toward new hardware devices.

Flipper Zero Firmware Development

In response to community demand, Flipper Devices outlined four operational changes:

Async-only communication: All development-related requests now route through GitHub Discussions rather than real-time chats or calls.
Weighted feature requests: Community members can vote on proposed features, with the team committing to review top-voted, concretely formatted requests weekly. General discussion and support queries remain on Discord, Reddit, and social media.
Stricter pull request review: An updated contribution guide imposes tighter scrutiny on PRs, particularly AI-generated code touching low-level libraries and changes affecting UI or documentation.
Mandatory integration testing: The team is publishing its internal QA integration test suite, requiring these tests for all firmware changes, with community involvement in regression testing.

Flipper Devices cited scale as the primary driver behind the shift. With over one million users generating requests across every communication channel, the company said it became impossible to distinguish genuine community-wide needs from isolated preferences, creating unmanageable noise.

The GitHub Discussions voting system is intended to surface prioritized, realistic requests while filtering out niche or unimplementable asks.

Notably, the Apps Catalog contribution process remains unchanged, preserving the existing pathway for third-party app submissions.

To address lingering questions, Flipper Devices’ core developers and managers held an AMA session on the r/flipperzero subreddit on Friday, July 3, at 15:00 BST.

The announcement signals an attempt to formalize open-source governance at scale, balancing limited internal engineering bandwidth against a large, technically engaged user base pushing for continued firmware innovation.

Strengthen Your SOC by Accelerating Threat Detection & Rapid Investigations. -> Integrate ANY.RUN With Your SOC Now.

The post Flipper Zero Firmware Development Continues With New Community Contribution Rules appeared first on Cyber Security News.