Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Min and Target SDK #146

Open
ghost opened this issue Oct 27, 2024 · 10 comments
Open

Min and Target SDK #146

ghost opened this issue Oct 27, 2024 · 10 comments

Comments

@ghost
Copy link

ghost commented Oct 27, 2024

Hey,

i saw that the App has Target SDK on 34 and Minimum SDK on 24 and I wanted to ask if you could make Target SDK to 35 for Android 15 and Minimum SDK to 26/28/29/31? (Higher is always better) I would appreciate that!

A higher Minimum SDK version implies that your app supports fewer Android versions, minimizing compatibility issues. Because higher SDK means also Versions which are supported better. It makes the work easier. because Android 12 (SDK 31) is the last version that receives security patches. Further more, the less minSdk, the more internal compatibility layers, techniques etc. For example, lower SDK versions require v1/v2 signing, have somewhat different optimization levels, etc.

@meypod
Copy link
Owner

meypod commented Oct 27, 2024

Hi
Thanks for taking the time to write this

Currently the app is being rewritten in jetpack compose with a new UI by a third party (which will be checked by me at the end),
which is why I'm not working on the current repo anymore

Moving to jetpack compose will reduce the maintenance burden for me a lot, which will help implementing new features and improvements faster

@meypod
Copy link
Owner

meypod commented Oct 27, 2024

I will consider moving up the min sdk as we go on, for sure

Thanks for the suggestion

@ghost
Copy link
Author

ghost commented Oct 27, 2024

Hi Thanks for taking the time to write this

No problem :)

Currently the app is being rewritten in jetpack compose with a new UI by a third party (which will be checked by me at the end), which is why I'm not working on the current repo anymore

Oh wow okay. When would this be available for us?

Moving to jetpack compose will reduce the maintenance burden for me a lot, which will help implementing new features and improvements faster

Oh nice

@ghost
Copy link
Author

ghost commented Oct 27, 2024

I will consider moving up the min sdk as we go on, for sure

Thank you so much!

Thanks for the suggestion

Np, thank you more!

@meypod
Copy link
Owner

meypod commented Oct 28, 2024

Oh wow okay. When would this be available for us?

I cannot give a timeframe, but its probably not any time soon, at least not in the next 140 days or so

@ghost
Copy link
Author

ghost commented Oct 28, 2024

@meypod Oh wow that's at least 6 Months...

@meypod
Copy link
Owner

meypod commented Oct 28, 2024

Sorry to disappoint you
Things may go faster or slower, but that's how things stand for now

@ghost
Copy link
Author

ghost commented Oct 28, 2024

No problem. I understand

@muhaaliss
Copy link

@meypod Will the new code be hosted in this repository or will you open a new repository?

@meypod
Copy link
Owner

meypod commented Oct 30, 2024

I have not decided yet, but I think it might be a new repo and keep this as is
but I will decided later

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants