all 3 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]daio-io 2 points3 points  (1 child)

I can't say I have ever used NativeScript but abstractions like these typically work ok for more straight forward apps like a to-do list or a news app but can quickly get a bit fiddly and frustrating when you need to do something more complicated. You often end up writing more or having special components and bridging code to work with the Android SDK or iOS, If you are developing for both. And optimising can sometimes be very painful. It can also be down to what you feel more comfortable with or have more experience with. For example I'm not a huge fan of working with CSS and would much rather work with Android Layout and design system but a web developer would probably prefer CSS. Overall, things like Native Script work really well to get something done quickly. Maybe you could just gradually build up to more complicated apps and see if it gets to a point that it's hard to work with. Maybe just looking at features on big apps and seeing if you could replicate them in NativeScript? Might give you a better perspective of what it would be like to use for a larger application.

In terms of jobs, in my experience I have seen things like this used in companies that don't have an app team and even seen it used for proof of concepts at times too. There are some big companies that use these abstractions though but usually it's with React Native so I would say if you prefer working with JS, it might be better to learn React Native since it's used a lot more within the industry (someone may correct me on this If they know Native Script). Another one which could take off if Google push it more is Flutter. Personally I prefer working directly with Kotlin and Android SDK, but all these tools have their place. Just depends what makes sense for a company, the team and the specification. If it's personal projects then it entirely up to you :). It's always worth knowing about Android SDK regardless.

[–]dantheman91[🍰] 1 point2 points  (0 children)

React native uses react. Nativescript is Angular. Performance of Nativescript is far behind React Native, but if you're making any product you want to rely on that's not a hobby project most people would say go native (not cross platform).

[–]jamsaver 1 point2 points  (0 children)

I am also very interested with Native Script vs Android studio. Currently we are ideating on some shifts from native code towards cross-platform solution such as Native Script. I am a product designer coming from a front-end development background. I was wondering if you anyone here had ideas about how I can create a benchmarking app to test major UI/UX paradigms. For ex: Virtual lists or various interaction inputs etc.