\n<\/p>\n
Posted by Fahd Imtiaz, Product Manager, Android Developer<\/em><\/p>\n \nWith Android reaching more devices, from phones to foldables to Chromebooks, building apps that seamlessly adapt to different screen sizes and types has never been more crucial. At this year\u2019s Google I\/O, we covered building adaptable apps, increasing user productivity with key inputs like keyboard and stylus, and scaling games across surfaces.\n<\/p>\n \nThroughout Google I\/O 2024, we\u2019ve talked a lot about how to build adaptive apps. With this shift, some of you may be asking \u201cwhat makes an app truly adaptive?\u201d\n<\/p>\n \nAdaptive apps take advantage of the full screen size they are on – whether that is a phone, a tablet, or a foldable. These apps adjust layout based on conditions, driving how your app\u2019s layout should adapt. These conditions include things like changes to the size of the window, device posture or font size.\n<\/p>\n \nAdaptive apps dynamically adjust their layouts by swapping components, showing, or hiding content based on the available window size, compared to simply stretching UI elements. With ever evolving form factors and screen sizes, adaptability for your app to any window size unlocks the seamless experiences users demand today.\n<\/p>\n \nNow that you know what they are, how do you get started building adaptive apps? We strongly recommend using WindowSizeClasses<\/a> as the opinionated breakpoints for your UI and we\u2019re bringing you a variety of new Compose APIs that make it easier to implement common adaptive layouts.\n<\/p>\n \nAvailable now in beta, the new Compose adaptive layout libraries<\/a> help you to make your UI look good across window sizes. From navigation UI<\/a> to list\/detail<\/a> and supporting pane style layouts<\/a>, we\u2019re providing composables to make building an adaptive app easier than ever.\n<\/p>\n \nCheck out these technical sessions to learn more:\n<\/p>\n \nOr get started by checking out the new documentation<\/a>!\n<\/p>\n \nTablets and foldables are great for consuming content but even better when it comes to creating content. That\u2019s why leveraging input devices like stylus for more productive experiences is especially important for your users.\n<\/p>\n \nStylus users on Android can remain more productive with new support for handwriting in text fields. You no longer need to put down your stylus when you need to input some text into a text field. Stylus handwriting and gestures will work automatically if you are using standard text components including BasicTextField in Compose (1.7), EditText in Views and text input elements in WebView.\n<\/p>\n \nFor stylus users, low latency is key to having a responsive inking experience. Reducing latency minimizes the amount of delay between when you move your stylus and when the ink appears on the screen, giving users a more authentic pen-to-paper experience. Based on developer feedback, we\u2019ve introduced new APIs to make low latency easier for apps that use Canvas for rendering.\n<\/p>\n \nA great example of these libraries in practice is Infinite Painter, where the team reduced their inking latency by 5x.\n<\/p>\n \nNext to the stylus, another essential input device is the physical keyboard that really shines when users need to do a lot of text input like long emails, documents or blog posts. As a developer, making it easy for users to navigate your app with keyboard navigation can set your app apart.\n<\/p>\n \nUsers should be able to navigate to all elements in your app with just their keyboard. It\u2019s also important that frequently used keyboard shortcuts are supported in your app. To help educate your users about shortcuts, consider making your keyboard shortcuts discoverable to users by adding entries to the system KeyboardHelper<\/a>.\n<\/p>\n \nTo improve the experience for keyboard, mouse, trackpad, and stylus users, we also recommend implementing hover states and keyboard focus. All interactive components should have a hover state and should show a visual cue<\/a> to indicate which component has the keyboard focus.\n<\/p>\n \nYou can learn more about all these improvements and more via the technical session<\/a>, and our updated documentation<\/a> and codelab<\/a>.\n<\/p>\n \nAlthough larger window sizes allow showing multiple panes of content at once, users often want to focus on one specific pane at a time. By following the new guidance<\/a> for pane expansion, users have the choice to see both panes at once, or resize them as they desire.<\/p>\n Google Calendar has added pane expansion to their supporting pane layout on expanded width window sizes, allowing users to resize to see more details of an event, or more information in their schedule.<\/p>\n \nAlthough larger window sizes allow showing multiple panes of content at once, users often want to focus on one specific pane at a time. By following the new guidance<\/a> for pane expansion, users have the choice to see both panes at once, or resize them as they desire.<\/p>\n Google Calendar has added pane expansion to their supporting pane layout on expanded width window sizes, allowing users to resize to see more details of an event, or more information in their schedule.<\/p>\n \nThis feature will be supported by activity embedding in Android 15, and is also planned to be supported by the material3-adaptive library.\n<\/p>\n \nGamers appreciate premium, immersive experiences and with Android tablets, foldables, desktops, and Chromebooks your game can reach more players than ever. Creating meaningful experiences on each of these devices is key to ensuring your game stands out.\n<\/p>\n <\/p>\n Diablo Immortal saw significantly increased engagement across all aspects of the game by users who play on multiple devices. <\/i><\/p>\n <\/i><\/p>\n \nDuring this year\u2019s Google I\/O, we are highlighting the best practices for rendering, managing assets, and windowing in resizable contexts to build quality experiences and impress your players across form factors.\n<\/p>\n \nWith the wide variety of devices and hardware configurations, provide configurable graphics options for your players. And, for the best experience right out of the box, define default graphics options for different devices. Additionally, consider trade offs like storage size, performance, and compatibility across platforms when deciding what texture compression formats to use.\n<\/p>\n \nLarge screen devices support different window sizes with configurations like multi-window mode and on orientation change and fold\/unfold. By default, Android provides a compatibility mode – but, for the most seamless experience, declare and handle configuration events. Display cutouts, hinges, and even system UI can also occlude your game window, so support edge-to-edge windowing and ensure no key game content is occluded. If you really want to take your game to the next level, consider using the Jetpack WindowManager library to support dynamic layouts on foldable devices.\n<\/p>\n \nTo provide smoother gameplay and reduce input latency consider using frame pacing. Also consider enabling wide color gamut support so that vivid colors are rendered properly while also maximizing contrast and brightness on large screen HDR displays to improve realism and immersion for your players.\n<\/p>\n \nWith the changing mobile landscape and transition from OpenGL to Vulkan, handle swapchain recreation after window configuration changes. If you rely on any device specific hardware features like host visible device local memory have fallback implementations for other platforms.\n<\/p>\n \nLearn more about the rendering best practices and how to level up your game across surfaces by tuning into this technical session<\/a> and be sure to check out our multiplatform optimization guide<\/a>.\n<\/p>\n \nYou can get started building adaptable apps that look great across tablets, foldables, Chromebooks and more by checking out the \u201cBuilding adaptive Android apps\u201d<\/a> technical session or heading to the large screens gallery<\/a> for content tailored to your specific app type – from productivity apps<\/a> to games<\/a>\u2026 and more!\n<\/p>\n<\/div>\nBuilding adaptive apps<\/h3>\n
![\"\"](\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEjzH-zcaTX6anX9deSBiGRpp52S8CDhQfR1njOx4pQW7xb1A1tA_nMEtsro7ShnS9t-XslBB7iDJXj96WdkQwD5XEzn4K-l_QFOPNNbsH5K9Oux9weJvtwFvD8n-qn4MJssu7ev5sj9I_R1myoJzuVkudkDz56UrToOp6UMdtANf1fjsGEc8eFl213X2lU\/s1376\/image1.gif\")
<\/a><\/div>\n<\/a><\/div>\nIncrease user productivity on tablet and foldables<\/h3>\n
Improving your app\u2019s stylus experience<\/span><\/h4>\n
<\/a><\/div>\nEnhancing productivity with keyboard and mouse support<\/span><\/h4>\n
Enhance productivity with pane expansion<\/span><\/h4>\n
<\/a><\/div>\nBuilding great games across surfaces<\/h3>\n
<\/a><\/div>\nGet started building adaptable apps from phones to tablets and foldables<\/h3>\n