7 ms·

My company tried using this a few years ago to build a cross platform app (and hopefully share a lot of code with our svelte web interface). We made a lot of pr

My company tried using this a few years ago to build a cross platform app (and hopefully share a lot of code with our svelte web interface). We made a lot of progress in 3-4 months of trying, but we ended up running into too many odd bugs and edge cases that were difficult to debug. We eventually switched to Flutter for the mobile codebase. No doubt this and nativescript have improved since then, but from my early impressions, I wouldn't have recommended nativescript for anything other than the simplest of interface needs.

scosman 3y ago
This is the story I’ve heard about almost every react native project. Get to proof of concept 10x faster. Spend 10x more time in the weeds on weird bugs.
- rhodysurf 3y ago
  NativeScript is not react-native
- mixmastamyk 3y ago
  Also the old Cordova equivalent and Kivy. Take mobile development and try to shoehorn a browser-based solution (they don't want) into it. Now you've got two problems and not enough expertise available to help.
- whizzter 3y ago
  Did they have JS _AND_ React experience beforehand? Or did they just pick RN because it was the cool thing on the block? I foundered on my first attempt at an React app (side project) coming from a C,C++,Java and non-React JS background, but the second one(professionally) after I've had exposure to some React got released and an fork of it is still in use today. And the company I work with has 2-5 other apps out for customers using RN/Expo (thanks to the positive experience I had). We're also strict about using TypeScript though so we're not chasing basic type bugs (since debugging is a tad weaker with RN/Expo even if it's usable if shit the fan only occasionally) and we have plenty of React experience outside of it, biggest "quirks" are often RN/Expo upgrades if we haven't maintained things in a while (the oldest app used a relatively early version of Expo though) or platform specific notification crap (that I've heard is painful regardless of Expo/RN).
TSiege 3y ago
How has Flutter compared in your experience?
ca-tech-run 3y ago
[flagged]

scosman 3y ago

This is the story I’ve heard about almost every react native project. Get to proof of concept 10x faster. Spend 10x more time in the weeds on weird bugs.

rhodysurf 3y ago
NativeScript is not react-native
mixmastamyk 3y ago
Also the old Cordova equivalent and Kivy. Take mobile development and try to shoehorn a browser-based solution (they don't want) into it. Now you've got two problems and not enough expertise available to help.
whizzter 3y ago
Did they have JS _AND_ React experience beforehand? Or did they just pick RN because it was the cool thing on the block? I foundered on my first attempt at an React app (side project) coming from a C,C++,Java and non-React JS background, but the second one(professionally) after I've had exposure to some React got released and an fork of it is still in use today. And the company I work with has 2-5 other apps out for customers using RN/Expo (thanks to the positive experience I had). We're also strict about using TypeScript though so we're not chasing basic type bugs (since debugging is a tad weaker with RN/Expo even if it's usable if shit the fan only occasionally) and we have plenty of React experience outside of it, biggest "quirks" are often RN/Expo upgrades if we haven't maintained things in a while (the oldest app used a relatively early version of Expo though) or platform specific notification crap (that I've heard is painful regardless of Expo/RN).

TSiege 3y ago

How has Flutter compared in your experience?

ca-tech-run 3y ago

[flagged]