AWS IoT Core vs. Flutter by Google

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

Flutter is well known for native app development, if you have android studio installed on your system, you can quickly start using it. This might not be the best choice for you if you do not wish to learn a new language, i.e. Dart and you do not know it already.

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

• It is powered by Google, so a great technical community is backing it.
• The development of native apps is an easy process using Flutter.
• As it is an open-source tool, we can use it without paying anything.
• It provides nice UI options.

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

• Occasionally updates to the Flutter SDK result in wide-sweeping changes that seem to not be thoroughly tested and considered. Flutter sometimes evolves too fast for its own good.
• While the 3rd-party Flutter package ecosystem is vast and rich, 1st-party support for basic things (audio/video playback, battery information, Bluetooth services, etc.) are lacking. You are occasionally forced to rely on an open-source package for use-cases that other platforms have native support for.
• Documentation, particularly around testing, is lacking. While there are some great docs, like the Dart Style Guide, many Flutter-focused support documents are lacking in quality and real-world usability.
• Flutter allows you to architect an app however you want. While this is a great feature, it also adds complexity and leads to the current state of Flutter's state management, where there are 50+ options on how to organize your app, with very little official guidance or recommendations from the Flutter team. For a beginner, this can create decision paralysis.

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

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

I have experience with react and React Native. I would say that the idea behind all those frameworks are quite similar. However, I found the javascript-based frameworks a bit more accessible as you could utilise your javascript knowledge. Here, Flutter works with its own language. This has advantages and disadvantages sometimes. I found the community around javascript frameworks bigger and therefore sometimes more helpful. However, Flutter does a good job here as well. I think the main argument for Flutter is its usability for less experienced developers. If you do not have knowledge in javascript or other programming languages then I think it is much easier to start with Flutter than with another framework like react. I think the package that you get form scratch is better than in the other frameworks were you have to set up and learn a lot more before you can start.

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

• The rapid development capabilities of Flutter allow us to build apps we could not have previously considered commercially viable, opening new revenue streams.
• Free and open licensing made adoption very easy (ie. free/low cost!).
• In comparison to Qt, our time spent arguing with build tools and perfecting development environments has decreased substantially.

Incentivized