![\"Get](\"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-content\/uploads\/sites\/53\/2020\/05\/get-your-app-ready-for-dual-screen-devices-in-3-st-1.png\")
<\/p>\n
Figure 1. Three steps to get your app ready for dual-screen devices<\/em><\/p>\n Today we are going to provide some additional useful tips for embracing new features (Step 3), so your app can take full advantage of both screens when it is spanned.<\/p>\n When creating apps, we often have to deal with different screen configurations (dimensions) and make design adjustments so the app adapts to whatever device it is being used on. Surface Duo is no different than other Android devices in that it also has its own device dimensions<\/a> that will need to be considered in your app design. Here are the Surface Duo screen specs to include in your app configuration:<\/p>\n Surface Duo dual-portrait screen specs:<\/p>\n Surface Duo dual-landscape screen specs:<\/p>\n When running your app on a Surface Duo device or emulator in single screen mode, you shouldn\u2019t need to make any specific layout changes as your app should work the same way as on any other single screen device. However, when your app is spanned across a dual-screen device, you may see that the layout that you are currently using is not perfectly adapted for this configuration. As an example, you might observe that there is content that is hidden by the hinge, and might consider some layout adjustments so that your app looks and behaves better when used on a dual-screen device. To manage these adjustments, Android provides qualifiers to handle multiple configurations<\/a>, so whether your app is running on a device with a small screen, a tablet with 10\u201d screen in landscape mode, or on Surface Duo, you can use different qualifier values to help you optimize your app for specific device configurations.<\/p>\n By default, your dimens, strings, layouts, and drawables, files go into the (default) values,<\/strong> layout <\/strong>and drawable<\/strong> folders in your app and the values located there are used as the default resources.<\/p>\n When your app is spanned across dual-screens (either in dual-portrait or dual-landscape mode), you can include alternative resources to support multiple device configurations (like dimens, strings, layouts, drawables, etc.) and can create new resource folders with specific qualifier values. For Surface Duo, you can use the qualifier sw720dp-2784×1800; <\/strong>so, for resource values the specific folder would be values-sw720dp-2784×1800<\/strong>, for layouts layout-sw720dp-2784×1800<\/strong>, etc. Surface Duo will take the resources located there and will use them. If no specific resources are available, Surface Duo will apply the existing qualifiers in order of precedence<\/a>.<\/p>\n To add a new resource folder, navigate to your res<\/strong> folder, right click over it and then select New<\/strong> -> Android resource Directory<\/strong>.<\/p>\n Figure 2. Creating a new Android resource directory<\/em><\/p>\n Then in the New Resource Directory<\/strong>, you just can simply type the directory name<\/strong> and accept:<\/p>\n Figure 3. Setting up the directory name<\/em><\/p>\n This is how your app folder structure should look after adding a specific Surface Duo resource folder:<\/p>\n Figure 4. App project structure with the default and a new specific values-resource folder<\/em><\/p>\n As an important note, remember to always define resources in the default configuration too, otherwise your app might encounter run time exceptions when the configuration changes.<\/p>\n You might be wondering why this strange resource folder qualifier name? If you go up to the Surface Duo dimensions spec we have shared above, you will see how the device in dual-landscape mode has a width of 720dp<\/strong>. This is the value we will use as the devices smallest width and this value doesn\u2019t change when the screen orientation changes, so this value remains constant whether we are in dual-portrait or dual-landscape mode.<\/p>\n The 2784×1800 <\/strong>value provides a more specific configuration. Since sw720dp can be shared with many available tablets on the market, the 2784×1800 <\/strong>value is the specific width and height of the Surface Duo device in pixels. As you can see, Surface Duo has a 1350px width per screen, so 1350 x 2 = 2700px; if we also add the width of the mask\/hinge (84px) we have now have a total width of 2784px (2700 + 84 = 2784px<\/strong>). For height, we simply use the screen height of 1800px, <\/strong>making our total screen value of 2784x1800px.<\/strong><\/p>\n To help you to visualize what we have covered here, we have created a qualifiers sample app in our Kotlin samples repository<\/a>. Please, have a look and play with the app and the Surface Duo emulator by using just one screen, spanning the app, rotating the emulator, etc. so you can see how the different resource folders are used in different device modes.<\/p>\n In the following figures, you can see how the app, that has specific resource folders for different configurations, behaves when running on a single screen device, a tablet, and on Surface Duo using its different configurations:<\/p>\n Figure 5. App running on a single screen device and on Surface Duo in single screen mode<\/em><\/p>\n <\/p>\n Figure 6. App running on a tablet (in landscape mode) and on Surface Duo in dual-portrait and dual-landscape modes<\/em><\/p>\n We are working on adding an official dual-screen qualifier which isn\u2019t just based on screen sizes so you will be able to define specific resources that Surface Duo will use when running your app on it.<\/p>\n We will share more about this in a future blog post.<\/p>\n Comments, questions, issues, requests, anything! We\u2019d love to hear from you!<\/p>\n Please leave us feedback using our\u00a0feedback forum<\/a>, or message me on\u00a0Twitter<\/a>\u00a0or\u00a0GitHub<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Hello Android dual-screen developers! As we mentioned in a previous blog post, enhancing your app for dual-screen devices is easily done by following this three step process: Figure 1. Three steps to get your app ready for dual-screen devices Today we are going to provide some additional useful tips for embracing new features (Step 3), […]<\/p>\n","protected":false},"author":30297,"featured_media":411,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[474,365,471,31,473,470,472,46],"class_list":["post-405","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-surface-duo-sdk","tag-android","tag-android-developer","tag-device-condiguration","tag-dual-screen-development","tag-kotlin","tag-qualifier","tag-sample","tag-surface-duo"],"acf":[],"blog_post_summary":" Hello Android dual-screen developers! As we mentioned in a previous blog post, enhancing your app for dual-screen devices is easily done by following this three step process: Figure 1. Three steps to get your app ready for dual-screen devices Today we are going to provide some additional useful tips for embracing new features (Step 3), […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/posts\/405","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\/30297"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/comments?post=405"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/posts\/405\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/media\/411"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/media?parent=405"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/categories?post=405"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-json\/wp\/v2\/tags?post=405"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Different configurations<\/h2>\n
\n
\n
Creating specific resources for Surface Duo<\/h2>\n
![\"Creating](\"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-content\/uploads\/sites\/53\/2020\/05\/creating-an-new-android-resource-directory-1.png\")
<\/p>\n![\"Setting](\"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-content\/uploads\/sites\/53\/2020\/05\/setting-the-name-for-the-new-resource-directory-1.png\")
<\/p>\n![\"Project](\"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-content\/uploads\/sites\/53\/2020\/05\/project-hierarchy-showing-the-duo-specific-resourc-1.png\")
<\/p>\nSample app running on different devices and configurations<\/h2>\n
![\"App](\"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-content\/uploads\/sites\/53\/2020\/05\/app-running-on-a-single-screen-device-and-on-surfa-1.png\")
<\/p>\n![\"App](\"https:\/\/devblogs.microsoft.com\/surface-duo\/wp-content\/uploads\/sites\/53\/2020\/05\/app-running-on-a-tablet-landscape-and-on-surface-1.png\")
<\/em><\/p>\nWhat\u2019s next?<\/h2>\n
Feedback<\/h2>\n