Flutter Limitations

WebViews - Flutter does not have a built-in WebView widget. So displaying web content within a Flutter app is not straightforward. There are plugins available but the support is not as robust as native.

Maps - Again, Flutter does not have a built-in maps widget. You have to use third party maps APIs like Google Maps or Mapbox by using their Flutter plugins. The map support is not as good as native maps.

Lack of Libraries - The Flutter ecosystem still lacks some of the libraries and packages that are available in native Android and iOS. So, sometimes you might have to build things from scratch.

Platform Specific Features - Since Flutter renders everything using Skia, it is difficult to access some platform specific features. Flutter team is continuously improving platform integration, but still lacks in some areas.

Larger App Sizes - Flutter apps tend to be a bit larger in size when compared to native apps. This is because the entire Flutter framework has to be bundled into the app.

Deeplinking - Handling deeplinks in Flutter apps is not straightforward and requires setting up routes and handlers. In native apps, deeplinking comes built-in.

Lack of Kotlin/Swift Interop - If there is an existing codebase in Kotlin/Swift, combining it with Flutter is difficult. The interop between Flutter and the native languages is still not perfect.

CI/CD Challenges - The build setup for Flutter projects tends to be slightly complex as you have to build for both Android and iOS. The CI/CD pipeline setup requires more configuration.

Native Libraries - Using native libraries within Flutter apps is not easy and straight forward. The support for calling into native libraries from Dart is still building up.