NativeScript vs. Tanzu Application Catalog

I gotta be honest, after a PoC period, we choose to rewrite the whole application in a different cross-platform app. Our developers had to invest a lot of time and effort to debug a lot of plugin-related issues, which we needed to utilize the android mobile phone capabilities. QR reader, special visualizations, and fine-tuning were really hard and often resulted in writing native Android code instead of using the shared Angular code. In the end, we think that writing a standalone Android app and an Angular app would have been a better alternative, as the shared code base was so unreliable that it did not save us any time.

Incentivized

The best way to take advantage of VMware Application Catalog (Bitnami) is as in the case I mentioned, that you constantly implement these free software, where any time saved is important in terms of installation, configuration and testing environment, it really is a very useful solution, also if you need a good community and support; however the cloud and VMs solutions is not designed for huge products, these can be slow or remain insufficient if the use of these grows a lot, even though it is an easy-to-use product, you need to have enough knowledge in terms of installation and management of cloud solutions, a beginner can find himself in trouble

Incentivized

• 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.

Incentivized

• pre-packaged templates they provide.
• ease of cloud-deployment of your projects.
• The development community page always has useful information and there is a lot of support.

Incentivized

• The need to know the native Android and iOS APIs to access device hardware and other platform-specific functionality
• Not all user interface components are available for free
• NativeScript has no HTML and DOM, which requires some deep knowledge of different UI tools to be implemented instead

Incentivized

• Possibility to configure the implementation through mobile devices
• Sometimes the performance of the VMs is slower than expected
• A best way to do the upgrades, you have reinstall and reconfigure in this process

Incentivized

The hybrid is ok but native is better for performance and the right use case I want to go for is the performance without dealing with too many development tools.

Incentivized

Most of it is intuitive. I think some of the awkwardness is found by new users who are unfamiliar with other software applications.

Incentivized

The community support is excellent.
They have a slack community as well as a discourse forum
forum.nativescript.org
Both of these offer community driven support.
The forum is more for a threaded discussion. The slack community is more for a quick talk.

Incentivized

They have an expert team, not just a frontline team that has learned the FAQs but a team that knows the product.

Incentivized

Ionic Ionic is an excellent Angular-based framework for mobile, and it does give a lot of access to the native device api's. However, the technology is based on Cordova, which means the apps being built are just webviews, with html, css and JS all running on the UI thread, and potentially creating very slow experiences for users. NativeScript is a truly native solution, and so provides a faster user experience. ReactNative We evaluate ReactNative, and found it much the same as NativeScript. The main difference is that your JS is all written with React, while NativeScript lets you choose between normal JS, Angular, and Vue. For our team, Angular was the most appropriate choice.

Incentivized

VMware Application Catalog (Bitnami) offers better tools to complete the task faster and more efficiently. The customer support and knowledge base is also well presented and trained

Incentivized

• The poor quality of NativeScript documentation has the potential to weigh heavily on development timelines, budgets, and QA resources in a NEGATIVE manner.
• The poor interoperability of NativeScript plugins can significantly increase development time.
• The need to seek out professional instruction to learn how to use NativeScript effectively may become a burden on your budget.
• The number of breaking changes between versions of NativeScript, may cause your development efforts to lag further behind the most recent releases of NativeScript and your other chosen environments than you are accustomed to.
• NativeScript still does not support the latest major version of Angular. Any significant changes to the other environment components of your systems may hold you back even further while NativeScript plays catch-up.

• We save a lot of time implementing the apps, less engineers working on this phase
• The upgrade process of the apps can be a pain and a waste valuable time
• The mains options of the VMware Application Catalog (Bitnami) are free so is important for save money in our organization

Incentivized