Personally, beyond a few material-like components I always prefer it when an app goes for its own system-agnostic design language like Spotify does. On desktop I'm definitely more picky if I can get away with it; Qt dor KDE and GTK for GNOME etc

[–] Blisterexe@lemmy.zip 1 points 8 months ago

i love having all my apps match my system, gtk or qt for desktop mui for android

[–] deadcream@sopuli.xyz 1 points 8 months ago

I have given up on the fight a long time ago. On the desktop the only line I draw is that the app must respect system font configuration and use system-provided file dialogs.

[–] deadcream@sopuli.xyz 2 points 8 months ago (1 children)

Same with Compose even though it's ironically considered native in the Android dev community.

The easiest way to tell that the app is not native is tooltips (those that appear when you long press on a button in a toolbar). For some reason UI frameworks just can't agree to display them in the same way, even if they use material design. Compose's ones are especially bad (some apps like Play store actually have different kinds of tooltips on different screens, meaning they use multiple UI frameworks in the same app).

[–] moritz@l.deltaa.xyz 1 points 8 months ago (1 children)

With Compose apps I actually never had this problems yet.

[–] deadcream@sopuli.xyz 1 points 8 months ago

It looks mostly the same as XML views but some components look and behave wildly different for no apparent reason (tooltips are one of those).