[Feature request]: Add Butterfly to IzzyOnDroid

[Gropinou]

Is your feature request related to a problem? Please describe

No response

Describe your feature request!

Add Butterfly to Accrescent so that it can have the convenience of an app store without the 10 days of waiting for release after it is published.

Additional context

For example, 2.4.0 Beta 1 was released on July 14th, and appeared on F-Droid on July 24 (10 days later). This means that if a bug was fixed, users would still experience/complain about it even after being fixed.

Code of Conduct

• I agree to follow this project's Code of Conduct

[CodeDoctorDE]

Hello, thanks for your idea.
I'm always open for new stores if they don't add more maintenance.
The f-droid delay was a problem time to time and I see the problem here.

I'm also thinking about izzyondroid https://apt.izzysoft.de/fdroid/, I think this could be also a good alternative.
I haven't heard about Accrescent. On the first view, it looks like it isn't really an "f-droid repository" and needs maintenance.

Personally, I'm not against reuploading my app on other appstores. If you do this, I would encourage showing it as "unofficial".

[Gropinou]

Izzyondroid is definitely a bit faster.

[CodeDoctorDE]

Okay, then I will try to get in contact to get this working :)

[Gropinou]

Cool

[CodeDoctorDE]

you can follow it here: https://gitlab.com/IzzyOnDroid/repo/-/issues/827

[CodeDoctorDE]

izzy on droid won't accept us due to the binary size I can't sadly reduce. Need to see what else i can do

[IzzySoft]

I've already pointed you to Strategies To Reduce Flutter App Binary Size. Another useful source is Reduce your app size. If you scroll down there, you see a section stating "Avoid extracting native libraries" – you already do that, your native libraries are stored uncompressed. Reverting that, would bring down the APK size by approx. 10 MB (by setting useLegacyPackaging to true in your build.gradle.kts). The only disadvantage of that would be the libraries would need to be extracted on-device when the app is installed/updated, thus needing extra space there – at the advantage of less data transfer.

Not saying you have to go that path, just mentioning that it does exist, and you have that option.

[CodeDoctorDE]

Thanks for pointing it out. I tried the strategies but it only gave ~1mb less. I analyzed the apk a bit and found out that most of the size comes from native libraries.
10MB would be fantastic I think. But useLegacyPackaging sounds like it's outdated and shouldn't be used?
Should I make a new buildconfig for useLegacyPackaging?