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

Android: modernize code #1709

Draft
wants to merge 23 commits into
base: master
Choose a base branch
from

Conversation

PatrykMis
Copy link
Contributor

@PatrykMis PatrykMis commented Apr 22, 2023

  • Restructure Gradle / Android Studio project
  • Convert build logic to fully Kotlin DSL
  • code restructure (reformat, optimize imports and cleanup)
  • avoid deprecated APIs and migrate to new ones (if needed)
  • Code improvements (following system's light/dark theme, enabling TTS pitch / rate / volume controls, etc.)

@beqabeqa473
Copy link
Contributor

beqabeqa473 commented Apr 22, 2023 via email

@PatrykMis
Copy link
Contributor Author

This is draft pull request (in progress). I've made it just to notice developers about work in progress.

@alex19EP
Copy link
Member

not sure if I like all those file mooving.

@PatrykMis
Copy link
Contributor Author

Why?

@alex19EP
Copy link
Member

because at the moment it's not of any use, we don't use different gradle modules...

@PatrykMis PatrykMis force-pushed the android-modernize branch 3 times, most recently from 86cded9 to ffedbb4 Compare April 29, 2023 14:12
@PatrykMis PatrykMis force-pushed the android-modernize branch 3 times, most recently from 21ee81d to 9d26dc7 Compare July 29, 2023 10:10
@PatrykMis
Copy link
Contributor Author

Hey @alex19EP , appreciate the feedback. Here's why I went with default Android Studio and Gradle structure:

  1. It's Familiar: Most Android devs know this structure, making it easier to jump in.
  2. Android Studio Benefits: The IDE has tools tailored for this setup, so why not make the most of them?
  3. Simpler Builds: Less custom stuff in Gradle means fewer headaches and smoother builds.
  4. Better Maintenance: Sticking closer to the default makes future updates smoother.
  5. Clear Layout: Easier to find code, resources, and configs.
  6. Resource Compatibility: Most Android docs and tutorials follow this structure. Easier for us to reference. I've updated scripts from outside of Android folder, too.
  7. Community Help: Need a hand? More devs will get our setup.
  8. Fewer Mistakes: Tried and tested structure = less room for slip-ups.

Just to highlight a few points. I think it sets us up well for the future, but I'm keen to hear your thoughts!

@alex19EP
Copy link
Member

alex19EP commented Feb 8, 2024

hello @PatrykMis looked at your pr again. some things I really like. however, I absolutely do not want to switch from groovy to kotlin. Don't get me wrong, if the entire project were in Kotlin, it would be logical, but now it looks like a change for the sake of change.

also I created and will merge #1863 so you should rebace your pr after it.

thanks.

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

Successfully merging this pull request may close these issues.

None yet

3 participants