APK availability about pixapencil HOT 8 CLOSED

Hi - thanks for the suggestion,

I am planning on releasing the .apk file in the releases section as you mentioned, and I'm also planning on putting the app on the F-Droid repo. As well as putting the app on the Google Play Store, which I think is also a good idea since it appeals to a significantly larger audience when compared to F-Droid. I value FOSS stores such as F-Droid and open source apps much more when compared to the Google Play Store, although the limiting factor is the small audience.

Although after having a look online, my one question would be whether it's actually possible to release an app on F-Droid as well as the Google Play Store. Hopefully it is, because I don't want to pick one store over another.

However I only want to do these things when the app is completely stable and relatively bug-free. I have observed a couple of bugs which I am working on fixing; when these are fixed I plan on releasing the app.

I added landscape support to the app, but while testing it on a Galaxy A10 I noticed that - contrary to the emulator - the pixel grid data gets cleared when the user rotates their screen. This shouldn't be happening, and perhaps when I fix this bug I will consider releasing it 😃

I also want to work on a couple of more features before releasing the app, just so the experience is better.

I plan on releasing this app in the next month or so. When the time comes, I will create a pull request on your F-Droid repository on GitLab. I will be looking forward to having the app on your store in the future!

Thanks for posting the issue! If you have any questions you can reply and I will do my best to answer them.

from pixapencil.

Thanks a lot! Should you need help with the F-Droid listing, I might assist. If you want a test-drive before that, with the APKs on the releases I might offer such via my repo. Looking forward to the first one!

from pixapencil.

It's always possible when conditions are met – the other question is if it's needed. If you mean F-Droid and my repo, a double-listing only makes sense if you either have a fast-paced release cycle (and thus need faster listings: F-Droid usually needs a few days to pick up as it needs to pass the build cycle there, while my repo picks up the ready-to-run APKs from your releases). If you mean F-Droid vs. Play, I guess that's a quite frequent combination (whether "F-Droid main" or my repo).

If you don't plan for GMS (or other proprietary components), you should be fine for all 3 places. In this case you shouldn't include them with your app at all. For other things, maybe the collection of my notes gives you some ideas/help.

from pixapencil.

Thanks for the info!

from pixapencil.

I will be submitting a pull request soon to F-Droid.

from pixapencil.

Great, would it be possible to release it on both stores? If so, are there any things I need consider? I don't plan on using Google Play Services in my app, though I'm not sure if it's possible to publish one without using them, that's what I'm kind of confused about.

from pixapencil.

@therealbluepandabear if you need help, just "yell" 😄 F-Droid will ask for:

• fastlane metadata (see my Fastlane Cheat Sheet for help on that)
• tagged releases

(best processed in this order, so fastlane is covered by the tag)

from pixapencil.

I have released v0.0.1-beta1 on GitHub so I consider this issue partially closed, although it is non-production ready and contains bugs.

Once I release v0.0.1 I will release it on F-Droid.

I will now close and lock this specific issue and migrate the F-Droid problem to #79.

If you have any questions in regards to the F-Droid release comment on issue #79,

from pixapencil.