4 ms·
I think they mean it runs as native code. What libraries that native code uses is a different issue - but it's still native code.
by chrisseaton 5y ago
I think they mean it runs as native code.
What libraries that native code uses is a different issue - but it's still native code.
- user-the-name 5y agoThe exact technical details of how an app executes code is a lot less interesting to an end user than whether or not it uses the native UI. The former has almost no noticeable impact on user experience, while the latter can cause tons of annoyance.
- chrisseaton 5y agoI think the number of people who care about a native UI has dropped to effectively zero over the last decade. The ship's sailed.
- BoorishBears 5y agoPeople don't actively care, but I've watched conversion rates on certain paths in an app skyrocket when the UI changed to respect platform norms. People build up an intuition about how apps on their devices work, going non-native is an easy way to subtly break their expectations.
- karottenreibe 5y agoI wouldn't call HN an "end user forum". So I think this content fits very well with the crowd here.
- Zababa 5y agoI don't think that's true. Outside of a very vocal minority of mac users on HN, most people don't really care about native UI.
- nicoburns 5y agoGenerally when they talk about native people want a small app with good performance and low resource usage.