{"id":2473,"date":"2022-05-19T12:18:20","date_gmt":"2022-05-19T19:18:20","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/surface-duo\/?p=2473"},"modified":"2022-05-19T12:18:20","modified_gmt":"2022-05-19T19:18:20","slug":"flutter-3-foldable","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/surface-duo\/flutter-3-foldable\/","title":{"rendered":"Flutter foldable support is now stable"},"content":{"rendered":"

\n Hello! Flutter 3 was announced<\/a> last week, and we have good news to share with you. The foldable support that we contributed to Flutter is now released in the latest stable<\/i> branch. Let us dive into what this means for you. We will first go over the new API that you can use and then review what else Flutter now does for you out of the box.\n<\/p>\n

What are Display Features?<\/h2>\n

\n Display features are parts of the display that create a visual distortion and can create a logical separation in the screen space. Our focus is on the hinge of the Surface Duo, but that is not the only type of display feature that Flutter knows about. The folding area on the Surface Galaxy Fold and the notch or cutout on many smartphones are also display features<\/em>.\n<\/p>\n

\n \"Visual\n<\/p>\n

\n For developers that work with both Android and Flutter, it is worth noting that Flutter display features are a bit different from Android display features. In Android, cutouts<\/a> and display features<\/a> are different concepts. Since Flutter works at a higher level, unifying the two concepts under one API was important.\n<\/p>\n

\n Until now, screens rarely made a shape other than a 2D plane. When a screen has a hinge<\/code> or fold<\/code> display feature, it can change shape. These shapes are called postures. When it looks like a book or laptop, the posture is half-opened<\/code>. When the screen is continuous, the posture is flat<\/code>.\n<\/p>\n

\n \"Visual\n<\/p>\n

\n Now that we went through the types of display features and what properties they might have, there is enough context for me to show you the structure that the DisplayFeature class has:\n<\/p>\n

class DisplayFeature {\r\n  final Rect bounds;\r\n  final DisplayFeatureType type;\r\n  final DisplayFeatureState state; \r\n}<\/pre>\n
\n  The bounds<\/code> represent the location and size of the display feature on the screen. The type<\/code> and state<\/code> are direct representations of the images above.\n<\/p>\n
MediaQuery has a new property<\/h2>\n
\n  The way you access information about display features is through MediaQuery.of(context).displayFeatures<\/code>. This is a new property, and it is a list. It is empty for devices that do not have any display features. For the Surface Duo, you can expect this list to have one item when your app is spanned across both screens and be empty when your app is in single-screen mode.\n<\/p>\n
\n  \"Screenshot\n<\/p>\n
\n  The app behavior should be the same in single-screen mode as on a candy bar smartphone. Therefore, no display feature is reported. Another way of thinking about it is that only display features that overlap your rendering area are reported.\n<\/p>\n
\n  \"Screenshot\n<\/p>\n
\n  On foldable devices that also have a cutout, you can expect the list to have two display features, one for the folding area and one for the cutout. If you rely on display features in many parts of your codebase, we recommend creating higher-level functions or widgets that help you with your specific enhancements. For example, checking the list to see if there is a hinge on the device could look like this and can be accessed through MediaQuery.of(context).hinge<\/code>:\n<\/p>\n
\/\/\/ Extension method that helps with working with the hinge specifically.\r\nextension MediaQueryHinge on MediaQueryData {\r\n  DisplayFeature? get hinge {\r\n    for (final DisplayFeature e in displayFeatures) {\r\n      if (e.type == DisplayFeatureType.hinge)\r\n        return e;\r\n    }\r\n    return null;\r\n  }\r\n}<\/pre>\n
Batteries included<\/h2>\n
\n  Some things simply work without you needing to do anything. For example, dialogs and popups were made aware of existing display features. They avoid overlapping them. \n<\/p>\n
\n  Dialogs, for instance, typically show in the middle of the screen. This would not be good when your app is spanned, since the dialog would overlap the hinge. To fix this, the default behavior for dialogs now is to show on the first<\/em> screen. The default behavior depends on Directionality<\/a> and puts the dialog on the left for left-to-right layouts or on the right on right-to-left layouts.\n<\/p>\n
\n  \"Screenshot\n<\/p>\n
\n  You have control over this behavior if you want to do something different. If you need finer control over this, you can use the anchorPoint<\/code> parameter. This is like a target on your display. The screen containing the target is the screen that renders the dialog. The anchorPoint<\/code> parameter is newly added to showDialog<\/code><\/a> and similar methods and is optional. What we think is particularly cool about this parameter is that you can easily show the dialog on the same screen that the user last interacted with. For example, you can create a helper widget or method that gives you the location on the screen of the button that led to showing the dialog.\n<\/p>\n
showDialog(\r\n  context: context,\r\n  anchorPoint: Offset(1000, 1000), \/\/ New and optional parameter.\r\n  builder: \u2026,\r\n);<\/pre>\n
\n  If instead of using showDialog<\/code>, you use custom popup routes and the navigator directly for rendering dialogs, you should wrap your routes with DisplayFeatureSubScreen<\/code>. Without doing this, your dialogs will overlap the hinge.\n<\/p>\n
class _MyRoute<T> extends PopupRoute<T> {\r\n  @override\r\n  Widget buildPage(...) {\r\n    return DisplayFeatureSubScreen(\r\n      child: ..., \/\/ previous content of buildPage\r\n      anchorPoint: ..., \/\/ optional\r\n    );\r\n  }\r\n}<\/pre>\n
Popup menus just work<\/h2>\n
\n  Popup menus, such as those in the following image, are also now aware of display features and avoid overlapping them. There is no change that you need to make since these contributions were made to showMenu<\/code><\/a>, which is then used by PopupMenuButton<\/code><\/a>.\n<\/p>\n
\n  \"Image\n<\/p>\n
What happened to TwoPane<\/h2>\n
\n  Since other parts of the framework did not depend on TwoPane we were able to make it part of the dual_screen package<\/a>. This way, we can iterate on it quicker and be a bit more opinionated on how it behaves. We have another blog article planned for diving into details about TwoPane and what else you can find in the dual_screen<\/code> package. Stay tuned for more (a good reason to follow us<\/a>) and in the meantime, you can read the package description<\/a>. \n<\/p>\n
Samples used in this article<\/h2>\n
\n  To give the new features a try you can quickly clone our Flutter foldable samples<\/a> and simply run the app. All the screenshots in this article are of our sample apps running in the Surface Duo Emulator. We recommend our Surface Duo emulator<\/a> as a target device since it simulates the hinge<\/code> display feature. Use the foldable devices available in Android Studio to simulate a fold<\/code> display feature.\n<\/p>\n
Call to action<\/h2>\n
    \n
  1. \n  If you are on the stable<\/code> flutter channel, run flutter upgrade<\/code>.\n<\/li>\n
  2. \n  Download the Surface Duo emulator<\/a>.\n<\/li>\n
  3. \n  Clone the Flutter foldable samples<\/a> and run it.\n<\/li>\n
  4. \n  If you have any questions or would like to tell us about your apps, use the feedback forum<\/a> or message us on Twitter @surfaceduodev<\/a>.\n<\/li>\n
  5. \n  Finally, please join us for the dual screen developer livestream<\/a> this Friday at 13h00 Central European Time and replay at 11am (Pacific time) \u2013 mark it in your calendar! You can also check out the archives on YouTube<\/a>.\n<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"
    Hello! Flutter 3 was announced last week, and we have good news to share with you. The foldable support that we contributed to Flutter is now released in the latest stable branch. Let us dive into what this means for you. We will first go over the new API that you can use and then […]<\/p>\n","protected":false},"author":54297,"featured_media":2480,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[31,693,717,706],"class_list":["post-2473","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-surface-duo-sdk","tag-dual-screen-development","tag-flutter","tag-foldable","tag-jetpack-window-manager"],"acf":[],"blog_post_summary":"
    Hello! Flutter 3 was announced last week, and we have good news to share with you. The foldable support that we contributed to Flutter is now released in the latest stable branch. Let us dive into what this means for you. We will first go over the new API that you can use and then […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/posts\/2473","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/users\/54297"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/comments?post=2473"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/posts\/2473\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/media\/2480"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/media?parent=2473"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/categories?post=2473"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/tags?post=2473"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}