Voice of the Proton Community app
DISCLAIMER: It's my ideea but due to going back and forth for hours, i had enough. As such, sorry proton and anyone else, the "corrected version" from Lumo is "wierd" but i hope i make it clear that (sadly for me....) it's still better whatever rambling i wrote. AKA proton or whoever, please ignore any "wording" and just focuse on the idea/suggestion. Since sadly it might not be clear why i suggest this app, aka for everyone to have a (well due to Lumo) have an easier, faster, more accurate, so on and on. Whatever, it's explained so here it starts:
Going forwards, I am going to suggest in a way that already exists just to show that it actually exists already, just not as an app.
This is intentional: by using existing tools like Sheets and Docs, the proposal proves that Proton has no excuse for not implementing this, as the entire system can be built immediately if someone creates the spreadsheet.
Now, open Sheets, create the columns for each section, like one is if it's for Sheets, Docs, Lumo, Drive, VPN, Mail, so on and on.
Other columns are for stuff like subgroup category, status (complete, rejected, ongoing, so on), and even if it's relevant for us, ok this is something new, since it can be "yes, each update" or "yes but only when complete" are both types that would trigger email notification if new updates happen.
So like this, there is a massive spreadsheet, heck it might be so big that the sheet pages/tabs/whatever they are called, will be used for stuff like Docs, Lumo, VPN, Email, Pass etc.
And for the column where each cell is a link to the actual suggestion post, as in a link to a Doc where the suggestion lives.
On the same row, meaning for the same suggestion, another cell (new column) could be for tips/FAQ for this new feature. Yet another link (new column) on the same row for bug reports. But honestly, it can all be done even in the 1st one, so this is really just extra steps for organization's sake. Meaning the columns are just an example since the whole reason for all this is just to showcase how, despite this app does not exist, the "funcitons" exist even if no one created them.
Proton as well as the person who created the document have direct edit rights but in a form of updating <- mind you, this also includes each person who reports a bug, makes new suggestion, writes a FAQ, guide, so on.
Ideea is that anyone else can use the suggest edits to: voice their opinion (like if half people want, half don't, this means this new feature MUST have an enable/disable option).
Anyone who has additional info, any bug reports where multiple people can voice that they are also affected.
And, even if some features have been implemented, people can still suggest new ideas to take it to the next level.
To rephrase it: new idea? 3 people said the same ideas? Well Proton can merge them into 1 and all 3 have the ability, separately, to separate it if there are some elements that were not clear (aka no merge since it's not the same).
Plus, due to our ability to link Sheets and Docs to Lumo, we can actually ask Lumo to help us find, categorise, even write, come up with new ideas, and more.
Ideea is that even if 100+ people are adding suggestions, Lumo (on the idea it's an AI (tool) and not person) can read all of them, sorting it in a way it's relevant for us and lisen to our feed back, like stuff we agree with, or do not (aka even if implemented, option to disable).
And like this, Lumo can generate "votes" (aka multiple people suggested multiple ideas and each person "voted" some, if not all, or even just 1, suggestion).
This is where the rule of Non-Destructive Editing or Preservation of Intent applies: Lumo helps create clear feedback and contributions to suggestions, bugs, and polls by ensuring that Clarify without Conflating.
Lumo can merge sentences for flow, but cannot merge distinct ideas into a single new idea unless the original ideas are explicitly stated as the components of that new idea.
Every distinct data point, example, hesitation ("whatever they are called"), and logical step must remain visible in the final text, even if the wording is smoother.
And then we can use what Lumo wrote and give a fast and accurate boting like a poll system
Ok, a poll system does not exist so I think that is a good sign to stop here since I said enough.