Accrescent Store?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Hey,
could you publish MicroG in the Accrescent Store? I would love to see you there and download the App from there.
Maybe you ask why we want this or what Benefits it would have for us as Users.
The Benefits for me would be a few, like these:
I could get MicroG from Accrescent, which I already installed and use to download Apps. I prefer Accrescent over Github or F-Droid, because on Accrescent the App get's checked before it comes to the Store and the Apps are always checked, like for example the SDK of Apps, if there is Malware and more.
It would make it a lot easier for me and save me time, because MicroG is one of the few Apps, I use in F-Droid/Github to download. And if my last few Apps would come to Accrescent, I wouldn't need to use Obtainium or F-Droid. I just use it until my last few Apps on there come to Accrescent.
Apps on Github or F-Droid are not checked, but on Accrescent they are going trough Filters always. And I think that would make it more secure. And since Accrescent is on a good way in terms of Security and Privacy, I think that it will be really good in the Future. And I think that Apps which value Security and Privacy should make it available there. Because Accrescent have the same values in Security and Privacy.
I really hope that you Guys could make that possible, because it would have great Benefits for us as Users. And think like that: If we support them by adding Apps, we help them to grow from Alpha to Stable.
Accresent features I think matter for MicroG.
Security:
Signed repository metadata
App signing key pinning
Name verification
Privacy:
No remote APK signing
No accounts
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is identified. Start by reviewing the linked Accrescent features and the project's current distribution process; done would mean confirming whether MicroG can be published there and documenting or completing that path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile-dev, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100