TrustRadius
https://dudodiprj2sv7.cloudfront.net/product-logos/E6/yx/T5MOCRDQS9B6.JPEGProgress Software CorporationClimb to NativeScript, enjoy the Vue...2018-07-24T19:42:34.025ZWe are testing NativeScript to see if it will be a good fit for the next version of our app. We have an e-learning education platform focused on mobile. Our current version is built on ionic v1, and we are looking for a better alternative. Our app needs to be offline first, but the courses and content are downloaded from the internet. The app has lots of gamification features. It needs to be much slicker than it is now in the current stack.,True native app. The app uses native components and that is quite noticeable in the overall performance of the app. NativeScript is also awesome in the way we can access the native APIs, so we are never really constrained by the framework. If we need, we can just dive into the native APIs without leaving our environment and language (JS).
Cross-platform. Builds for Android and iOS. It deals with the platforms differences very well.
Support for Vue.js. Even though it is just a community effort, the NativeScript-Vue plugin is the best alternative to build native Apps with Vue.js. That was a major factor to go with NativeScript.,Web build. It is still hard to share code with a web build. In our case, we want to build a web app with pretty much the same functionality. Other frameworks are stronger at this point.
No hot-reload. It still takes a couple of seconds to test an app. React Native does it better... With NS-Vue, the live-reload is even more fragile...
Tooling. Overall, NS could use better tooling. Again, RN does it better.
Better NS-Vue support. It is improving very well, considering it is a community effort. I see NS organization 100% supporting NS-Vue, but it is still not at the same level as NS-Ng, for instance.,9,(I haven't built an app in production yet.),,Visual Studio IDE, Bitbucket, Google DriveTiago AlvesMobile apps delivered by leveraging our existing skillset with NativeScript2018-04-30T14:14:29.657ZWe are using NativeScript on a single mobile project at the moment. It is the framework which supports development of this entire project for our client. In particular, we are using NativeScript with Angular 5, to leverage the current skills of our front-end development team. We also have an internal app to track our knowledge sharing events that we are developing with NativeScript.,NativeScript allows our front-end developers to build actually native mobile apps with the javascript we already know well.
It is very quick to get started using NativeScript. We can generally onboard a new developer into the project in just a day or two.
The open source community surrounding NativeScript allows our team to find solutions to open issues quickly, as well as give back by fixing some issues ourselves. Work can progress quicker with the plugins other developers have already built.,The frequency of updates can make it hard to stay fixed to a common version. I found that there were so many improvements happening that it was worth bumping versions and adjusting the code at least every 3 months. This added extra development time, which also added stress. The benefit is worth it, but it's important to keep in mind that sometimes even a bugfix version bump will require some code changes.
We also found the fractured dependencies hard to keep up with at times. The nativesript-cli, tns-android, tns-ios and nativescript-angular dependencies all have their own release cycles that are close together, but not tied together, and that has downsides when prioritising upgrades during a release cycle. Again, the benefit to upgrading is worth it, but staggered releases do add additional complications.
Documentation is good, but could be better. Over the past year, this has been greatly improved, but there is still a delay between the adding or refactoring of features and the updates to the documentation.
The plugin ecosystem is open source, which is good, but as with your own project, the authors of these plugins also have to keep up to date with the changes in the repos, and that isn't always done in a timely fashion.,10,We had built this particular app once already, during a 6 month time frame, using Ionic. When we hit the wall, we chose NativeScript, and built the whole app from scratch. We estimated another 6 months, but completed the work in 4 months due to the ease of use.
We have found collaboration with our client much easier because of the simplicity of releases and speed of development.
Having a tool like NativeScript has allowed us to make competitive quotes for mobile app development contracts, where previously that would have been closed to us due to our lack of native development experience. Being able to build iOS apps without a Swift-code expert has opened those doors for us.,,Adobe Experience ManagerEvan PayneNativeScript - Mobile App Development on Steroids2018-04-10T15:51:16.017ZI work at a fitness based startup. Our app, "AnyGo" is built entirely using NativeScript. I was the one who proposed to the team, to use NativeScript. And today when I look back, I'm glad that I found NativeScript. We were able to launch our app in 6 months, all thanks to NativeScript. I worked on the app, while 3 other developers built the backend on NodeJS.,NativeScript has a large repository of plugins at market.nativescript.org for the times when you want to boost your development speed.
NativeScript gives you 100% day zero Native API access.
NativeScript doesn't use any webview to render the UI. So you get Native UI, and therefore better performance, when compared to things like ionic or phone gap.
With NativeScript you get 4 architectural choices, JavaScript, TypeScript, Angular and Vue. Choose the one you are comfortable with.,Nativescript runs everything on a single thread. i.e., the UI thread. If you want to offload some processing, you have to use web workers. This experience can be improved in the future releases.
Currently NativeScript only have hot reload when you change the UI file or Css file. There is no hot reload when you change Js/Ts file, unlike Google's Flutter. This is also something which NativeScript will get in the future releases.
In current version of NativeScript, there is no livesync when building with webpack. This feature will be added with NativeScript 4.x. (an RC version for 4.x is already available),10,With NativeScript we were able to goto market sooner than what we expected. We were in market in just 6 months.
Customers are happy with our products, in just a month, we reached 200 active users for AnyGo user app, and 17 active partners for AnyGo Partner app.
We were able to build all the features that the business requires, using NativeScript. We even built some new plugins for this app. Example nativescript-paytm for payment gateway integration.,React Native and Xamarin,WordPress,No,10,Yes,I had reported a bug in the side drawer once, which caused a jaggered feel when slowly opening the drawer on android.
The nativescript ui team let me in on their private repo, and i was able to fix it and submit a PR.Shiva Prasad KNativeScript: Good for mobile performance.2018-02-16T18:38:43.215ZNativeScript is the main tool to develop mobile apps for internal and external projects. The main feature is the capacity to develop one source code to address ios and android using the actual experience the dev team has with javascript and angular. Because of their active community, we can reuse our experience and others' in order to speed up every project. Using the extensive library of components already available and the one we have built with the time, we reuse a lot of code saving time.,The fastest transition from prototype to final product
Javascript with angular allow us to use the actual experience. No need for native development
Native performance, you can exploit the hardware better than hybrid tools,If you come from the nodejs world, you will have to sacrifice some ways to deal with data. For example, we had to sacrifice PouchDB for offline data
The final size for Android could be huge compared with hybrid tools or the sameNativeScriptt for iOS
Some native development is required in order to exploit all the components
Sometimes web development experience is not enough. Even with Angular you need to learn some new concepts. Once dominated, you can rock native mobile apps,8,Positive: shorter delivery time because you don't have to go for the usual native workflow and you have a common base code for all mobile platforms
Positive: you can start faster to dominate your hardware. From the very beginning, you will be sure about the performance you will get
Negative: you can't have your prototype on a browser, you will require an emulator or a real device
Negative: training was required at the beginning because web experience is not enough. Not that you need to become an expert but some native knowledge is required. Also, you need to work on a standard way to deal with database and backend communication,Ionic and Apache Cordova,CouchDB, Couchbase Data Platform, SQL Server Integration Services, Redis,10,3,Control an integrated barcode scanner, or any other integrated component, on a mobile device for fast identification and control
Processing complicated business rules keeping a fast user experience in the mobile app
Faster UI, you have to go for NativeScript,we moved from pouchdb in hybrid mobile apps to couchbase with nativescript for offline database,We need to do some more work with geolocation
Battery efficiency is also another field for us to research,8victor pease solanoNativeScript makes cross-platform mobile app development easy, fast, and efficient.2018-04-10T15:59:30.766ZWe are a consulting company and use NativeScript for apps internally and externally for customers. We chose to use NativeScript as a mobile app development platform because of its native performance, native UI generation, and ease of cross-platform mobile development. Furthermore, we can leverage existing skills on our development teams (Angular, TypeScript, and CSS) to create native mobile apps. This was the first platform we tried that was easy to get started with, and provided the least amount of friction for developing mobile apps.,NativeScript allows you to build on skills many development teams already have: HTML, JavaScript, and CSS. Many developers understand the paradigm of web development where you have HTML, JavaScript, and CSS to define an application's behavior. NativeScript apps are similar. By using a similar paradigm of development, it enables web developers to quickly jump into their first app, write it quickly, and see the results on iOS and Android.
The NativeScript Playground sets NativeScript apart from other technologies. The NativeScript Playground is a browser-based environment for developing simple NativeScript apps. It’s a great place to get started learning NativeScript, as you can develop apps without needing to install the various SDKs and tools needed for native iOS and Android development. All you need is your browser, and an Android or iOS mobile device connected to the internet to get started. We use the NativeScript Playground to quickly prototype apps. It's an extremely powerful tool.
NativeScript provides abstracted UI and component APIs to access native iOS and Android hardware and UI components. This accelerates development because you can write a singular UI and business logic code for both iOS and Android, thus saving time. At the same time, you have the ability to access native SDK/APIs of the underlying platforms through JavaScript.
NativeScript has three flavors of development: NativeScript Core, Angular, and VueJS. NativeScript Core uses XML, JavaScript, and CSS to build native apps. But, if your developers already know Angular or VueJS, then you can build NativeScript apps using Angular/VueJS development paradigms.
There are dozens of online resources for getting started, troubleshooting, and staying up-to-date with NativeScript: forums, slack channel, twitter, online docs, NativeScript snacks, NativeScripting, blogs, etc. The community has been very strong, and continues to be a shining star NativeScript.,If users jump directly into NativeScript Angular and are not familiar with NativeScript or Angular yet, it can be difficult to understand where NativeScript ends and Angular begins. This can be confusing.,10,The ROI on using NativeScript for app development for us has been approximately a 75% decrease in the price of mobile app development for our customers. When creating native apps on both Android and iOS platforms, we used to need a significantly greater amount of time. Now, we can bring cross-platform mobile apps to our customers at a reduced cost.,Xamarin,XamarinMike Branstein
Windows, Linux, Mac
NativeScript
15 Ratings
