Johnatan56
Honorary Master
Can kind of say that about any design trend though. At least it's standardized. Personally, I hate Apple's flat design as well. Lots of designers just have no clue how to properly place shadows, etc.It doesn't take much Google effort to see that a lot of users don't share your point of view. Material design is awful idea; same design everywhere is never a good approach with UI/UX.
Codepen's site is a good implementation of Material Design, Apple's site is a great one of their Flat design. Tbh I really like Microsoft's Fluent design. I find the best designs for web are between Material and Flat, best mobile probably Fluent and Material.
Again, this is all subjective and depends on how you implement it.
The reason I like Flutter is that it is consistent, you customize one, you customize it the same in the other.
Didn't say it was positive?So how exactly is that a positive thing?
I mean thin client apps.Huh... mobile apps where the code base is non-GUI? Example?
So you're saying native can't have crappy UX?Did you read this article? Certainly plays into my conclusions i.e. crappy UX is non native.
Trade-offs, faster to market versus a better app native. At no point did I say not to ever go native, what I said was make your decisions based on requirements, if it's faster/more budget efficient to go cross-platform for a small app, do it, if it's something larger like Solarion's bank app, then go native.So in your... ... quote, the conclusion is that we should go with non-native if:
... sounds like the recipe for a crappy UI / UX -- which is quite typical for a garbage app -- clearly I'm missing the point you're making?
Last edited: