3 ms·

I have making web and mobile apps for a long time and have never understood what "native" UI even means. No two native apps look the same. And the thing I alway

by tootie 4y ago

I have making web and mobile apps for a long time and have never understood what "native" UI even means. No two native apps look the same. And the thing I always notice is that I can't deep link or do a text search on a native app. You are absolutely correct that most users prefer native apps but I have no actual data on why.

jcelerier 4y ago
as a user, because even of beast of a machine native apps are faster, snappier, don't have a ton of shitty useless animations and gigantic spacings & margins between everything. I swear whenever something animates in a UI it almost makes me reflex-xkill it. good: https://cancel.fm/ripcord/static/ripcord_screenshot_win_6.png https://cancel.fm/ripcord/static/ripcord_screenshot_win_6.pn... (densely packed information, respects the fonts of my OS, menus with dialogs, opens in 0.01 second, etc. bad: slack/discord. they make me want to stop using computers altogether whenever I have to interact through one of those as a developer, for now my experiments porting code requiring full-throttle maximal performance from the user's hardware in https://ossia.io https://ossia.io to wasm for https://ossia.io/score-web https://ossia.io/score-web really still puts wasm in the "toy" section, it's like going back to 15 years old hardware. Sure, there's likely wasm-specific optimizations that would help, but i don't need to do any of those for maintaining mac / win / linux versions so this is a bit frustrating. Also wasm is not likely to be able to load the tens of thousands of native VST, etc... native-code-based plug-ins developed over the last decades.
babypuncher 4y ago
If you want a good example of what I'm talking about, go look at the official Reddit app and compare it to Apollo for iOS. The former feels like a wrapper for the mobile site with a few native flourishes on top. It ignores lots of iOS design conventions, because they want the experience to be the same on iOS and Android. Apollo on the other hand feels like a true native iOS app, it follows all of Apples design paradigms, and feels right at home next to the apps that come preinstalled on your iPhone.
locutous 4y ago
The numbers aren't as good as the native proponents claim. A lot of sites put on a full court press to use native going so far as to intentionally cripple web in mobile. This is the environment that produces the numbers cited from time to time. The feel good answers by devs about native experience or OS integration don't have any real data backing them that I can find.

by tootie 4y ago

jcelerier 4y ago

as a user, because even of beast of a machine native apps are faster, snappier, don't have a ton of shitty useless animations and gigantic spacings & margins between everything. I swear whenever something animates in a UI it almost makes me reflex-xkill it. good: https://cancel.fm/ripcord/static/ripcord_screenshot_win_6.png https://cancel.fm/ripcord/static/ripcord_screenshot_win_6.pn... (densely packed information, respects the fonts of my OS, menus with dialogs, opens in 0.01 second, etc. bad: slack/discord. they make me want to stop using computers altogether whenever I have to interact through one of those as a developer, for now my experiments porting code requiring full-throttle maximal performance from the user's hardware in https://ossia.io https://ossia.io to wasm for https://ossia.io/score-web https://ossia.io/score-web really still puts wasm in the "toy" section, it's like going back to 15 years old hardware. Sure, there's likely wasm-specific optimizations that would help, but i don't need to do any of those for maintaining mac / win / linux versions so this is a bit frustrating. Also wasm is not likely to be able to load the tens of thousands of native VST, etc... native-code-based plug-ins developed over the last decades.

babypuncher 4y ago

If you want a good example of what I'm talking about, go look at the official Reddit app and compare it to Apollo for iOS. The former feels like a wrapper for the mobile site with a few native flourishes on top. It ignores lots of iOS design conventions, because they want the experience to be the same on iOS and Android. Apollo on the other hand feels like a true native iOS app, it follows all of Apples design paradigms, and feels right at home next to the apps that come preinstalled on your iPhone.

locutous 4y ago

The numbers aren't as good as the native proponents claim. A lot of sites put on a full court press to use native going so far as to intentionally cripple web in mobile. This is the environment that produces the numbers cited from time to time. The feel good answers by devs about native experience or OS integration don't have any real data backing them that I can find.