-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace progress bar with feature list #122
Comments
Hi @iNPUTmice. Thanks for your input! I wanted to keep the overview as simple as possible so it could be "sorted" / "ranked" with Conversations as a kind of "reference implementation" on the top. How many boxes would you say need to be checked to get to a "100%"? 😄 |
You can - if you want to - keep the simplicity of the progress bar. But base it on some hard criteria such as the features mentioned above and then put the criteria in fine print somewhere. However I don’t think it makes sense that something like Converse which doesn’t support multi users chats or the aesgcm uri scheme should have the same percentage as Conversations. (Nothing against converse just picked that as an arbitrary example) Edit: I don’t care whether or not the features are expressed as a percentage or as checked boxes; One is easier for the user the other one would give users the option to priorities certain features (like I don’t use trust management anyway or i don’t use group chats). But the way the percentage is calculated right now feels completely random. |
So, basically we could have something like Sort by number of checked boxes as a default and then have the user apply filters for their preferences. Could work. 😄 |
Is this still developed? I see the site recomended yet users won't know that apps are missing group or files from that bar. (developed aka add more columns, I've seen the updates) |
I’m not really sure what the progress bar is supposed to indicate. Also some of the projects which are at 100% have what I would argue is limited support for OMEMO. I therefor propose to replace it with a feature check box table that indicates various levels of support. (Sub) features that are historically milestones in the OMEMO development process include
The text was updated successfully, but these errors were encountered: