AppSheet vs. NativeScript

If you need to manage special assets with unique characteristics and keep data in spreadsheets, Appsheet is ideal for replacing these sheets with a system. Once you start using it, you find yourself trying to move everything into Appsheet. It is perfect for generating internal software that would otherwise never be developed due to programming costs.

Incentivized

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

• Calculations - I have several apps that do some pretty complicated calculations, and decision making to build things like Shopping Lists for a Kanban assembly team, where the app will help a stocker determine whats low in a kanban assembly line stock box.
• Document generation and record keeping - I have an app that users digitally sign and receive PDF contracts, and the system automatically records all records from the transaction. Everything is held in files on YOUR OWN DRIVE (Google Drive) so when you're done with the project or AppSheet you DONT loose your data.
• Client/Customer Management - I follow the old school "Swimming with Sharks" model for client retention and customer engagement, and have built several small customer tracking tools for local businesses. This tool is limited ONLY by your imagine and desire to learn.

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

• Once the tables / UX Views get way too many in number, it can become a little daunting to manage. This part of the UX may need something really smarter.
• Ability to Undo.
• Could provide more UI Look and Feel options. BTW, the new Graphs look great, but have some bugs, while the new INPUT() feature is a great addition too.

• 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

We are still less than 10 users and probably may continue to be so. But, this being a franchisor set up, could be of use to other users like us.

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

It's just great. The usability is the best thing about Appsheet. You must choose which things will really be used later. You have to be careful of not generating something too big and then it feels like something that need to be learned. This is something that resolve problems, but you had to be able to think before doing. It will not solve problems itself. You need to find the problem, think a solution, and then use appsheet to make this solution a reality

Incentivized

AppSsheet has a support group and they show videos to help app builders. Though I have truck drivers' hours and can't join the webinars. Support groups with better assists me on a Saturday evening or a Sunday that I have time off. It's hard to watch videos driving down the highway.

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

I did everything on my own

Incentivized

The ease that AppSheet provides to the developer is limitless. Before starting with AppSheet I used other software, but they didn't give me the tools at my fingertips.
When I learned about AppSheet and everything it could do, I understood that it was what I was looking for, the ease with which everything is related within the app with a few clicks is impressive.

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

• A good impact in general at the beginning since the free version allows great development so the investment in the implementation is of knowledge and time.
• As a consultant I have expanded my services through this platform including new low code application building services.

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