Hacker News new | ask | show | jobs
by jimbokun 3737 days ago
"It has a price : performance, sometimes native look&feel not perfectly accurate, supported platform must have similarities."

This is what makes the whole idea a complete non-starter. Users want apps without perceptible latency for their interactions, that look and (more importantly) work like the other apps they are used to. Hard to come up with more important criteria for a successful end user application than these.
1 comments
hartmel 3737 days ago
I really agree. I described the current state. As my next comment explain it more, there is room for improvements. Is the "write once run everywhere" paradigm a realistic goal, would it be achieved at runtime or at code generation/compilation, without an unbearable cost for users ? I want to believe.

W3C made it possible for web.

link
cleversoap 3736 days ago
> Is the "write once run everywhere" paradigm a realistic goal

A part of me sees react-native adding another option here - "write once, tailor anywhere"

While it's always been possible to have common core logic and then tweak your frontend for each platform as a separate project to get a slightly closer to actual native experience, react-native makes it significantly easier to do so and I think it's that one+ standard deviation away ease that makes all the difference.

I don't think we'll see a lot of successful react-native cross platform that goes for the one-size-fits-all approach but rather, with the same (probably even less) effort, we'll see react-native apps that target the UX of a platform rather than just the UI elements.

link
jakevn 3737 days ago
> W3C made it possible for web

W3C provided what might be akin to C compiler standards which are only partly followed by implementors.

The rest is handled by libraries/frameworks/polyfills that get you 80% of the way there.

link