Accrescent

@moshimotsu@floss.social Yes, we appreciate the feedback and we agree. We plan on posting an update soon and hope to maintain more frequent posts going forward.

@zhx02@mastodon.social Yes! We've been hard at work readying Accrescent for broader adoption by reworking our developer console to make it run more stably, fix bugs, tighten security, improve the UI, simplify development (so we can develop faster and so it's easier to contribute), and prepare for more feature additions. We've written tens of thousands of lines of code and hundreds of tests (most not public yet) to be merged which will help us accomplish these goals, and we're still working on more. While we can't promise any specific timeline, we're hoping to open up developer registration more broadly later this year so anyone can sign up and submit their apps to Accrescent. Happy to answer any more questions!

@zxzx01@mastodon.social RiMusic and Clipious should be delisted (not visible to new users) once we implement support for that in our servers.

We don't manage the updates to apps in Accrescent, their developers do, so if the app hasn't been updated, it's because they haven't uploaded a new version (or in some cases, because we haven't reviewed the update yet). But as far as we know, both Transcribro and NextPush are actively maintained.

@bebop@defcon.social Thank you!

@bebop@defcon.social Hi! We are still very much in active development and hope to post an update soon. We have GitHub activity, so be sure you're looking at all of our repositories, not just the one for the Accrescent app. For example, we've made extensive changes to Parcelo and changes to the console API, our API gRPC gateway, and console web app (plus a code generator project which is currently private but will be open sourced soon).

@moshimotsu There hasn't been much news, no. We've gotten a response from Google indicating that they're aware of the problems we have and the solutions we need, but nothing specific. The project is still in very active development! Most work recently has been on the Accrescent server at https://github.com/accrescent/parcelo/tree/massive-overhaul You can see a lot of changes there. They're just not on the main branch.

@Canning1452 Hi! No, we did not. It was written by a person without any AI assistance.

@anton_kaminsky@mastodon.social Accrescent has been developed mostly in unpaid developers' free time for most of its existence, so it hasn't had the time to mature enough for us to be comfortable allowing a large number of apps to be submitted. We don't want app developers to encounter too many issues. We artificially limit submissions right now for this reason, though developers frequently request submission access.

We recently received enough funding to sponsor a full-time developer though and have been making more extensive development progress in the last few months as a result.

@zahox@mastodon.social Hi! Was Cake Wallet installed through Accrescent, or another app store? That information would help us figure out the cause.

@eighthave Google has recently stated on the Android developers blog that they are working on allowing "experienced users" to install unregistered apps. But we plan to allow unregistered apps to be published regardless of whether that feature applies to Accrescent. If it doesn't, then yes, unregistered apps wouldn't be installable on certified Android devices.

If you've wondered how Android developer verification affects Accrescent, today we have a new blog post explaining briefly what it is, how it impacts us, and how we're responding.

https://blog.accrescent.app/posts/android-developer-verification/

#accrescent #android #appstore #security #privacy

@zahox@mastodon.social Unfortunately no. We have the capacity to manage communities on only a few platforms.

@shadowwwind If put into place, Android developer verification would affect us. Accrescent is used on stock Android and we officially support both stock Android and AOSP, and we plan to continue that even if Android developer verification is implemented. We have an upcoming blog post which will address the situation in more detail.

@shadowwwind We appreciate it. More to come!

@shadowwwind Thank you! It should be fixed now.

It's time for an update! Check out our blog for a new update on:

- What we've accomplished in the last 3 months
- What's next for Accrescent

Thank you to our supporters for making this possible!

https://blog.accrescent.app/posts/road-behind-road-ahead/

#accrescent #appstore #android #security #privacy

Accrescent 0.28.0 is out, including:

- Download cancellation support
- Better update scheduling (especially on Android 14+)
- UI improvements and bug fixes

Full release notes below!
https://github.com/accrescent/accrescent/releases/tag/0.28.0

#accrescent #appstore #android #security #privacy

@hfgdastyutret We plan to include more information in app listings in the future.

@niko4u Thanks!

Accrescent 0.27.0 is here! This is the most significant release we've made to date:

- New, stable app store API
- Complete installer rewrite, resolving all known bugs
- Tons of new features
- More snappy, correct, & informative UI

Check it out! 👇

https://github.com/accrescent/accrescent/releases/tag/0.27.0

#accrescent #security #privacy #appstore #android

Development on our roadmap is progressing smoothly. Our next app and server releases are undergoing final testing before deployment.

We hope to make an announcement soon about what Android's recently announced developer verification requirements mean for Accrescent. Stay tuned!

#accrescent #android #appstore #security #privacy

Since we published our blog post on the future of Accrescent, donations have increased dramatically.

According to the rates in that post, we should now be able to fund full-time development through at least May 2026!

Thank you to our community for your monumental support!

Because of you, we can dedicate ourselves fully to our mission of building a modern Android app store focused on security, privacy, and usability.

If you want to read the original blog post: https://blog.accrescent.app/posts/the-future-of-accrescent/

Or if you want to see our plans: https://blog.accrescent.app/posts/progress-update-and-roadmap/

#accrescent #security #privacy #android #appstore

Today is the day! Read all about our development progress, view our roadmap for the future, and check out the new projects we're releasing as open source in our new blog post!

https://blog.accrescent.app/posts/progress-update-and-roadmap/

Check out our new repositories:

https://github.com/accrescent/android-bundle
https://github.com/accrescent/directory
https://github.com/accrescent/directory-api
https://github.com/accrescent/ina

#android #security #privacy #accrescent #appstore

@fonos@mastodon.social @blueluma@mastodon.social Thanks! We'll look at them!

@blueluma@mastodon.social We'll look into it! We only supported GitHub Sponsors at first because it doesn't have any transaction fees (so your full donation goes to us) and to simplify keeping track of donations for us, but since other options have been requested, we'll consider them.

Accrescent depends completely on donations to run. Today we share a significant update in our new blog post on the future of Accrescent: https://blog.accrescent.app/posts/the-future-of-accrescent/.

New releases of Accrescent and our developer console are also out, with Android 16 updates and Material 3 changes. Check them out!

https://github.com/accrescent/accrescent/releases/tag/0.26.0
https://github.com/accrescent/parcelo/releases/tag/0.12.0
https://github.com/accrescent/console/releases/tag/0.12.0

#security #privacy #accrescent #android #appstre

@eskuero We appreciate you mentioning this. Unfortunately, we don't currently have the capacity to develop and maintain official documentation for how to run Accrescent independently. It would also be very difficult for a third party to keep up with running Accrescent right now since the backend is constantly changing and often requires manual intervention to update which requires special knowledge of how Accrescent works. We may consider supporting documentation once Accrescent is more stable.

With the Amazon Appstore shutting down, it's becoming even more important to invest in sustainable alternative stores you can trust.

See how you can invest in Accrescent's future! A little help goes a long way:

https://accrescent.app/faq#contributing

More information on the Amazon Appstore discontinuation on Android:

https://www.amazon.com/appstoreonandroidFAQ

#privacy #security #appstore #accrescent #android

With the release of Parcelo 0.11.0, we've made some significant changes to our server infrastructure. App developers can now find the developer console at console.accrescent.app.

If you encounter any issues, please let us know ASAP through our socials or contacts on our site.

#security #privacy #android #appstore #accrescent

Accrescent 0.25.0 is out with Android 15 app archiving support, Private Space support, and settings UI improvements!

We also forgot to announce that since 0.24.0, Accrescent supports in-app predictive back!

Check out the release notes below 👇

https://github.com/accrescent/accrescent/releases/tag/0.25.0

#privacy #security #appstore #android #accrescent #opensource

Accrescent recently surpassed 1,000 stars on GitHub 🥳! Thank you to everyone for your continued support!

If you'd like to help us grow, check out https://accrescent.app/faq#contributing. There are lots of ways to contribute even if you can't code!

https://github.com/accrescent/accrescent

#security #privacy #appstore #accrescent #android

Accrescent 0.24.0 is out with settings menu accessibility improvements, target SDK 35 (Android 15), and LOTS of translation and dependency updates! 🎉

Download it from our website at https://accrescent.app or read the changelog below 👇

https://github.com/accrescent/accrescent/releases/tag/0.24.0

#accresent #security #privacy #appstore #android