Support Material 3+You.

[RokeJulianLockhart]

Having the application appear consistent with the system and well-made goes a long way in ensuring that it appears trustworthy (and not old, which matters for AV). Since the GUI is very basic, this should be trivial to implement, but shall become more difficult as more graphical activities are created.

Additional rationale is available at QuickLyric/QuickLyric#271 (comment).

[SkewedZeppelin]

Currently it uses the in-built system themes in order to avoid using any libraries like Android Support/Jetpack & Material libraries.

[RokeJulianLockhart]

#57 (comment)

@SkewedZeppelin, I wasn't aware that the concept of a system theme existed in AOSP (I'm not an Android app dev). I'm all for the consistency and lack of maintenance burden afforded by utilizing system components. However, do later AOSP iterations (like Android 15) implement M3+You natively, or is this new GUI paradigm also an attempt to force application vendors into Google component lock-in? I'm still all for this due to the customization and consistency benefits it provides, but it's a shame that theming the fundamentally correct way doesn't afford these benefits.

[Coehill]

@RokeJulianLockhart If you have some ideas for theming, or even better, are able to attach wireframes/screenshots, then a dev could come in and style it from scratch.

[RokeJulianLockhart]

#57 (comment)

@Coehill, I can't currently. I've always used Adobe Illustrator for this, but I can't afford the subscription anymore. I'll try to create something in Figma, but don't expect it. Until then, have a look at https://m3.material.io/foundations/layout/understanding-layout/overview if you're not familiar with the new design paradigm.