AWS IoT Core vs. NativeScript

AWS iot core is very useful if you need to scale very quickly for managing lots of devices without handling the underlying infrastructure cost. It can enable real time publishing and subscription of devices, monitoring and early stage intervention in case of unexpected issues while developing a full stack solution. However, healthcare scenarios where government intervention is needed should be developed and scaled by following the set of compliance policies of the government and the SLA requirements of the customer. Finally, it is great where you need to do data science research after anonymizing data

Incentivized

NativeScript allows to easily integrate with native APIs by threading models. Moreover, the framework itself can be integrated with Angular, VueJS and JavaScript due to the fact that it was built on based on these frameworks. It allows you to easily maintain if you projects are based on these frameworks. Therefore, for the development of cross-platform applications it can be very handy!

Incentivized

• AWS IoT Core integrates power analytics and an AI solution for sensor data processing.
• Great protocol support including HTTPs and MQTT required to connect resource constraint IoT devices to cloud
• High security standards during data transmission
• Scalability and a great user community

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

• It would be great to have better integration with other IoT products outside of AWS
• It has been lagging in some of our applications. It's difficult to tell whether this is on AWS IoT or on our implementation
• It would be great to support a wider range of protocols

Incentivized

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

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

I give AWS IoT Core's overall usability this rating because it is very easy to use and is enjoyed by all of our staff. The only problem is that it sometimes glitches and it freezes a lot. So overall, the usability of AWS IoT Core is very good, and we will continue to use it.

Incentivized

It covers all the aspects of IoT services required for an IoT company. It supports all the industry-wide protocols for secure data transmission and integrates powerful AL and ML technology for data analytics. For data storage, Amazon S3 is a great solution. Strong tech support and user community. Since it is widely used as compared to other products, there is an abundance of training and learning material on the web.

Incentivized

My focus has been, and must remain, with obtaining support from web resources over that of paid support programs. Many companies, including those of government agencies, do not have a budget sufficient for paying large sums of money to other organizations to answer questions. Even in cases where an organization did purchase support programs, developers often found that the delays in obtaining responses to development issues was excessive. I give NativeScript the lowest possible rating, due to the fact that their website content is severely outdated and of little use to a developer in a crunch. The NativeScript environment may be far better than I have been able to report, but held back from excelling due to poor support content. Being that I am often asked to push the boundaries in various areas, improper documentation is highly detrimental to a development team, and thuss a review. I would be more than happy to improve this review as the content of the support documentation provided by the NativeScript team makes its way to their website in the form of real-world examples which are applicable to all versions, or at least the most recent versions, of their product.

Azure IoT is a good product but since our whole suite of tech is now set up in AWS (ec2, s3, sagemaker, cloud formation, etc.), we wanted something that could quickly adapt to our environments. Learning a new tech for IoT was simply a bottleneck that we wanted to avoid at this point.

Incentivized

NativeScript was indeed a better experience at first than Ionic. But the real game-changer in 2022 for cross-platform applications is Flutter now. We changed to it shorty after NativeScript, as it is much more stable, more widely supported, has a ton of extra features, and does not rely on JavaScript and Android knowledge as much as NativeScript.

Incentivized

• Gives confidence to prototype iot solutions across lots of devices in little time
• Ability to meet requirements for managing a variety of communication protocols
• Learning iot analytics and visualization for faster insights enablement
• Onboarding devices and managing quickly without building inhouse solutions

Incentivized

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

Incentivized