430

Bitwarden will be switching to native apps for both Android and iOS (www.reddit.com)

submitted 8 months ago* (last edited 8 months ago) by mahavir@lemmy.world to c/opensource@lemmy.ml

52 comments fedilink hide all child comments

Libredit link: https://reddit.invak.id/r/Bitwarden/comments/1b32bbz/going_native_the_future_of_the_bitwarden_mobile/

you are viewing a single comment's thread
view the rest of the comments

[-] moritz@l.deltaa.xyz 13 points 8 months ago

I always recognize Flutter apps on Android as being non-native and avoid them because of this.

I think it is because they seem to never use the system font but Quicksand instead and all the animations feel slightly off.

[-] merthyr1831@lemmy.world 5 points 8 months ago

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

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).