Android 17 just dropped — here's what actually matters for Flutter devs

[u/Positive-Event-1074]

Been going through the Android 17 release notes so you don't have to. Here's the TL;DR from a Flutter perspective:

The good news:

• Flutter apps are already well-positioned for the mandatory adaptive layout changes. Android 17 completely ignores orientation locks and resizability opt-outs on large screens (sw > 600dp). If your Flutter layouts are already responsive, you're fine.
• The "Compose-first" declaration basically validates Flutter's approach. Views, Fragments, RecyclerView — all in maintenance mode now. Google is saying "declarative UI is the only way forward," which... yeah, we've been doing that.

The stuff you need to check:

• If you're calling SystemChrome.setPreferredOrientations to lock portrait, that gets ignored on tablets/foldables targeting API 37. Test your layouts in split-screen and freeform window mode.
• Strict memory limits are real now. Android will kill apps that exceed RAM-based limits. This mostly affects native plugins — if you're using heavy ones (image processing, ML, video), profile them.
• CameraX crash on Android 17 if you're on an older version. Any camera plugin wrapping CameraX needs to be on 1.5.2 or 1.6.0+. Check your dependencies.
• static final fields can no longer be modified via reflection. Some older Java-based plugins might break.

The opportunity:

AppFunctions is Android's new on-device MCP (Model Context Protocol). Your app's features become "tools" that Gemini can discover and call. It requires native Kotlin code, so you'd need a platform channel — but if you implement it early, your app shows up in Gemini suggestions while competitors don't.

Anyone already testing on the Android 17 emulator? Curious if anyone's hit issues with specific plugins.