Flipper Zero 的未来发展
The future of Flipper Zero development

原始链接: https://blog.flipper.net/future-of-flipper-zero-development/

为了回应社区反馈,Flipper Devices 重申了其对 Flipper Zero 固件的承诺。虽然公司目前将工作重心转向新硬件的开发,但他们承诺将通过结构化的异步流程来支持社区贡献,从而维护现有的固件。 为了有效地管理这一流程,团队引入了一套新的参与框架: * **以 GitHub 为中心的协作:** 所有功能需求必须通过 GitHub Discussions 提交,并由社区进行投票。团队将根据这些投票结果,优先处理并实施相应功能。 * **更严格的指导方针:** 合并请求(Pull Requests)现在将面临严格的评估,包括强制性的集成和回归测试,以确保稳定性。 * **更明确的界限:** 官方开发沟通将仅限于 GitHub 进行,而 Discord 和 Reddit 等社交渠道将保留用于一般的社区讨论。 公司强调,由于团队规模较小,他们无法进行实时聊天,但这种新方法可以确保社区最迫切的需求得到解决,在保持核心固件稳定性的同时,推动 Flipper Zero 平台的不断发展。

这篇 Hacker News 帖子讨论了 Flipper Zero 的未来发展。尽管该项目已经实现了最初的目标,但由于公司将重心转向新产品,核心固件的更新有所放缓,引发了社区的不满。 讨论的焦点主要集中在固件是否应该完全开源。一些用户认为,公司对官方代码库的严格控制以及对其 Discord 频道的激进审核,正将用户推向非官方的、功能“全包含”的第三方固件。支持官方立场的人则认为,保持产品的“完成度”是一种美德,且过于激进的功能集会招致不必要的监管审查。 除了软件生命周期之外,讨论还演变成了一场关于网络安全社区中“兽迷”(furry)文化盛行与否的争议性话题。虽然一些用户对该项目品牌和文档中的美学选择表示不满,但另一些人则认为信息安全界这种多元化且带有“反主流文化”色彩的构成是一个积极的包容性特征。归根结底,共识表明对于许多用户而言,无论官方企业支持与更广泛的黑客社区之间存在怎样的持续紧张关系,Flipper Zero 依然是硬件爱好者手中多功能的“瑞士军刀”。
相关文章

原文

We've seen the strong reaction from the community over the idea that we've stopped developing the Flipper Zero firmware. We want to address this and let you know that we've heard all your feedback and have decided to rethink our approach to maintaining the project and engaging with the community.

TL;DR: We've allocated resources to maintain Flipper Zero firmware and support community contributions. From now on, community requests and contributions will be reviewed under new rules: voting for feature requests in GitHub Discussions, clearer pull request guidelines, and mandatory integration testing.

When Flipper Zero launched on Kickstarter, we were overwhelmed by the community's support. That support came with a responsibility to deliver what we had promised. At the same time, we faced a wave of skepticism. We were called scammers and told the project would never ship.

A year and a half later, our entire team worked with the fear of letting our backers down and becoming another crowdfunding project remembered for taking $5 million and never delivering. We were hit by post-COVID component shortages, soaring supply chain costs, and political turmoil. On top of that, we were still dealing with thousands of accusations, insults, and threats.

We worked as hard as we could while trying to ignore the constant storm of criticism around us. But we have to admit that it was incredibly difficult. Today, we can look back and say that we made the right decisions: we planned our resources carefully, took risks, and worked really hard.

In the end, we made it through every challenge: from hardware and manufacturing to supply chains, logistics, firmware, and software development. We feel empathy for the teams behind crowdfunding projects that tried to copy Flipper Zero, but ended up shipping nothing. We could easily have been one of them, but today we can say with confidence:

  • We delivered on all Kickstarter promises — every backer received the Flipper Zero they paid for, even if it took much longer than anyone had expected.
  • All features were implemented — everything we stated in our Kickstarter campaign works as promised. This took us years of development.
  • We built a platform and infrastructure — we're proud that Flipper Zero has become a hardware platform with software tools, APIs, and an SDK that developers genuinely enjoy using. That’s exactly why there are so many community-driven projects around Flipper Zero: alternative firmware, apps, and scripts.
  • Flipper Zero is available worldwide (almost) — it may not be the most visible achievement, but we invested an enormous amount of effort into getting regulatory certifications, customs approvals, and all the paperwork required to officially import Flipper Zero into most countries. That's why there are now so many devices in people's hands.

