Add comparison table

[efb4f5ff-1298-471a-8973-3d47447115dc]

Comparison table should at least include the following app stores

• Google Play Store
• Accrescent
• Aurora Store
• F-Droid
• Obtainium
• Sandboxed Google Play Store from GrapheneOS?

The table should be an simple overview to compare security/privacy related components and maybe some features. If the platform supports it use checkmark. If it doesn't support it use red cross.

Table should not include extensive explanation about why it does/doesnt support something. If documentation is available for it then u should link to it.

[PoorPocketsMcNewHold]

Aggree on that. Would make an easy way to showcase the purpose of Accrescent compared to the other available offerings on a first glance. Especially for a dev searching the optimal place to release their apps.

[efb4f5ff-1298-471a-8973-3d47447115dc]

@lberrymage just noticed that i kind of created a duplicate of https://github.com/accrescent/meta/issues/19

Do you want me to close this one and put all the info there or would u like this to stay open in favor of #19 ?

[lberrymage]

I'll close the other in favor of this one since this one is more extensive.

[lberrymage]

It may also be good to add Obtainium to the list.

[efb4f5ff-1298-471a-8973-3d47447115dc]

Didnt know about that one, added to the list!

[efb4f5ff-1298-471a-8973-3d47447115dc]

Should the table be directed to users or to devs? Maybe two tables to address both parties?

[lberrymage]

I think it would be best to have two tables, yes.

[efb4f5ff-1298-471a-8973-3d47447115dc]

Do you want the table to be added to the readme of https://github.com/accrescent/accrescent or only in the docs repo? IMO we should add it to both

[lberrymage]

I think it would be best to add comparisons to the website and link them in the README (maybe with a brief summary of features like there is now). There's a lot to compare and I think the README might become a little cluttered if we try to fit all of that information in there.

[efb4f5ff-1298-471a-8973-3d47447115dc]

@lberrymage What do you think of this? Note: Values in tables are just for example purposes

Users features

App store	Accrescent	Aurora Store	F-Droid	Google Play Store	Obtainium
Search and Discovery	✅	✅	✅	✅	✅
Principle of least privilege	✅	✅	✅	❌	✅
User Feedback Mechanisms	✅	❌	✅	✅¹	✅

• ¹ U need to have a Google Account

Developers features

App store	Accrescent	Aurora Store	F-Droid	Google Play Store	Obtainium
Developer console	✅	✅	✅	✅	✅
Example 1	✅	✅	✅	✅	✅
Example 2	✅	❌	✅	✅	✅
Example 3	✅	✅	✅	✅	✅

[lberrymage]

I like it and think it's a good place to start, although imo Sandboxed Play Store could be removed since it isn't really its own alternative in terms of features, especially from the developer PoV.

[efb4f5ff-1298-471a-8973-3d47447115dc]

Edited the tables. What i need from u is a list of user/dev features u think matters and based of that list i will investigate if the appstores do or dont have that feature.

If u stuck thinking about features (i dont think that would be hard for u tbh) maybe think about security/privacy related ones

[efb4f5ff-1298-471a-8973-3d47447115dc]

Could still be mentioned in the User Table tbh

GrapheneOS supports Sandboxed Google Play, which runs Google Play Services fully sandboxed like any other regular app. This means you can take advantage of most Google Play Services, such as push notifications, while giving you full control over their permissions and access, and while containing them to a specific work profile or user profile of your choice.

[lberrymage]

Edited the tables. What i need from u is a list of user/dev features u think matters and based of that list i will investigate if the appstores do or dont have that feature.

If u stuck thinking about features (i dont think that would be hard for u tbh) maybe think about security/privacy related ones

In the user table I would list:

• Unprivileged, unattended updates (yes/no - Accrescent (on Android 12+), maybe Aurora and/or Obtainium on Android 12+)
• Split APK support (yes/no - Accrescent, Google Play, maybe Aurora)
• Usable without account (yes/no - Accrescent, F-Droid, Obtainium, special note for Aurora)
• Delta updates (yes/no - Google Play, maybe Aurora)

In the developer table I would list:

• App update REST API (yes/no - Google Play)
• Required personal info (Google Play: https://support.google.com/googleplay/android-developer/answer/10788890, Accrescent: email)
• Time to update (Accrescent: ~1 minute unless new sensitive permissions are requested, would be careful about how this is listed for Google Play and F-Droid so it's accurate)
• App signer (developer/store - Google Play: store (except apps created before Play App Signing became required), F-Droid: store (except for apps with reproducible builds), Accrescent: developer)

These lists aren't exhaustive, but I think they're some of the most important features to mention. I'm open to suggestions.

Could still be mentioned in the User Table tbh

GrapheneOS supports Sandboxed Google Play, which runs Google Play Services fully sandboxed like any other regular app. This means you can take advantage of most Google Play Services, such as push notifications, while giving you full control over their permissions and access, and while containing them to a specific work profile or user profile of your choice.

Maybe, but I think that gets confusing, especially for those who aren't familiar with other mobile operating systems and GrapheneOS specifically. Sandboxed Google Play, Obtainium, and Aurora also aren't seprate app stores per se. The first is a way to run Google Play, the second pulls from multiple sources, and the third is a third-party client for Google Play. On the other hand, Google Play, Accrescent, and F-Droid source apps from their own stores and have their own clients and developer submission processes.

Perhaps we should start with those three and see whether it's worth adding others later.

[efb4f5ff-1298-471a-8973-3d47447115dc]

Maybe, but I think that gets confusing, especially for those who aren't familiar with other mobile operating systems and GrapheneOS specifically. Sandboxed Google Play, Obtainium, and Aurora also aren't seprate app stores per se. The first is a way to run Google Play, the second pulls from multiple sources, and the third is a third-party client for Google Play. On the other hand, Google Play, Accrescent, and F-Droid source apps from their own stores and have their own clients and developer submission processes.

Perhaps we should start with those three and see whether it's worth adding others later.

The reason i mentioned these projects is because they are all mentioned on https://www.privacyguides.org/en/android/#obtaining-applications

Wanted to make it kind of future proof because i see this application getting listed on their site in the future.

Im open to removing them though if thats what u think is the route to go for now

These lists aren't exhaustive, but I think they're some of the most important features to mention. I'm open to suggestions.

For the user table i could ask around to users of these stores whats important to them and post it here to see if anything can be included.

Can try the same for the dev table.