4 ms·
Two of the examples mention are platform providers. If they standardize on flutter as their native UI, that’s fine and they are following my suggestion. If they
by scosman 2y ago
Two of the examples mention are platform providers. If they standardize on flutter as their native UI, that’s fine and they are following my suggestion. If they port a BMW app from my dashboard to iOS / Android, I’m 99% sure you’ll see the issues I mentioned.
Google earth is fine, but doesn’t feel native. I think that’s fine for some apps (games mostly).
- mdhb 2y agoCould you maybe provide a single clear example of how Google earth doesn’t feel native?
- scosman 2y agoWelcome screen was a popover on iPhone (only available on iPads, should be a sheet on iPhone), with rounded non standard button and non standard horizontal lines. “Signed in as” toast wasn’t designed for iOS rounded bottom and “swipe up” bar leaving ugly stripe. Sheet easing is off, and FPS stutter. No swipe from left to go back support. Non standard animations all over. Visible FPS issues (on newest HW) I could go on and on. Feels like an android app running in an emulator.
- mdhb 2y agoI think several of your examples appear to be confusing Google’s material design system with the frameworks capabilities.
- scosman 2y agoYou asked how it doesn’t feel native. Using a design system from a different platform, and not complying with the interface guidelines of the current platform, is a big part of not feeling native. And the frame drops and lack of system gestures, and lack of standard nav stack are major infractions on usability outside of design.