Thanks to everyone who supports us

We are deeply grateful to everyone who has supported us since the Kickstarter campaign and believed in our team. Without your support back in 2020, Flipper Zero would probably never have happened. Together with you, we built something far bigger than we ever imagined.

It’s important to understand that Flipper Zero has only 700 KB of flash memory available for firmware. And we ran into this limit very quickly, making it impossible to add new features. To work around it, we came up with dynamic apps loading from the microSD card — it allowed us to move device functions (including core features) outside the firmware into apps.

Firmware 1.0: a new approach to firmware architecture

This architecture became the foundation of the stable firmware 1.0, which was released in 2024 following the Apps Catalog launch. We polished the user interface and documentation. We also stabilized the firmware API and SDK for app developers, so they no longer had to rebuild their apps every month due to some API changes.

Since the firmware no longer required major changes, we decided to limit our work to maintaining the infrastructure and fixing critical bugs, while shifting our focus to building new devices (after all, we're called Flipper Devices).

By that point, an entire ecosystem of alternative firmware projects and communities had already existed, with people implementing every feature they could think of — even the weirdest ones. We consider our mission accomplished: we built an accessible development platform, and communities can now shape it into whatever they want.

We didn’t expect so many people to care so deeply about the development of the official Flipper Zero firmware. It's genuinely moving that this project and everything we’ve built together matters to you. That's why we’re ready to revisit some of our past decisions. We decided to allocate resources to continue supporting community contributions, but with a new approach.

What this means in practice:

  • Limited team resources — our team is still small, and all our attention right now is on building new DEVICES. We can no longer hang out in chats, jump on calls, and talk in real time the way we used to. From the outside, it might look like we're ignoring the community, but in reality, it's just focused work.
  • Async communication only — from now on, all communication with the development team will happen through requests in GitHub Discussions. You can vote on topics, and we commit to reviewing the requests that get the most votes. But these have to be concrete feature requests, formatted according to the rules. Abstract questions, general discussion, and help requests stay on Discord, Reddit, and social media.
  • New contribution rules — we'll now evaluate pull requests more strictly, as reflected in our updated contribution guide. This applies especially to AI-generated code that touches low-level libraries that is hard to verify, as well as changes that affect the device's UI and require edits in the documentation.
  • Integration and regression testing — it's important that code changes don't break existing features. That's why we're making public the integration test cases that our QA team used to test the firmware. These tests will need to be run for every change to the firmware code, and we'll bring the community in to help with part of the regression testing.

Once the total number of Flipper Zero users passed one million, direct real-time communication with the community became impossible. We receive a huge number of requests across every communication channel, to the point where we eventually had to disable direct messages on our social media accounts.

At the same time, in all this noise, it became impossible to separate what actually matters. You can’t really distinguish between requests that reflect real community needs and a single person’s niche request — everything just blends into the same white noise.

Vote for what really matters

We'll work on the feature requests with the most votes

We're moving all requests from the Flipper Zero community to GitHub Discussions. Now you can 🤚 vote for feature requests that really matter, so we can see what the community actually wants and prioritize them.

Please stay on topic

We'd really ask you to keep this space for genuinely important requests — ones that can realistically be implemented and that you're sure aren't just something you personally want, but something others actually need too. Otherwise, it just turns into noise, spam, and endless back-and-forth.

For discussions that aren’t suitable as feature requests, there's Discord, Reddit, Twitter, and our other social channels.

Good vs bad feature request
  • We're allocating resources to maintaining the Flipper Zero firmware. Our team will go through community requests weekly.
  • Communication with the development team will now happen only through GitHub Discussions. We'll work on the feature requests with the most votes.
  • Accepting PRs in the Apps Catalog will work as before.

If you still have questions, you can ask them at our AMA (Ask Me Anything) session on Reddit on Friday, July 3, 15:00 BST: All our core developers and managers will be there:

https://www.reddit.com/r/flipperzero/comments/1ukn1ir/official_ama_askmeanything_with_the_flipper_zero/

联系我们 contact @ memedata.com