Test the following:
- UI Components
https://www.nomtek.com/blog/flutter-vs-react-native
React Native transforms JavaScript components into native ones.
Flutter renders all components on its own canvas.
Because of that, component updates (to, for example, iOS 16) don’t have any impact on Flutter apps but do on React Native apps.
Depending on where you’re standing, this can be a good or bad thing. For example, if you want your components to stay exactly the way you want them to, Flutter’s approach will satisfy you. But if you want your app to “catch up” with the latest native component designs, then React Native is the way to go — in React Native this update happens automatically and is free. Also, if you don’t want your components in a React Native app to follow the new iOS design (because you want to retain the style, for example), you can turn the automatic component update off.
But to include the latest native components in Flutter, you have to update the app manually.
- Multilingual support
- Database support
- Calling native Android/iOs modules. (https://reactnative.dev/docs/native-modules-android)
- HTTP request/response, json support
- Device alarm, notification, home widget, location change hook, and date/time/time zone changes hook
- Notification support for adding action buttons with listeners, clickable notification listener
- Issues
- Flutter has a steep learning curve.
- Flutter is a high level cross platform framework, it is hard to diagnose problems
Solutions:
- It is better to have some external Flutter programmer develop the app.