Kintone vs. NativeScript

Kintone is great if you want a software that will help you in managing your data, and keep track of which tasks are assigned to whom. It also helps to streamline communication and information in one central place. However, it is not for you if you are looking for something complex that has to manage a lot of data.

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

• Flexibility. You can build apps (without coding) to serve a wide range of processes and projects.
• Ease of use. The interface is intuitive.
• Training. There are resources readily available to train new users. Even starting from scratch, I felt like I was up to speed in just a few hours.

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

• I feel that Kintone is not well enough known yet. This means that other apps/APIs are not necessarily easy to connect with Kintone. Yes, you can use Zapier though for interfacing with other apps.
• It would be great if it could give more customized options to change the look and format of certain things. You can make price quote apps, for example, but have to rely on 3rd party apps or programming skills to customize the look and fields.
• If you make a table as an input field, it cannot connect to other internal Kintone apps for lookups and such.
• I think there is more potential to make more customized data graphs.

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

I still think that there's a room for Kintone's future, and high expectations for them in additional features and innovative tools and supports. Truly hope that they will support email features, and standardized supports for various plug-ins with the 3rd party software and apps. In the meantime, we will have to consider our ways of doing our work in all aspects

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

Kintone is agile app and most of the time we can easily come up with new apps. However, there should be more feature-based drag and drop and or a visual-based usability, as we all want to minimize the number of clicks and dropdown menu selections as much as possible. Thanks.

Incentivized

Never had an issue with this.

Incentivized

No issues.

Incentivized

I have had very specific questions about different aspects of the software, and I have always been able to get a hold of someone who could help. If my sales rep didn’t know the answer, he would get me in touch with someone who did know the answer. The whole team is very ready to help. It definitely feels like they view my success as their success, which is so important with this type of software.

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

Everyone has their own tastes of things and way they want to work. Asking them to adapt to the changes with the new tools or apps is always difficult. We would want to start with a very small but best example within the organization, which in our case was that the employees will not be bothered by the bosses by being asked to find the documents, status of the progresses, or major things/requests/projects.

Incentivized

Kintone is the easiest product to create from and the cost is the lowest I believe. In addition, reconfigurability and extendability are great. If you look for a low code tool, you can try Kintone. But as same as another low code tool, don't expect too much.

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

Should be multiple pricing packages.

Incentivized

I could see this work for all departments if implemented correctly.

Incentivized

Needed improvement at the time.

Incentivized

• It has helped us reduce the amount of people we need to track our inventory. We’ve saved time and money using less people.
• We are able to see our data much better now and have a spot that we can all look at the database on the go.

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