Migrate to Material 3 (M3)

[rfc2822]

Time to have fun

https://developer.android.com/develop/ui/compose/designsystems/material2-material3#phased-approach

This is a meta-issue and can be closed when everything is M3. Please don't add things here yourself.

When rewriting things to M3, please apply the new App Architecture as discussed as well as it's possible without rewriting core features (for instance, I wouldn't touch data layer things too much during the rewrite):

• In general, one screen has three files:
  1. SomeScreen.kt with the @Composable SomeScreen() (only UI, no or little UI logic)
  2. SomeScreenModel.kt with the ViewModel for SomeScreen (UI logic and interface to data layers, if required); usually contains a UI state data class + methods to calculate state for the UI + methods for events that come from the UI
  3. SomeActivity.kt with the Activity (if the screen is an Activity) – should only contain the contract
• Use UiState classes as described in App Architecture. One explicit UI state data class + mutableStateOf(UiState()) private set in the model is preferred, but you may have to use Flows or other methods like multiple states if it fits better.

Tasks:

• Add M3 theme and apply to AboutActivity #731
• Rewrite ui.intro to M3
  • Rewrite BatteryOptimizationsPage to M3 #741
  • Rewrite OpenSourcePage to M3 #740
  • Rewrite PermissionsIntroPage to M3 → PermissionsActivity #757
  • Rewrite TasksIntroPage to M3 → TasksActivity #759
  • Rewrite WelcomePage to M3 #739
  • Rewrite IntroActivity to M3
• Rewrite TasksActivity to M3
• Rewrite PermissionsActivity to M3
• Rewrite DebugInfoActivity to M3 #742
• Rewrite AccountsActivity to M3

[devvv4ever]

These themes reflect our current color scheme in M3:

material-theme-classic.zip
material-theme-classic-reversed.zip

[rfc2822]

We should also follow the recommended App Architecture more when refactoring. Like having more clear and separated UI state holders, using Compose state in ViewModels etc.

[rfc2822]

Now we don't have FABs or other accent elements yet but I also like the "reversed" theme more:

[devvv4ever]

I've read a bit more into the color scheming of M3 and it seems unless we want to define everything (!) on our own we can't use our brand color green (with orange in addition) anymore.

I've adapted our colors a bit and here is an updated version for now that looks more appealing:

material-theme-moreappealing.zip

It now looks like this:

[sunkup]

I've read a bit more into the color scheming of M3 and it seems unless we want to define everything (!) on our own we can't use our brand color green (with orange in addition) anymore.
[...]
It now looks like this:

Well, this definetly makes for a better integration with jtxBoard. They look the same now 🥂

[devvv4ever]

I've read a bit more into the color scheming of M3 and it seems unless we want to define everything (!) on our own we can't use our brand color green (with orange in addition) anymore.
[...]
It now looks like this:

Well, this definetly makes for a better integration with jtxBoard. They look the same now 🥂

but we're still green, while jtx is yellow :P wooow

[devvv4ever]

Updated Color Schemes:

material-theme-colors-updated.zip
material-theme-colors-fit.zip

[rfc2822]

#691 (comment)

@rfc2822, when shall the next https://github.com/bitfireAT/davx5-ose/releases be, with this included? I'd like to know when to expect it on F-Droid.

We plan to make a public beta soon, and then release maybe in 1 week or so – if everything goes well