4 ms·
Unless you are writing a Tier 1 application that needs every fancy do-hicky, I don't see the point of 100% native anymore. Use React Native, then if necessary h
by seibelj 10y ago
Unless you are writing a Tier 1 application that needs every fancy do-hicky, I don't see the point of 100% native anymore. Use React Native, then if necessary have a devoted native developer for each platform to handle parts that absolutely have to be executed in native and provide a JavaScript API. If you are a big company with tons of money, sure, create duplicate teams to make the same app for each platform. But if you are small or just starting, React Native is the best choice.
- copperx 10y agoI'm all for write-once-deploy-everywhere, but React Native is better suited for apps that could be easily written web-only. Maybe I don't get what's better about React Native over a native app that is just a web view.
- naiyt 10y ago> Maybe I don't get what's better about React Native over a native app that is just a web view. It's better because React Native is actually rendering native components. Stuff like PhoneGap never feels or works quite right as a side effect of being rendered in a web view.
- wingerlang 10y agoI think his point is - why make a native app that just re-renders the data which you can just as well look at in a browser.
- suprfnk 10y agoNext to the fact that something like push notifications require a native implementation, people like apps more. I'm currently working on a way to make our mobile-tailored website into an app, just because customers keep requesting a _real_ app instead of a webpage.
- clay_to_n 10y agoReact Native apps are written in JavaScript, but the components you use are wrappers for actual native view components. So you get native performance (the views can be GPU-accelerated), and native styles. I've been working with Android for a couple years, and (while I like it) it has it's warts. The architectural patterns required to keep a medium-sized codebase understandable are simply not agreed upon. There are lots of ways to do things, and (as the article points out) even the basic activity + fragment API's are very complex. I just started playing with React Native, after having some React experience, and it's a breath of fresh air. It feels like cross-platform without obvious negatives, and the rare bonus of being able to wrap + use native components or libraries whenever you need to. You can even share most of your code (even view code for basic views) across IOS and Android. React has a super simple API. The tooling is younger, but is out of the box faster to develop with than Android. That said, I haven't built a large app in React or React Native, and maybe it bites developers at some scale. No idea how it deals with long-running services, multiple threads, bluetooth or other hardware APIs. But for now, I'm very optimistic.
- collyw 10y agoI have an Ubuntu phone, where the majority of stuff is web based. One problem I noticed is that many apps won't load unless you are connected to the internet. Is it possible to cache the stuff that would get loaded for using apps offline?
- vetinari 10y agoYes, but the app developers have to do it when developing the app. It involves app manifest and service workers. At this years Google I/O, there were talks how to do that (in the Chrome track).
- wccrawford 10y agoReact Native isn't web-based. It's a way to create native widgets but the library works like the React library for Javascript. So there's no worries about being online or offline, just from using React Native.
- rimantas 10y agoNative is the best joice. Why do people want to stuff some lame language in between I fail to understand.
- pier25 10y agoOr NativeScript