Most people talk about PhoneGap/Cordova when they talk about hybrid, but NativeScript and React-Native are also partially based on Web technologies (CSS/JS) and aren't 100% native.
I also read that NS & RN get better performance (60fps yaddayadda) than PG/C, so if you don't persist on using HTML as render target, the difference between "real" native and "hybrid" native isn't that big anymore.
That's very true. And this is a big problem with technology which evolves quickly but we can't (and probably shouldn't) rename each different iteration. So hybrid means something totally different in different times and places.
The Facebook story is from, like, 2010 and newer approaches to both the native-interacting/compiling and the Cordova approaches have evolved a lot.
Then there's the situation where you were able to convince the clients that hybrid isn't what they think it is but now they think nothing will ever go wrong and if something does go wrong or is non-performant, there's the "If only we'd gone full native" cloud hanging over your head. Either way, the client will have a hard time envisioning all the problems that were avoided by making the choice that was made.
That's just a mini-rant about clients. :P
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Most people talk about PhoneGap/Cordova when they talk about hybrid, but NativeScript and React-Native are also partially based on Web technologies (CSS/JS) and aren't 100% native.
I also read that NS & RN get better performance (60fps yaddayadda) than PG/C, so if you don't persist on using HTML as render target, the difference between "real" native and "hybrid" native isn't that big anymore.
That's very true. And this is a big problem with technology which evolves quickly but we can't (and probably shouldn't) rename each different iteration. So hybrid means something totally different in different times and places.
The Facebook story is from, like, 2010 and newer approaches to both the native-interacting/compiling and the Cordova approaches have evolved a lot.
Yes.
At the moment I make react-native apps for a living and clients still only know about "hybrid" (PhoneGap) and "native"(Objective-C/Java).
Then I tell them about the "app spectrum" and they're mind blown, haha.
Then there's the situation where you were able to convince the clients that hybrid isn't what they think it is but now they think nothing will ever go wrong and if something does go wrong or is non-performant, there's the "If only we'd gone full native" cloud hanging over your head. Either way, the client will have a hard time envisioning all the problems that were avoided by making the choice that was made.
That's just a mini-rant about clients. :P