Project ideas from Hacker News discussions.

Fairphone 6 and PostmarketOS working main camera

📝 Discussion Summary (Click to expand)

3 Core Themes from the Discussion

Theme Summary Representative Quotation
1. Preference for a for‑profit model Participants argue that a for‑profit structure is simpler, more flexible, and still allows free sharing of creations. “not take the frustrating and useless road of a non‑profit structure … The for‑profit will be simpler and give you more liberties, and if, in the end, you have the good mindset that you want your creations to be shared freely, you can do it anyway. It is a state of mind.” — greatgib
2. Open‑source mobile OS built on volunteer effort faces OEM and driver hurdles The community repeatedly points out that projects like PostmarketOS cannot easily partner with OEMs and must rely on hacks, leading to delayed or fragile support. “PostmarketOS can't partner with any OEM/ODM and volunteers have to use hacks to unofficially implement basic Android 1.0 functionality years after a device was released?” — zb3
3. Hardware/driver limitations hinder practical use Technical concerns focus on missing driver access (e.g., PDAF pixels) and certification issues that make real‑world functionality hard to achieve. “Does this HW have access to PDAF pixel data?” — megous

These three themes capture the most prevalent opinions expressed in the thread.


🚀 Project Ideas

Generating project ideas…

CarrierCertify

Summary

  • A SaaS platform that lets developers upload custom ROMs or modem firmware and run automated carrier-certification tests (including emergency calling) on a fleet of real smartphones.
  • Eliminates the need for each project to negotiate expensive carrier test lab access.

Details

Key Value
Target Audience Mobile OS developers, FOSS phone projects, startup teams building carrier‑ready devices
Core Feature Cloud‑based test runner exposing carrier test suites (e.g., 3G/4G/5G emergency call handshakes, SIM PIN handling) via a simple API
Tech Stack Backend: Go + Kubernetes; Test devices: real Android phones (Pixel, Librem 5, PinePhone); API: REST + Webhooks
Difficulty Medium
Monetization Revenue-ready: Pay‑per‑minute test execution + monthly tier for unlimited runs

Notes

  • HN commenters like cure_42 and NewJazz lament the hassle of “getting authorized to test emergency calling capabilities” – CarrierCertify solves this directly.
  • Provides a practical utility for volunteers who otherwise “use hacks to implement basic Android 1.0 functionality years after a device was released”.

DriverStack

Summary

  • A modular driver‑development framework that supplies pre‑certified, GPL‑compliant drivers for common smartphone components (camera, modem, sensors) which can be dropped into PostmarketOS or AOSP builds.
  • Reduces the volunteer burden of writing low‑level drivers from scratch.

Details

Key Value
Target Audience FOSS mobile OS maintainers, hobbyist developers, OEMs looking to adopt open‑source drivers
Core Feature Library of reusable driver modules written in Rust, auto‑generated from hardware specs, with a plug‑in system for adding vendor‑specific code
Tech Stack Rust core, QEMU for emulation, Buildroot for packaging, CI via GitHub Actions
Difficulty High
Monetization Hobby

Notes

  • zb3 remarked that drivers “should be implemented by those who work on them” but volunteers often hit roadblocks; DriverStack gives them a ready foundation.
  • Aligns with NewJazz’s call for “real OS support that didn’t have to rely on third‑party volunteers”.

FOSSphone Marketplace

Summary

  • An online marketplace and certification service for open‑source mobile OS images that have passed a standardized hardware compatibility test suite.
  • Sellers can list certified builds, receive legal guidance, and earn revenue through a share‑of‑sales model.

Details

Key Value
Target Audience End‑users seeking reliable open‑source phones, hardware startups, community maintainers
Core Feature Curated OS listings with badge system (e.g., “Certified‑FOSS ✓”), automated test reports, and a marketplace checkout
Tech Stack Django + PostgreSQL for marketplace; Dockerized test runners; Smart‑contract based royalty distribution
Difficulty Medium
Monetization Revenue-ready: 15 % transaction fee + optional certification subscription

Notes

  • References to “Murena could, Jolla could, GrapheneOS could do that too” (zb3) indicate demand for official, non‑user‑hostile OS options; the marketplace fulfills that need.
  • Addresses the frustration of “volunteers have to use hacks” by providing vetted, certified images.

Read Later