I believe you should be speaking about Sapio so that many people contribute to its community driven database. Just saying (:
I believe you should be speaking about Sapio so that many people contribute to its community driven database. Just saying (:
@degoogle I believe you should be speaking about Sapio so that many people contribute to its community driven database. Just saying (:
You're viewing a single thread.
I had contributed before but ultimately I don't find it that useful because the app is incomplete. The concept is valuable and I like the evaluation visualization, but incomplete or incorrect data make it much less useful.
Only the latest "evaluation" of an app is saved. It was very common for me to reopen Sapio only to discover someone had assigned a different evaluation from the one I had given and my evaluation was gone.
The user should be able to add a comment saying which features don't work. Just saying "Some features do not work" is not that helpful. Some users may have tested an app more thoroughly than others and so can provide details about specific parts of the app that do or do not work.
I have relied on completely degoogled android for many years now (first LineageOS and then GrapheneOS) but I almost didn't even try because I didn't know if my apps would work. A database like this would have been very useful at the time. Hopefully it can be made even better.
@banana The idea is to have an overview of how an app is behaving without Google Play Services. We have a few scenarios only to me:
- An app is using Play Integrity (for instance) at start and does not launch. Red.
- An app works in general properly but has a feature like connecting to Google Health API that does not work. Yellow.
- An app does not have notification working. Yellow.
- An app works perfectly. Green.@banana About Sapio displaying only the latest evaluation, my idea was that we have enough contributions to auto regulate and have a clear snapshot of the current behavior of an app without Google Play Services.