• General
  • Is There A Roadmap For Upcoming Features?

I would like to see a list of upcoming features that are currently being worked on. I know about the 2FA fingerprint unlock, but it is a bit cumbersome/impossible for a non-daily GOS user to have a good overview of all upcoming features. Is there a thread here in the forum for such a purpose?

    ttmp12 Is there a thread here in the forum for such a purpose?

    Traditionally the GrapheneOS project has not published a roadmap. At various times various features are mentioned as being in development, but I am unaware of "We plan to do feature X before feature Y" statements, let alone target dates.

    Please note that I do not speak for the GrapheneOS project.

    ttmp12 I would like to see a list of upcoming features that are currently being worked on.

    From what I gathered from just reading here on the forum and the chats, GrapheneOS based on Android 15 is highest priority now. That feature is expected to be finished and released within a few days. After that, additional VPN leak protections will be highest priority. Most are fixed already and has the fixes released, but there are a few known VPN leaks left. The development team has said this will be highest priority to fix after Android 15. As you mentioned yourself, fingerprint+PIN unlock is another feature being worked on. I have the impression this feature may be nearing completion, so maybe only a few months away. Another feature that is being worked on is App Scopes, to prevent communication between specific apps inside the same profile. This feature is probably far away from completion, as the developers have repeatibly hinted it is unexpectibly hard to do and even asked volunteers to help out with the implementation, indicating they currently paused development of that feature internally. A wild guess could be the feature is a year away from being ready.

    Thanks for all the answers! I would like to see an overall roadmap, even if features are pushed or delayed. This would help me as a GrapheneOS user to get a better understanding of where the project currently stands. A funding structure like Monero would also be interesting, where community members can make specific donations for feature development.

      ttmp12 I would like to see an overall roadmap, even if features are pushed or delayed.

      The best place to find that info has already been shared: the issue tracker. Filter by tag and you'll know what's being worked on and the features' priorities, which are updated from time to time.

      Other places to get updates would be by following the official project account on whichever social media site you prefer. They're listed on the contact page: https://grapheneos.org/contact

      ttmp12 A funding structure like Monero would also be interesting, where community members can make specific donations for feature development.

      Not sure I'm following here. You can already donate with Monero: https://grapheneos.org/donate#monero

        • [deleted]

        other8026 Just to give you context the Monero community fund things they want or need in the Monero currency at https://ccs.getmonero.org where they kind of vote for things they need or want with XMR donations. It's based on donations made from everyday Monero users.

          [deleted] thanks. I thought maybe they were suggesting something like that, but wasn't sure so I didn't address it.

          Basically, GrapheneOS accepts donations for the work that's done, but don't want donations for specific features to determine how developers prioritize their time. There's also the risk that someone or a group of people donate for one specific thing and they don't get exactly what they want.

            ttmp12 A funding structure like Monero would also be interesting, where community members can make specific donations for feature development.

            Non-profits usually don't want people to donate for specific features, as the project team loses the ability to work on what they consider important. Tor Project is an example of a non-profit that accept both general donations like GrapheneOS does today, but also feature specific donations from govermental institutions. When applying for donations from governmental institutions one has to pitch what feature the money will go to develop. The Tor Project has been unhappy about this, and posted about it on their blog repeatedly. Governments always only donate for developing anti-censorship features, they don't ever donate for security, privacy or anonymity features. The Tor Project was stuck with a weak design for onion services for many years, despite already having a thought up design of a new much improved implementation, but couldn't implement it as all their effort went into pluggable transports instead as that was what governmental institutions funded. This issue is not just with software developments. A non-profit working for positive environmental change and saving endangered species ended up in the same situation. They launched a donation campaign where you could donate towards effort to save a specific species of endangered animals in the hope to raise the amount of donations received. But people only donated towards saving the cute animals, not at all the ones that were the most endangered and in need for help.

            Bottom line: Non-profits do not want donations for a specific cause, but want to use their own expertize to judge where to put the money.

            Yes the explanations here are largely correct. GrapheneOS has a lot to keep on top of dealing with such large upstream codebases - linux, chromium and AOSP are all huge, complex and constantly changing

            Due to the nature of the project the GrapheneOS team has to act quickly to include upstream security fixes and fix any bugs or issues that are discovered. This last year our developers have spent huge amounts of time working on fixing up the VPN leaks and dealing with local device vulnerabilities following the reporting of those problems. Also various issues in AOSP which we needed to fix so we could ship security updates in a timely fashion. None of that was planned/scheduled work. They werent things we were prepared to ignore.

            If our funding was tied to new features we would not have the agility to switch focus to work on fixing things. Keeping the OS secure and stable is something we, and we think our user base, find critically important.

            We are a relatively small team. We have a number of highly talented and productive developers working on GrapheneOS but there is always much to do. We are constantly actively recruiting, but its not quick or easy to bring new developers into working on the project. They have to have the right skill set, learn the way we do things and some people are only really productive under certain work regimes. So we are not able to just throw money at a new feature, hire a load of new devs and get results.

            Every new feature also requires ongoing maintenance. Sometimes lots of work. We cant just let features that people depend upon suddenly stop working. So we have to think carefully about potential future maintenance burden before adding anything.

            Due to the complex codebase, the necessity to implement features in a way which make it as easy as possible to maintain in the future and to have it done 'correctly' rather than as fragile hacks, features often require far more work than anyone predicted. Its very hard to set realistic budgets for any new feature.

            We have a policy of rejecting feature tied funding. For the reasons I outline and also because of the potential for disagreements about what qualifies as a feature being 'complete'.

            The quality of the operating system speaks for itself. If you value it please consider donating. Recurring donations are most useful as it gives us more certainty about future levels of cash flow and we can increase the number of people on our team with more confidence.
            https://grapheneos.org/donate

              • [deleted]

              Carlos-Anso This was a very informative post, thank you for explaining to everyone.