Material Design 3 #142
Replies: 18 comments 2 replies
-
I have already tried to see what I could change to adapt Material Design 3 but as it stands, M3 seems to be way more limited in design than M2. It takes a lot of the choices you had in M2. But I'll continue looking into it. |
Beta Was this translation helpful? Give feedback.
-
Yea, I see this as being a more down-the-road addition, as (hopefully) by the time 1.0 rolls around, there will be far more options with Material 3 |
Beta Was this translation helpful? Give feedback.
-
ColorScheme.fromSeed using Kaiteki's pink leaves a lot to be desired. |
Beta Was this translation helpful? Give feedback.
-
Well for |
Beta Was this translation helpful? Give feedback.
-
Uhh, Flutter is technically using it everywhere since the app theme propagates globally throughout the app. This nothing more than a color scheme. I also tried setting |
Beta Was this translation helpful? Give feedback.
-
When I say "everywhere", I'm also referring to the accent color and background, which will probably be easier to set once Material Design 3 is better implemented in Flutter. |
Beta Was this translation helpful? Give feedback.
-
I found out why |
Beta Was this translation helpful? Give feedback.
-
Maybe have it toggleable in settings? I actually kinda like it. |
Beta Was this translation helpful? Give feedback.
-
The settings are broken lmao. (I still have nobody who can properly assist me in state management and data persistence) |
Beta Was this translation helpful? Give feedback.
-
I wish I could help but I've literally never used dart or flutter before :( For settings, maybe the key value schema could work? https://www.raywenderlich.com/5965747-data-persistence-on-flutter |
Beta Was this translation helpful? Give feedback.
-
I am aware of using shared_preferences to store simple data types as key-value, but it's going to suck real hard later on with more complex settings, as the code maintenance will shoot through the roof. (This is my main gripe with Flutter tutorials and apps, that they don't actually attempt to be massive) |
Beta Was this translation helpful? Give feedback.
-
Perhaps with SQLite then? Seems to be better for bigger data. For the one desktop app I've ever written (in Electron), I used key-value stores for settings but SQLite seems to makes more sense for this.
|
Beta Was this translation helpful? Give feedback.
-
The problem is that we aren't aiming for storing large amounts of data, or tables. Kaiteki might store several themes, boolean flags, strings, ints, arrays of compound data, etc in the future. |
Beta Was this translation helpful? Give feedback.
-
The only thing I can think of then is key-value stores combined with some custom files for things like themes :/ |
Beta Was this translation helpful? Give feedback.
-
Sneak peek of M3 |
Beta Was this translation helpful? Give feedback.
-
Adopted the M3 contrast when landscape |
Beta Was this translation helpful? Give feedback.
-
@Craftplacer when are we getting dynamic colors :D |
Beta Was this translation helpful? Give feedback.
-
Kaiteki's MD3 support is pretty much the default now |
Beta Was this translation helpful? Give feedback.
-
Components that are Material 3 ready should opt-in to Material Design 3 with
useMaterial3
.https://api.flutter.dev/flutter/material/ThemeData/useMaterial3.html
Material 3 support in Flutter is currently in pretty early stages, but staying ahead of the curve on design can't hurt too much :)
Beta Was this translation helpful? Give feedback.
All reactions