Where Flutter apps break on one platform and not the other
Native features such as the camera, location, payments and Bluetooth come through plugins, and each plugin is really two pieces of native code with one Dart face.
The app crashes the moment an iPhone user opens the camera
How you'll know: Fine on Android, and an instant close on iOS when the feature is first used.
Fix: iOS needs a written usage description in Info.plist for the camera, photo library, location and similar. Without it the app is closed by the system, and App Review rejects it. Each plugin's setup notes list the keys it needs.
A plugin only really supports one platform
How you'll know: It installs fine, but a feature does nothing on one platform, or throws a missing-implementation error.
Fix: Check the platforms listed for the package on pub.dev, and read its open issues before depending on it. Where no good plugin exists, the developer writes the native piece and calls it through a platform channel.
The build stops working after nobody touched it for a year
How you'll know: A small text change won't compile, or a store refuses the upload.
Fix: Apple raises the minimum Xcode and SDK for new uploads, and Google Play raises the Android version apps must target. Updating the Flutter SDK, the plugins and the native build files together, then testing both platforms, is a planned job rather than an emergency if you do it once a year.
One abandoned plugin holds the whole app back
How you'll know: You can't update Flutter because one package hasn't been updated to work with it.
Fix: Replace it, take over a copy of it, or write that feature natively. Keeping the plugin list short from the start makes this rare.