# Large Screen

Android application design and optimization for large-screen devices such as tablets, foldables, and ChromeOS devices.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Google will force Android developers to make their apps work properly on foldables

DevFeed: [Google will force Android developers to make their apps work properly on foldables](<https://devfeed.tech/articles/google-will-force-android-developers-to-make-their-apps-work-properly-on-foldables-143836.md>)

Original publisher: [Read original article](<https://www.techspot.com/news/114626-google-force-android-developers-make-their-apps-work.html>)

Author: Alfonso Maruccia

Published: 2026-11-19T16:18:00Z

Content type: news

Language: en

Sources: [TechSpot](<https://devfeed.tech/sources/techspot.md>)

Topics: [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [Android](<https://devfeed.tech/topics/android.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [android](<https://devfeed.tech/tags/android.md>), [android-17](<https://devfeed.tech/tags/android-17.md>), [api](<https://devfeed.tech/tags/api.md>), [apps](<https://devfeed.tech/tags/apps.md>), [design](<https://devfeed.tech/tags/design.md>), [developers](<https://devfeed.tech/tags/developers.md>), [foldable](<https://devfeed.tech/tags/foldable.md>), [foldables](<https://devfeed.tech/tags/foldables.md>), [gaming](<https://devfeed.tech/tags/gaming.md>), [google](<https://devfeed.tech/tags/google.md>), [google-play](<https://devfeed.tech/tags/google-play.md>), [google-play-store](<https://devfeed.tech/tags/google-play-store.md>), [guidelines](<https://devfeed.tech/tags/guidelines.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [playback](<https://devfeed.tech/tags/playback.md>), [software](<https://devfeed.tech/tags/software.md>), [standards](<https://devfeed.tech/tags/standards.md>), [support](<https://devfeed.tech/tags/support.md>)

### AI overview

Google Play is requiring Android apps to meet Tier 3 of its adaptive quality guidelines: fill foldable displays without letterboxing or compatibility modes, preserve text or playback state during rotation or folding, and support multi-window use. Enforcement is already live, and from April 2027 new releases must meet the baseline and include at least three foldable screenshots alongside standard phone screenshots. Older unupdated apps will remain downloadable but may receive less promotion. Gaming apps face additional requirements starting August 2027, and updated apps must target Android 17 API level 37. Tier 2 and Tier 1 apps may qualify for enhanced merchandising.

### Source excerpt

Google recently published the new "adaptive quality standards" Android developers will be required to adopt over the next few months. The change will affect apps published on the Google Play Store, with a specific focus on improving support for the latest foldable devices coming to Android. Read Entire Article

## Build for every screen with the latest Jetpack Compose updates from Android Developer Summit

DevFeed: [Build for every screen with the latest Jetpack Compose updates from Android Developer Summit](<https://devfeed.tech/articles/build-for-every-screen-with-the-latest-jetpack-compose-updates-from-android-developer-summit-118936.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/build-for-every-screen-jetpack-compose-updates>)

Author: Rebecca Gutteridge

Published: 2026-11-04T00:00:00Z

Content type: release

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [Android](<https://devfeed.tech/topics/android.md>), [mobile-ui-design](<https://devfeed.tech/topics/mobile-ui-design.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [jetpack-navigation](<https://devfeed.tech/topics/jetpack-navigation.md>), [deeplinks](<https://devfeed.tech/topics/deeplinks.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [cameraX](<https://devfeed.tech/topics/camerax.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [adaptive-development](<https://devfeed.tech/tags/adaptive-development.md>), [android](<https://devfeed.tech/tags/android.md>), [build](<https://devfeed.tech/tags/build.md>), [car](<https://devfeed.tech/tags/car.md>), [compose](<https://devfeed.tech/tags/compose.md>), [developer](<https://devfeed.tech/tags/developer.md>), [development](<https://devfeed.tech/tags/development.md>), [device](<https://devfeed.tech/tags/device.md>), [displays](<https://devfeed.tech/tags/displays.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [events-programs](<https://devfeed.tech/tags/events-programs.md>), [foldables](<https://devfeed.tech/tags/foldables.md>), [googlebook](<https://devfeed.tech/tags/googlebook.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [latest](<https://devfeed.tech/tags/latest.md>), [screen](<https://devfeed.tech/tags/screen.md>), [summit](<https://devfeed.tech/tags/summit.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The Compose 1.13 stable release is planned to add adaptive Grid and Flexbox layouts, Progressive Blur, and Formatted Text; the excerpt also describes a rewritten BasicTextField using TextFieldState and a buffer-driven architecture to avoid IME race conditions and support rich-text editing. Jetpack AppState, in alpha, extends Compose snapshot state into app architecture: Transform derives reactive state from State and Flow inputs, while StateStore shares observable keyed state across app surfaces and can persist it with DataStore. Navigation 3 version 1.2 adds type-safe deep links using Kotlin Serialization and supports custom argument parsing and synthetic back stacks. The excerpt also highlights Compose input support for trackpads, mice, and physical controls, adaptive multi-pane layouts using Navigation 3 and WindowManager, and Android skills for agent-assisted adaptive work, performance, XML migration, and Ink. These are summit highlights from the supplied excerpt, not a complete account of all sessions or announcements.

### Source excerpt

The Android ecosystem is a multi-device reality that spans phones, foldables, tablets, wearables, in-car displays, XR, and Googlebook. In this landscape, adaptive development is foundational to reaching users wherever they are.

## Googlebook Tablets Are Coming: What We Know About Lenovo's First Detachable

DevFeed: [Googlebook Tablets Are Coming: What We Know About Lenovo's First Detachable](<https://devfeed.tech/articles/googlebook-tablets-are-coming-what-we-know-about-lenovo-s-first-detachable-114872.md>)

Original publisher: [Read original article](<https://www.techrepublic.com/article/news-googlebook-detachable-tablets-lenovo-duet/>)

Author: Aminu Abdullahi

Published: 2026-11-03T15:34:35Z

Content type: news

Language: en

Sources: [TechRepublic](<https://devfeed.tech/sources/techrepublic.md>)

Topics: [lenovo](<https://devfeed.tech/topics/lenovo.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [acer](<https://devfeed.tech/tags/acer.md>), [added](<https://devfeed.tech/tags/added.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-mode](<https://devfeed.tech/tags/ai-mode.md>), [also](<https://devfeed.tech/tags/also.md>), [android](<https://devfeed.tech/tags/android.md>), [android-tablets](<https://devfeed.tech/tags/android-tablets.md>), [availability](<https://devfeed.tech/tags/availability.md>), [detachable](<https://devfeed.tech/tags/detachable.md>), [detachable-tablets](<https://devfeed.tech/tags/detachable-tablets.md>), [first](<https://devfeed.tech/tags/first.md>), [google](<https://devfeed.tech/tags/google.md>), [googlebook](<https://devfeed.tech/tags/googlebook.md>), [googlebook-os](<https://devfeed.tech/tags/googlebook-os.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [innovation](<https://devfeed.tech/tags/innovation.md>), [know](<https://devfeed.tech/tags/know.md>), [launch](<https://devfeed.tech/tags/launch.md>), [lenovo](<https://devfeed.tech/tags/lenovo.md>), [lenovo-googlebook-duet-m](<https://devfeed.tech/tags/lenovo-googlebook-duet-m.md>), [news](<https://devfeed.tech/tags/news.md>), [tablets](<https://devfeed.tech/tags/tablets.md>), [tech-industry](<https://devfeed.tech/tags/tech-industry.md>), [techrepublic](<https://devfeed.tech/tags/techrepublic.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Google confirmed that detachable tablets will join Googlebook, but gave no launch date, price or manufacturer. Lenovo appears to be the likely first maker: FCC records reportedly show a branded keyboard with pogo-pin connectors, and prior reports describe a kickstand, stylus support and a possible 13-inch Lenovo Googlebook Duet m with 16GB RAM and a MediaTek processor. Lenovo has not confirmed the device or specifications. The detachable design would separate the screen from the keyboard, unlike the current Acer convertible, which folds around a 360-degree hinge. Googlebook OS still restricts its home screen, Overview and app tray to landscape, a potential drawback for tablet use; Google may need to improve the tablet interface as well as encourage apps to adapt to screen sizes. Pricing and how the experience compares with Android tablets remain open questions.

### Source excerpt

Google confirms detachable Googlebook tablets are coming, with Lenovo rumored to launch the first model. Here's what to know about features and availability. The post Googlebook Tablets Are Coming: What We Know About Lenovo's First Detachable appeared first on TechRepublic.

## 6 Scenes, 36 Store Screenshots: A Fixture Pipeline for Identical iOS and Android Listings

DevFeed: [6 Scenes, 36 Store Screenshots: A Fixture Pipeline for Identical iOS and Android Listings](<https://devfeed.tech/articles/6-scenes-36-store-screenshots-a-fixture-pipeline-for-identical-ios-and-android-listings-105525.md>)

Original publisher: [Read original article](<https://hackernoon.com/6-scenes-36-store-screenshots-a-fixture-pipeline-for-identical-ios-and-android-listings?source=rss>)

Author: Philip Ellis

Published: 2026-10-28T21:20:21Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [Android](<https://devfeed.tech/topics/android.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Android Testing](<https://devfeed.tech/topics/android-testing.md>), [Image](<https://devfeed.tech/topics/image.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [about](<https://devfeed.tech/tags/about.md>), [android](<https://devfeed.tech/tags/android.md>), [android-listing](<https://devfeed.tech/tags/android-listing.md>), [app](<https://devfeed.tech/tags/app.md>), [app-store](<https://devfeed.tech/tags/app-store.md>), [app-store-screenshots](<https://devfeed.tech/tags/app-store-screenshots.md>), [automated](<https://devfeed.tech/tags/automated.md>), [automation](<https://devfeed.tech/tags/automation.md>), [data](<https://devfeed.tech/tags/data.md>), [fastlane](<https://devfeed.tech/tags/fastlane.md>), [foldables](<https://devfeed.tech/tags/foldables.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ios-listing](<https://devfeed.tech/tags/ios-listing.md>), [phones](<https://devfeed.tech/tags/phones.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [play](<https://devfeed.tech/tags/play.md>), [play-store](<https://devfeed.tech/tags/play-store.md>), [screenshots](<https://devfeed.tech/tags/screenshots.md>), [store](<https://devfeed.tech/tags/store.md>), [tablets](<https://devfeed.tech/tags/tablets.md>), [tests](<https://devfeed.tech/tags/tests.md>), [ui](<https://devfeed.tech/tags/ui.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

A fixture driven pipeline creates matching store screenshots from six courier app scenes across iOS and Android, with raw capture separated from caption composition. Both platforms use fixed fictional data and a clock aligned to the 9:41 status bar. On iOS, a DEBUG-only launch argument swaps in fixture services and routes directly to a scene; XCUITest, fastlane, and configured simulators capture it. Android uses a dedicated screenshots build type and source set with fixture services, UI tests that tap through screens, and emulator scripts. Unhandled Android fixture calls throw and log the missing method. Pillow composes captions independently, so copy edits do not require rebuilding or recapturing; wording can reflect platform differences, such as navigation handled by Android's map app. The pipeline checks capture dimensions and, on Android, rejects nearly blank images. Warm-up tests reduce map loading issues, but timed waits cannot guarantee complete tiles, so images still need visual inspection. The resulting set also helps compare layouts across device widths, though it does not cover long text, errors, empty lists, or interactions.

### Source excerpt

How we automated App Store and Play Store screenshots for phones, tablets and foldables with fixture data, UI tests, fastlane and Pillow.

## The case for a full-circle Googlebook future

DevFeed: [The case for a full-circle Googlebook future](<https://devfeed.tech/articles/the-case-for-a-full-circle-googlebook-future-104554.md>)

Original publisher: [Read original article](<https://www.computerworld.com/article/4241218/googlebook-future.html>)

Author: JR Raphael

Published: 2026-10-28T09:45:00Z

Content type: opinion

Language: en

Sources: [Computerworld](<https://devfeed.tech/sources/computerworld.md>)

Topics: [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [chromeos](<https://devfeed.tech/topics/chromeos.md>), [chromebook](<https://devfeed.tech/topics/chromebook.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-17](<https://devfeed.tech/tags/android-17.md>), [android-computers-computers-and-peripherals-google-laptops-operating-systems-tablets](<https://devfeed.tech/tags/android-computers-computers-and-peripherals-google-laptops-operating-systems-tablets.md>), [chromebook](<https://devfeed.tech/tags/chromebook.md>), [chromeos](<https://devfeed.tech/tags/chromeos.md>), [computer](<https://devfeed.tech/tags/computer.md>), [computers-and-peripherals](<https://devfeed.tech/tags/computers-and-peripherals.md>), [ecosystem](<https://devfeed.tech/tags/ecosystem.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [future](<https://devfeed.tech/tags/future.md>), [google](<https://devfeed.tech/tags/google.md>), [googlebook](<https://devfeed.tech/tags/googlebook.md>), [googlebook-os](<https://devfeed.tech/tags/googlebook-os.md>), [interface](<https://devfeed.tech/tags/interface.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [laptop](<https://devfeed.tech/tags/laptop.md>), [laptops](<https://devfeed.tech/tags/laptops.md>), [lenovo](<https://devfeed.tech/tags/lenovo.md>), [operating-system](<https://devfeed.tech/tags/operating-system.md>), [operating-systems](<https://devfeed.tech/tags/operating-systems.md>), [os](<https://devfeed.tech/tags/os.md>), [phone](<https://devfeed.tech/tags/phone.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [screen](<https://devfeed.tech/tags/screen.md>), [software](<https://devfeed.tech/tags/software.md>), [storytype-analysis](<https://devfeed.tech/tags/storytype-analysis.md>)

### AI overview

The author argues that Googlebook OS may make more sense as the basis for Android tablets than as a full laptop replacement. It combines a familiar Android interface, large-screen touches, phone connections and a less restrictive browser; the author says these strengths suit a touch-focused companion device where productivity is occasional, while serious laptop use still feels awkward and less polished than Chromebook. The piece proposes that Google could relaunch tablets as Googlebooks, then speculates that a shared OS might eventually blur the distinction between Googlebook phones and Android phones. These are possibilities, not announced plans.

### Source excerpt

Put on your finest propeller-packin' thinking caps, my fellow Android-appreciating animals -- 'cause I've got a brain-bending bit of big-picture thinking about the future of Android and everything around it. This pondering comes out of my ongoing time living with one of Google's new Googlebook laptops -- the beautifully built Lenovo Googlebook (provided to me as a short-term loaner for editorial assessment). Right now, the Googlebook experience itself is best summed up as an awkward start with plenty of potential. Android in a laptop environment just comes with an awful lot of asterisks, especially when you're trying to use such a system for serious work. In many ways, it feels like a step down from the more polished and productivity-optimized Chromebook setup it's ultimately designed to replace. But while working on a Googlebook and using it as your primary computer still seems like a bit of a square-peg situation, I've been struck by one area where the Googlebook OS software at the center of the experience feels almost shockingly natural. And that's led me down a rabbit hole of pondering about the bigger-picture implications of this operating system and how it could, at least in theory, one day affect the rest of the Android ecosystem. Lemme explain. [Get original Googley insight in your inbox with my free Android Intelligence newsletter -- one new thing to try every Friday.] A Googlebook by any other name So, at its core, Googlebook OS is essentially Android -- right? The software that powers Googlebooks is a specialized version of Android 17 designed to have some ChromeOS-like elements along with phone-connecting powers and a handful of feature additions that help it work better on a big screen. And the more I use it, the more I keep coming back to a thought that I mentioned in passing in my initial Googlebook analysis -- that this is what the Android tablet interface oughta be. Think about it: Google has never really figured out how it wants an Android tablet to wor

## Agentic and Flexible: A next era of Android development

DevFeed: [Agentic and Flexible: A next era of Android development](<https://devfeed.tech/articles/agentic-and-flexible-a-next-era-of-android-development-105740.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/build-it-your-way-a-next-era-of-android-development>)

Author: Matthew McCullough

Published: 2026-10-28T00:00:00Z

Content type: news

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [Android XR](<https://devfeed.tech/topics/android-xr.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Jetpack XR SDK](<https://devfeed.tech/topics/jetpack-xr-sdk.md>), [AI in frontend development](<https://devfeed.tech/topics/ai-in-frontend-development.md>), [ML Kit](<https://devfeed.tech/topics/ml-kit.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [google-antigravity](<https://devfeed.tech/topics/google-antigravity.md>), [Android Testing](<https://devfeed.tech/topics/android-testing.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [android](<https://devfeed.tech/tags/android.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [apis](<https://devfeed.tech/tags/apis.md>), [apps](<https://devfeed.tech/tags/apps.md>), [availability](<https://devfeed.tech/tags/availability.md>), [build](<https://devfeed.tech/tags/build.md>), [dev](<https://devfeed.tech/tags/dev.md>), [development](<https://devfeed.tech/tags/development.md>), [era](<https://devfeed.tech/tags/era.md>), [everyday](<https://devfeed.tech/tags/everyday.md>), [flexibility](<https://devfeed.tech/tags/flexibility.md>), [flexible](<https://devfeed.tech/tags/flexible.md>), [great](<https://devfeed.tech/tags/great.md>), [next](<https://devfeed.tech/tags/next.md>), [product-news](<https://devfeed.tech/tags/product-news.md>), [summit](<https://devfeed.tech/tags/summit.md>), [tools](<https://devfeed.tech/tags/tools.md>)

### AI overview

Android's announced tools aim to reduce development friction through agent choice, agent-ready workflows, new APIs, and broader form-factor support. Android Studio Rabbit 2 is stable and supports Claude Agent, Codex, Antigravity, and 40+ ACP-compliant agents. Android CLI adds Firebase-powered remote device testing, Compose previews, Perfetto profiling, bundle and library analysis, and 30+ Android skills; official plugins are also available for Antigravity, Claude Code, and Codex. For agentic apps, AppFunctions is in beta, while A2UI for Compose and ML Kit's Gemini Nano 4 Agentic API are in alpha. Connected Apps can be prototyped before applying for the production preview. Adaptive development updates include alpha AppState, stable Navigation 3 1.2, and adaptive layout features planned for Compose 1.13. The excerpt also announces stable Jetpack XR libraries, Android Studio XR emulators, XR Engine Hub, and geospatial APIs. Google Play foldable requirements are to be detailed later.

### Source excerpt

Today, at the Android Dev Summit, we are announcing the broad availability of many tools and APIs designed to remove everyday friction and give you more flexibility to build great Android apps.

## The Googlebook work test: Can an Android laptop get the job done?

DevFeed: [The Googlebook work test: Can an Android laptop get the job done?](<https://devfeed.tech/articles/the-googlebook-work-test-can-an-android-laptop-get-the-job-done-90842.md>)

Original publisher: [Read original article](<https://www.computerworld.com/article/4237256/googlebook-work-test-can-an-android-laptop-get-the-job-done.html>)

Author: JR Raphael

Published: 2026-10-20T11:00:00Z

Content type: article

Language: en

Sources: [Computerworld](<https://devfeed.tech/sources/computerworld.md>)

Topics: [chromebook](<https://devfeed.tech/topics/chromebook.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>)

Tags: [acer](<https://devfeed.tech/tags/acer.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-features](<https://devfeed.tech/tags/ai-features.md>), [android](<https://devfeed.tech/tags/android.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [android-chromeos-computers-computers-and-peripherals-google-laptops-operating-systems-product](<https://devfeed.tech/tags/android-chromeos-computers-computers-and-peripherals-google-laptops-operating-systems-product.md>), [app](<https://devfeed.tech/tags/app.md>), [app-ecosystem](<https://devfeed.tech/tags/app-ecosystem.md>), [apple](<https://devfeed.tech/tags/apple.md>), [chromebook](<https://devfeed.tech/tags/chromebook.md>), [chromeos](<https://devfeed.tech/tags/chromeos.md>), [computers-and-peripherals](<https://devfeed.tech/tags/computers-and-peripherals.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [google](<https://devfeed.tech/tags/google.md>), [googlebook](<https://devfeed.tech/tags/googlebook.md>), [iphone](<https://devfeed.tech/tags/iphone.md>), [journalism](<https://devfeed.tech/tags/journalism.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [laptop](<https://devfeed.tech/tags/laptop.md>), [lenovo](<https://devfeed.tech/tags/lenovo.md>), [operating-systems](<https://devfeed.tech/tags/operating-systems.md>), [productivity](<https://devfeed.tech/tags/productivity.md>), [productivity-software](<https://devfeed.tech/tags/productivity-software.md>), [review](<https://devfeed.tech/tags/review.md>), [reviews](<https://devfeed.tech/tags/reviews.md>), [storytype-analysis](<https://devfeed.tech/tags/storytype-analysis.md>), [tech-journalism](<https://devfeed.tech/tags/tech-journalism.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

The $1,149 Lenovo Googlebook pairs Android at its core with desktop Chrome and laptop features, but the review finds it awkward and unreliable for work in its current state. The interface and keyboard shortcuts require adjustment, and productivity apps vary: Docs sometimes blanks with several tabs open, Superhuman fails, Notion's Android app is less capable than its web version, and web app installation errors affect Notion and Slack. Linux apps are limited to command-line installation and do not integrate into the main interface; ChromeOS's Windows app support is absent. Strengths include a customizable desktop with widgets, smooth Android app performance, phone file access, useful phone notifications, and strong Lenovo hardware. App streaming and AI features are mixed: Authy cannot stream or install, Wallet hangs, Magic Pointer is rarely useful to the reviewer, and Rambler rewrites speech rather than directly transcribing it. The reviewer sees potential but does not consider it a strong Chromebook or laptop replacement yet; progress depends partly on developers building better support.

### Source excerpt

In a weird way, I've been thinking about the idea of a Googlebook for well over a decade now -- despite the fact that such a product has only officially existed for a matter of months. I'm relatively unusual in the world of tech journalism, y'see, in that I've been both writing about Android and ChromeOS since the platforms' earliest days and actively using devices from both ends of those ecosystems in my own day-to-day life that entire time. Most tech writers tend to be iPhone owners and Chromebook skeptics who see this part of the digital world from an outside view -- once a year or so, when significant new devices come along for assessment -- without having the perspective of someone who's truly immersed in it day in and day out. That distinction is always painfully apparent when you read a review that waxes on endlessly with out-of-touch iPhone comparisons and comments about the limiting nature of Google's ChromeOS concept -- positions that simply aren't accurate for those of us who live in these ecosystems and embrace the philosophies they offer. This won't be one of those reviews, and I perhaps more than anyone have been champing at the bit to get my hands on one of Google's new Android-ChromeOS-combining Googlebooks since the vaguest concept of these devices first appeared on the horizon earlier this year. So keep that in mind when I tell you, coming from the perspective of someone who very much wanted to love this: Using a Googlebook is an extraordinarily strange experience -- especially when you're treating it like a regular laptop, as it's being positioned by Google, and relying on it to get real work done. But amidst all the oddness, there are some true high points along with plenty of intriguing, if unfinished-feeling, potential. Here's what it's been like trying to actually work on a Googlebook -- specifically, the Lenovo Googlebook, which sells for $1,149 (and was provided to me as a short-term loaner from Lenovo for the purposes of this article). The Google

## iPhone Duo with Sample Code for All Six Orientations!

DevFeed: [iPhone Duo with Sample Code for All Six Orientations!](<https://devfeed.tech/articles/iphone-duo-with-sample-code-for-all-six-orientations-59717.md>)

Original publisher: [Read original article](<https://medium.com/mobile-app-development-publication/iphone-duo-with-sample-code-for-all-six-orientations-c4a24073cdc6?source=rss----f9c208bdbb09---4>)

Author: Elye - A Dev By Grace

Published: 2026-09-25T05:57:31Z

Content type: tutorial

Language: en

Sources: [Mobile App Development Publication](<https://devfeed.tech/sources/mobile-app-development-publication-medium.md>)

Topics: [Mobile](<https://devfeed.tech/topics/mobile.md>), [mobile-app-development](<https://devfeed.tech/topics/mobile-app-development.md>), [iphone](<https://devfeed.tech/topics/iphone.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [code](<https://devfeed.tech/tags/code.md>), [design](<https://devfeed.tech/tags/design.md>), [ios](<https://devfeed.tech/tags/ios.md>), [ios-app-development](<https://devfeed.tech/tags/ios-app-development.md>), [ios-development](<https://devfeed.tech/tags/ios-development.md>), [iphone](<https://devfeed.tech/tags/iphone.md>), [layouts](<https://devfeed.tech/tags/layouts.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>)

### AI overview

This tutorial discusses designing an iPhone Duo interface across six layouts or orientations, with sample code and comparisons to earlier iPhone and foldable Android device designs.

### Source excerpt

With a single iPhone Duo, Apple recommend 6 different layouts to consider. Let's tackle them all. Continue reading on Mobile App Development Publication "

## How to adapt Android apps for Googlebook laptops

DevFeed: [How to adapt Android apps for Googlebook laptops](<https://devfeed.tech/articles/land-your-apps-on-googlebook-with-adaptive-development-58049.md>)

Original publisher: [Read original article](<https://android-developers.googleblog.com/2026/09/adaptive-development-scale-app-googlebook.html>)

Author: Android Developers (noreply@blogger.com)

Published: 2026-09-22T17:00:00Z

Content type: article

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [App](<https://devfeed.tech/topics/app.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [layout](<https://devfeed.tech/topics/layout.md>), [navigation](<https://devfeed.tech/topics/navigation.md>), [Google](<https://devfeed.tech/topics/google.md>), [Hardware](<https://devfeed.tech/topics/hardware.md>)

Tags: [adaptive-development](<https://devfeed.tech/tags/adaptive-development.md>), [android](<https://devfeed.tech/tags/android.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [development](<https://devfeed.tech/tags/development.md>), [google](<https://devfeed.tech/tags/google.md>), [googlebook](<https://devfeed.tech/tags/googlebook.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [information-density](<https://devfeed.tech/tags/information-density.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [layouts](<https://devfeed.tech/tags/layouts.md>), [optimized](<https://devfeed.tech/tags/optimized.md>)

### AI overview

Google describes Googlebook as a laptop category built on Android and explains how developers can adapt existing Android apps for large displays and desktop use. The guidance covers adaptive layouts, window size classes, multi-input support, multi-pane interfaces, and Navigation 3 strategies.

### Source excerpt

Posted by Fahd Imtiaz, Senior Product Manager, and Loryn Hairston, Product Marketing Manager, Android Developer Googlebook introduces a new category of laptops built on a shared Android foundation. High-performance hardware from partners such as HP, Dell, Lenovo, Acer, and Asus, combines mobile convenience with desktop power. Googlebook offers high-resolution OLED touchscreens, dedicated keyboards, and precision trackpads with all-day battery life and OS-level Gemini Intelligence. With Googlebook, users can transition fluidly from quick interactions on their phones to rich, immersive sessions on their laptop. Bringing your app to Googlebook opens up valuable opportunities for you across the Android ecosystem. Google Play highlights optimized titles with dedicated badging, enhanced search, and featured spots across curated store homepages. Delivering this level of quality also prepares your app for the Apps Experience Program, where you can enroll to unlock a new program rate card designed to drive business growth. Even better, when users set up their new Googlebook using their Android phone, optimized apps are prominently highlighted for easy transfer, giving your app day-one presence on their new device. Optimized for desktop badging and dedicated collections on Google Play. The best part? You don't need to build a separate app from the ground up to take advantage of this reach. Adaptive development is how modern Android apps naturally scale across large displays, new device postures, and emerging form factors. If your app already embraces adaptive layouts, it is primed for Googlebooks. By building on your existing foundation of adaptive UI, window size classes, and multi-input support, you can deliver an optimized experience. Adaptive layouts reorganizing mobile views into a multi-pane experience. Anchor your app in desktop fundamentals On a laptop, your app operates within a desktop environment where user expectations shift toward higher information density, prec

## Emulator control for adaptive app development

DevFeed: [Emulator control for adaptive app development](<https://devfeed.tech/articles/emulator-control-for-adaptive-app-development-4234.md>)

Original publisher: [Read original article](<https://android-developers.googleblog.com/2026/08/emulator-adaptive.html>)

Author: Android Developers (noreply@blogger.com)

Published: 2026-08-31T16:00:00Z

Content type: article

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Android Studio](<https://devfeed.tech/topics/android-studio.md>), [Terminal](<https://devfeed.tech/topics/terminal.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [developer](<https://devfeed.tech/tags/developer.md>), [devices](<https://devfeed.tech/tags/devices.md>), [feature](<https://devfeed.tech/tags/feature.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

This article explains how to use Android Emulator console commands from a terminal to test adaptive app behavior across foldable configurations, display sizes, rotations, and physical postures. It highlights fire-and-forget commands and targeting specific virtual devices with adb.

### Source excerpt

Posted by Rob Orgiu, Developer Relations Engineer, Adaptive Apps, Android Adaptive app development is fundamental on Android, but making sure everything looks good and every feature works the way it should require multiple tests on multiple devices. Or does it? Well, yes... and no! While Android Studio is bundled with the Resizable Emulator to let you test layouts manually, there's a faster, more streamlined way to control form factors directly from your terminal. By leveraging fire-and-forget console commands using the adb emu shortcut, you can execute commands that immediately return control to your invoking shell. If you have multiple emulators running at the same time, you can target a specific virtual device by passing in the shortcut's serial: adb -s <serial> emu <command> <parameter> First things first: Fold and unfold To test foldable-specific user journeys and layout configurations, you can fold and unfold your emulated device programmatically. adb emu fold If your foldable emulator is unfolded, you can fold it to display its smaller screen configuration, powering on the (virtual) external display. To unfold the emulator and power on the internal display, simply run: adb emu unfold Now, you can instantly verify that your app preserves its state and that layouts appear exactly as they should on different display sizes. Rotation, rotation, rotation Correctly handling orientation changes is a cornerstone of adaptive app development. You can trigger device rotations programmatically to test how well your app handles configuration changes, including state restoration. The following command rotates the device 90° clockwise: adb emu rotate Simulating postures using sensors What about placing the emulator into a specific physical posture, like tabletop mode? The easiest approach is querying for the number of available positions with . First, list all available sensors and their current status: adb emu posture This returns a list of positions similar to the following:

## Emulator control for adaptive app development

DevFeed: [Emulator control for adaptive app development](<https://devfeed.tech/articles/emulator-control-for-adaptive-app-development-88693.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/emulator-control-for-adaptive-app-development>)

Author: Rob Orgiu

Published: 2026-08-31T00:00:00Z

Content type: tutorial

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Wireless Debugging](<https://devfeed.tech/topics/wireless-debugging.md>), [adb](<https://devfeed.tech/topics/adb.md>), [Android](<https://devfeed.tech/topics/android.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [Responsive Design](<https://devfeed.tech/topics/responsive-design.md>), [Macrobenchmark](<https://devfeed.tech/topics/macrobenchmark.md>)

Tags: [adb](<https://devfeed.tech/tags/adb.md>), [android](<https://devfeed.tech/tags/android.md>), [android-studio](<https://devfeed.tech/tags/android-studio.md>), [command-line](<https://devfeed.tech/tags/command-line.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [foldable](<https://devfeed.tech/tags/foldable.md>), [product-news](<https://devfeed.tech/tags/product-news.md>), [tests](<https://devfeed.tech/tags/tests.md>)

### AI overview

A tutorial explains how to use adb emulator console commands from a terminal to test adaptive Android apps. It covers folding and unfolding, rotation, simulated postures, and changing the resizable emulator's display size, allowing developers to check layouts and app state across form factors.

### Source excerpt

Adaptive app development is fundamental on Android, but making sure everything looks good and every feature works the way it should require multiple tests on multiple devices. Or does it?

## Enhance your app for the new Pixel lineup: Unveiled at Made by Google

DevFeed: [Enhance your app for the new Pixel lineup: Unveiled at Made by Google](<https://devfeed.tech/articles/enhance-your-app-for-the-new-pixel-lineup-unveiled-at-made-by-google-4240.md>)

Original publisher: [Read original article](<https://android-developers.googleblog.com/2026/08/pixel-app-experience-made-by-google.html>)

Author: Android Developers (noreply@blogger.com)

Published: 2026-08-12T19:00:00Z

Content type: article

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [App](<https://devfeed.tech/topics/app.md>), [Canvas](<https://devfeed.tech/topics/canvas.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [building](<https://devfeed.tech/tags/building.md>), [compose](<https://devfeed.tech/tags/compose.md>), [developer](<https://devfeed.tech/tags/developer.md>), [features](<https://devfeed.tech/tags/features.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [platform](<https://devfeed.tech/tags/platform.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

Android guidance for adapting apps to foldables and expanded displays. It covers Window Size Classes, Jetpack Compose, state preservation with ViewModel, and posture-specific layouts for responsive experiences across screen sizes and device configurations.

### Source excerpt

Posted by Fahd Imtiaz, Senior Product Manager, Loryn Hairston, Product Marketing Manager, and Tracy Agyemang, Product Marketing Manager, Android Developer Made by Google expands what's possible across the Android ecosystem. With the introduction of the Pixel 11 Pro Fold, Pixel Watch 5, and the entire Pixel family, users are moving seamlessly across diverse screen sizes, unique postures, and intelligent experiences. For you, the developer, this represents a massive opportunity: foldable users spend about 14x more than standard phone users. To help you elevate your existing experience without starting from scratch, we're sharing our latest platform guidance alongside real-world examples from developers already putting these features into production. Deliver adaptive experiences across foldables and expanded displays The Pixel 11 Pro Fold gives your app a chance to flex its capabilities with an expanded inner display and a standard size outer screen. Building for the foldable form factor requires dropping hardcoded layout rules and designing around available window space. Leveraging Jetpack Compose APIs like Navigation 3 with Scene strategies or our newest layout APIs like Grid and FlexBox allows your layout containers to automatically wrap, span, and reflow. You can also use the experimental MediaQuery API to dynamically adapt your UI to environmental signals like foldable posture, and keyboard states. Building adaptively requires tracking actual app dimensions rather than physical device size, especially during split-screen and multitasking flows. Using Window Size Classes from the WindowManager library allows your layout to respect folds and hinges as natural content separators. For instance, Notability leveraged Material 3 Window Size Classes to create a responsive two-pane layout that transitions smoothly between folded and expanded screens. As Ryan Shea, Android Engineering Manager at Notability, shared, tracking the window itself allows their layout and canvas z

## More linked devices are on the table (and the Android tablet)

DevFeed: [More linked devices are on the table (and the Android tablet)](<https://devfeed.tech/articles/more-linked-devices-are-on-the-table-and-the-android-tablet-1788.md>)

Original publisher: [Read original article](<https://signal.org/blog/linked-devices-and-android-tablets/>)

Published: 2026-08-04T00:00:00Z

Content type: article

Language: en

Sources: [Signal](<https://devfeed.tech/sources/signal-blog.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [App](<https://devfeed.tech/topics/app.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [devices](<https://devfeed.tech/tags/devices.md>), [ios](<https://devfeed.tech/tags/ios.md>), [iphone](<https://devfeed.tech/tags/iphone.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [support](<https://devfeed.tech/tags/support.md>), [sync](<https://devfeed.tech/tags/sync.md>), [ux](<https://devfeed.tech/tags/ux.md>)

### AI overview

Signal's latest Android update adds support for linking another Android phone or Android tablet, keeping messages synchronized across devices. The article also describes interface improvements for tablets, foldable phones, and other large-screen devices, alongside expanded linked-device support for iOS and iPhone.

### Source excerpt

The latest update for Signal Android introduces comprehensive support for linked devices. Now you can easily link another Android phone or Android tablet to your Signal account. Thanks to significant interface improvements to better support large devices, your messages will stay in sync across every screen and look good on all of them too. We're also expanding linked device support on iOS so you can link an iPhone to your Signal account in addition to our ongoing support for iPads. Signal Android v8.20 and Signal iOS v8.22 are rolling out now. Feel free to stop here if that's all you needed to know, but there's more info ahead if you want to kill some time while you wait for your freshly unboxed second (or third) device to finish charging. Read more...

## Optimize your apps for the next generation of Samsung Galaxy devices

DevFeed: [Optimize your apps for the next generation of Samsung Galaxy devices](<https://devfeed.tech/articles/optimize-your-apps-for-the-next-generation-of-samsung-galaxy-devices-4228.md>)

Original publisher: [Read original article](<https://android-developers.googleblog.com/2026/07/optimize-galaxy-screen-sizes.html>)

Author: Android Developers (noreply@blogger.com)

Published: 2026-07-22T19:00:00Z

Content type: article

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Large Screen](<https://devfeed.tech/topics/large-screen.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [devices](<https://devfeed.tech/tags/devices.md>), [samsung](<https://devfeed.tech/tags/samsung.md>), [tooling](<https://devfeed.tech/tags/tooling.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

Guidance for adapting Android app layouts to Samsung foldable and wearable devices, including ultra-wide landscape-first displays.

### Source excerpt

Posted by Fahd Imtiaz, Senior Product Manager and Miguel Montemayor, Developer Relations Engineer, Android Developer Experience Today at Galaxy Unpacked, Samsung unveiled its latest lineup of foldable and wearable devices. For developers, this means that the variety of form factors, screen sizes, and device postures your app needs to support is expanding once again. With devices like the Galaxy Z Fold8, the ecosystem is expanding to include hardware with a landscape-first natural orientation and a wider aspect ratio in its main display state. Whether a user is unfolding a large display, flipping open a cover screen, or glancing at their wrist, users expect a flawless experience. To help you meet this moment, we're sharing actionable guidance and new tooling updates to enable you to build adaptively proactively. Rethink layout architecture for dynamic displays, including ultra-wide foldables Building for the latest foldables means dropping assumptions about display orientation and size. This is especially true for the Galaxy Z Fold8, which adopts an ultra-wide display, adding to the variety of aspect ratios to account for. Devices with this landscape-first natural orientation show the limitations of hardcoded layout rules when users unfold the device. That's why we've introduced dedicated guidance for building for landscape foldables and trifolds. To build a responsive UI that handles these physics seamlessly, focus on the following core pillars: Build fluid, adaptive layouts: Wide aspect ratios and compact vertical heights require fluid UIs that scale responsively. Our updated adaptive design guidance advises considering the window class width first to determine layout changes, then adjusting for height. To let individual components fluidly adapt to the grid, structure your layout using flexible containers that allow your content to automatically wrap, span, and reflow. For design inspiration browse our adaptive sample app and dual-screen design galleries. Track act

## Motion, Stylus, Trackpads And Foldables In The Core

DevFeed: [Motion, Stylus, Trackpads And Foldables In The Core](<https://devfeed.tech/articles/motion-stylus-trackpads-and-foldables-in-the-core-19375.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/motion-input-form-factors/>)

Author: Shai Almog

Published: 2026-07-05T00:00:00Z

Content type: tutorial

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [cross-platform](<https://devfeed.tech/topics/cross-platform.md>), [Hardware](<https://devfeed.tech/topics/hardware.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [iOS](<https://devfeed.tech/topics/ios.md>)

Tags: [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [devices](<https://devfeed.tech/tags/devices.md>), [hardware](<https://devfeed.tech/tags/hardware.md>), [ios](<https://devfeed.tech/tags/ios.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [screen](<https://devfeed.tech/tags/screen.md>), [sensors](<https://devfeed.tech/tags/sensors.md>)

### AI overview

This article describes Codename One APIs for motion sensors, gesture recognition, detailed pointer and stylus input, wheel and trackpad events, context menus, and foldable-device support across multiple form factors.

### Source excerpt

Motion sensors, gestures, pointer detail, wheel events, stylus input, trackpads and foldable posture are now core Codename One APIs.

## Codename One Release Adds Car Dashboards, Motion Sensors, Foldables, Commerce, Video Generation, and Versioned Builds

DevFeed: [Codename One Release Adds Car Dashboards, Motion Sensors, Foldables, Commerce, Video Generation, and Versioned Builds](<https://devfeed.tech/articles/more-surfaces-same-deal-cars-sensors-commerce-video-and-builds-19423.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/one-codebase-more-surfaces/>)

Author: Shai Almog

Published: 2026-07-03T00:00:00Z

Content type: release

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Open Source](<https://devfeed.tech/topics/open-source.md>), [API](<https://devfeed.tech/topics/api.md>), [Android](<https://devfeed.tech/topics/android.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [api](<https://devfeed.tech/tags/api.md>), [features](<https://devfeed.tech/tags/features.md>), [new-features](<https://devfeed.tech/tags/new-features.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [release](<https://devfeed.tech/tags/release.md>)

### AI overview

This Codename One release expands its open-source core to car dashboards, motion sensors, foldable devices, richer input, video and audio processing, and timed subtitles. It also adds Commerce, Secrets API access, versioned builds, and master builds while keeping paid services optional and separate from purchase processing.

### Source excerpt

This release adds car dashboards, motion sensors, desktop-class input, foldables, Commerce, Secrets, versioned builds, and real video generation while keeping last week's open-source deal intact.

## React Native 0.81 - Android 16 support, faster iOS builds, and more

DevFeed: [React Native 0.81 - Android 16 support, faster iOS builds, and more](<https://devfeed.tech/articles/react-native-0-81-android-16-support-faster-ios-builds-and-more-48129.md>)

Original publisher: [Read original article](<https://reactnative.dev/blog/2025/08/12/react-native-0.81>)

Author: Moti Zilberman; Vitali Zaidman; Gabriel Donadel Dall'Agnol; Christian Falch

Published: 2025-08-12T00:00:00Z

Content type: release

Language: en

Sources: [React Native Blog](<https://devfeed.tech/sources/react-native-blog.md>)

Topics: [React Native](<https://devfeed.tech/topics/react-native.md>), [Android](<https://devfeed.tech/topics/android.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [migration](<https://devfeed.tech/topics/migration.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [builds](<https://devfeed.tech/topics/builds.md>), [deprecated](<https://devfeed.tech/topics/deprecated.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-16](<https://devfeed.tech/tags/android-16.md>), [builds](<https://devfeed.tech/tags/builds.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [ios](<https://devfeed.tech/tags/ios.md>), [large-screen](<https://devfeed.tech/tags/large-screen.md>), [migration](<https://devfeed.tech/tags/migration.md>), [react-native](<https://devfeed.tech/tags/react-native.md>)

### AI overview

React Native 0.81 adds Android 16 support, stability improvements and bug fixes, experimental faster iOS builds using precompilation, and community-maintained JavaScriptCore support. The release also deprecates SafeAreaView and documents migration requirements for edge-to-edge layouts, predictive back handling, large-screen responsiveness, and native binary page sizes.

### Source excerpt

Today we are excited to release React Native 0.81!

## A product manager's guide to adapting Android apps across devices

DevFeed: [A product manager's guide to adapting Android apps across devices](<https://devfeed.tech/articles/a-product-manager-s-guide-to-adapting-android-apps-across-devices-22667.md>)

Original publisher: [Read original article](<https://medium.com/androiddevelopers/a-product-managers-guide-to-adapting-android-apps-across-devices-b2e9b8bfe5f1?source=rss----95b274b437c2---4>)

Author: Android Developers

Published: 2025-06-10T18:06:14Z

Content type: article

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-medium.md>)

Topics: [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [mobile-ui-design](<https://devfeed.tech/topics/mobile-ui-design.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Android](<https://devfeed.tech/topics/android.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [Android XR](<https://devfeed.tech/topics/android-xr.md>), [SDK](<https://devfeed.tech/topics/sdk.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [android](<https://devfeed.tech/tags/android.md>), [android-16](<https://devfeed.tech/tags/android-16.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [chromebooks](<https://devfeed.tech/tags/chromebooks.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [featured](<https://devfeed.tech/tags/featured.md>), [foldables](<https://devfeed.tech/tags/foldables.md>), [google-io-2025](<https://devfeed.tech/tags/google-io-2025.md>), [large-screen](<https://devfeed.tech/tags/large-screen.md>), [large-screen-display](<https://devfeed.tech/tags/large-screen-display.md>), [layout](<https://devfeed.tech/tags/layout.md>), [orientation](<https://devfeed.tech/tags/orientation.md>), [ui](<https://devfeed.tech/tags/ui.md>), [user](<https://devfeed.tech/tags/user.md>), [user-experience](<https://devfeed.tech/tags/user-experience.md>)

### AI overview

Android 16 will ignore orientation and resizability restrictions for apps targeting SDK 36 on large-screen devices with a smallest width of at least 600dp, making adaptive layouts increasingly important. The excerpt says adapting apps can improve large-screen usability, engagement, accessibility, and Play discoverability, while warning that low tablet usage may reflect a poor experience rather than lack of demand. It recommends checking the app on tablets, foldables, Chromebooks, and desktop windowing; fixing basic stretching and navigation issues; then improving core screens incrementally. Suggested steps include supporting portrait and landscape, split-screen resizing, keyboard and pointer input, and layouts such as list-detail or two-pane views. The article notes upfront investment but says shared adaptive designs may reduce the need for separate layouts. These points are from the supplied excerpt.

### Source excerpt

Posted by Fahd Imtiaz, Product Manager, Android Developer Experience This article is also shared on the Android Developers Blog Today, Android is launching a few updates across the platform! This includes the start of Android 16's rollout, with details for both developers and users, a Developer Preview for enhanced Android desktop experiences with connected displays, and updates for Android users across Google apps and more, plus the June Pixel Drop. We're also recapping all the Google I/O updates for Android developers focused on building excellent, adaptive Android apps. With new form factors emerging continually, the Android ecosystem is more dynamic than ever. From phones and foldables to tablets, Chromebooks, TVs, cars, Wear and XR, Android users expect their apps to run seamlessly across an increasingly diverse range of form factors. Yet, many Android apps fall short of these expectations as they are built with UI constraints such as being locked to a single orientation or restricted in resizability. With this in mind, Android 16 introduced API changes for apps targeting SDK level 36 to ignore orientation and resizability restrictions starting with large screen devices, shifting toward a unified model where adaptive apps are the norm. This is the moment to move ahead. Adaptive apps aren't just the future of Android, they're the expectation for your app to stand out across Android form factors. Why you should prioritize adaptive nowSource: internal Google data Prioritizing optimizations to make your app adaptive isn't just about keeping up with the orientation and resizability API changes in Android 16 for apps targeting SDK 36. Adaptive apps unlock tangible benefits across user experience, development efficiency, and market reach. Mobile apps can now reach users on over 500 million active large screen devices: Mobile apps run on foldables, tablets, Chromebooks, and even compatible cars, with minimal changes. Android 16 will introduce significant advancements i

## Now in Android #117 -- Google I/O 2025 Part I

DevFeed: [Now in Android #117 -- Google I/O 2025 Part I](<https://devfeed.tech/articles/now-in-android-117-google-i-o-2025-part-i-22671.md>)

Original publisher: [Read original article](<https://medium.com/androiddevelopers/now-in-android-117-google-i-o-2025-part-i-fd20a09a2299?source=rss----95b274b437c2---4>)

Author: Daniel Galpin

Published: 2025-06-05T17:28:56Z

Content type: news

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-medium.md>)

Topics: [Material Design](<https://devfeed.tech/topics/material-design.md>), [Android](<https://devfeed.tech/topics/android.md>), [Design system](<https://devfeed.tech/topics/design-system.md>), [software-development](<https://devfeed.tech/topics/software-development.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [3D](<https://devfeed.tech/topics/3d.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [adaptive](<https://devfeed.tech/tags/adaptive.md>), [ai](<https://devfeed.tech/tags/ai.md>), [android](<https://devfeed.tech/tags/android.md>), [android-16](<https://devfeed.tech/tags/android-16.md>), [android-xr](<https://devfeed.tech/tags/android-xr.md>), [animations](<https://devfeed.tech/tags/animations.md>), [cars](<https://devfeed.tech/tags/cars.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [colors](<https://devfeed.tech/tags/colors.md>), [design](<https://devfeed.tech/tags/design.md>), [design-patterns](<https://devfeed.tech/tags/design-patterns.md>), [development](<https://devfeed.tech/tags/development.md>), [displays](<https://devfeed.tech/tags/displays.md>), [featured](<https://devfeed.tech/tags/featured.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [google-i-o](<https://devfeed.tech/tags/google-i-o.md>), [google-io-2025](<https://devfeed.tech/tags/google-io-2025.md>), [guidelines](<https://devfeed.tech/tags/guidelines.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [laptops](<https://devfeed.tech/tags/laptops.md>), [material](<https://devfeed.tech/tags/material.md>), [now-in-android](<https://devfeed.tech/tags/now-in-android.md>)

### AI overview

Google I/O 2025 introduced Material 3 Expressive, with a new motion physics system, typography for variable and static fonts, morphing shapes, more colors, and expanded configuration options across 15 new or updated components. The Q3 Android 16 beta includes much of this visual polish and is available for supported Pixel devices. Google also released the Wear OS 6 developer preview, which lets developers test apps in its emulator. The excerpt additionally points to design guidance for accessibility and multiple Android form factors, but does not provide the rest of the post's coverage.

### Source excerpt

Now in Android #117 -- Google I/O 2025 Part IDesign, Watches, Cars, Tablets, Adaptive Apps, Android XR, Gemini, and Android 16 Welcome to part one of a special two-part Google I/O 2025 edition of Now in Android. This first post will cover a bunch of changes related to the latest evolution of Material Design, watches, cars, tablets, laptops, and connected displays, the latest in adaptive app development, XR development, how to take advantage of on-device and cloud based AI, and Android 16. https://medium.com/media/f4779f9096112bf2cfff21aec7eeb199/hrefhttps://medium.com/media/d23b17afda66e01541bb4c84ecea4974/href Most of the content of this post is available in the form of a video or podcast, so feel free to watch or listen rather than read on. (Or do all three to help you remember! There won't be a quiz.) The Android Show: I/O Edition -- what Android devs need to know! 🤖 We began the I/O season with a special edition of The Android Show, where we introduced the latest evolution of Material Design, Material 3 Expressive. https://medium.com/media/815112dc9a5b3a849cced5343837f4e6/href The Android Show: I/O Edition - what Android devs need to know! https://medium.com/media/906cc031e2cbb814b2a4964db156a2cc/href Material 3 Expressive adds a new motion physics system, new type styles for variable and static fonts, an expanded shape library with morphing animations, and an expanded range of colors. Fifteen new or updated components now feature more configuration capabilities, shape options, emphasized text, and other expressive updates. The Material team has a post where you can read all about it, including design tactics. M3 Expressive: Engaging UX Design At I/O Build next-level UX with Material 3 Expressive covered how to use the new expressive design patterns; breaking down the research, explaining new guidelines, and including new design files + code. https://medium.com/media/4ce31edc8b396f71acc6192d1ac6160f/href The first beta of the Q3 Android 16 update contains much of

## The Accessibility Problems Caused by Incorrect Text Truncation in Android Apps

DevFeed: [The Accessibility Problems Caused by Incorrect Text Truncation in Android Apps](<https://devfeed.tech/articles/the-problem-of-trun-38505.md>)

Original publisher: [Read original article](<https://eevis.codes/blog/2025-04-26/the-problem-of-trun/>)

Author: Eevis Panula

Published: 2025-04-26T07:31:38.151000Z

Content type: article

Language: en

Sources: [Eevis Blog](<https://devfeed.tech/sources/eevis-blog.md>)

Topics: [Web Accessibility (a11y)](<https://devfeed.tech/topics/web-accessibility.md>), [Android](<https://devfeed.tech/topics/android.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Font](<https://devfeed.tech/topics/font.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>)

Tags: [accessibility](<https://devfeed.tech/tags/accessibility.md>), [android](<https://devfeed.tech/tags/android.md>), [cognitive-load](<https://devfeed.tech/tags/cognitive-load.md>), [text](<https://devfeed.tech/tags/text.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

The article examines how Android apps truncate text with ellipses when it does not fit, often without a way to expand the hidden text. It argues that this can prevent users, especially those using larger font sizes or smaller displays, from accessing important labels and context.

### Source excerpt

Imagine that you're in an unfamiliar location. You can see a signpost, but it's old, and most of the letters of the words have been scratched off. The names in the signs all seem similar, given the couple of letters you can see. And you need to get somewhere, but the signpost is not helping at all. You're lost. As the title gives away, I'm writing about something starting with "trun". I could be writing about the problems of trunkfish. They seem a bit lost, so the topic could be that. Or I could be writing about truncheons and the issues caused by them. But no, this time, it's about truncation, specifically when truncation has not been implemented correctly. Texts in applications are like those signs in a signpost. They most often lead to somewhere, give some instructions or necessary information, or are otherwise relevant. Texts wouldn't be in the app if they weren't meaningful. Problem of Truncation Done Wrong We have this widely spread pattern on Android, where the words are truncated with an ellipsis if they don't fit the container, without any way to expand the missing part of the text. For example, when you have a font size that is big enough, app names are truncated. The following image shows an example from accessibility settings and font size selection in Pixel: And okay, one could argue that if you install an app, you should be familiar with it and be able to recognize it even when you just get three letters from the name with the icon. But it's not that straightforward - what if it's an app you've used a year ago? Or what if you have memory issues due to something permanent or due to stress? Or any of the number of reasons why recognizing the app only with a partial name and an icon is not possible - let alone the cognitive load it creates. And it's not just the app icons; it's everywhere in the apps: The bottom navigation, buttons, links, titles... All these are places where the user would need the context of "What will happen if I press this item?" or "

## A Synchronized Start for Linked Devices

DevFeed: [A Synchronized Start for Linked Devices](<https://devfeed.tech/articles/a-synchronized-start-for-linked-devices-1726.md>)

Original publisher: [Read original article](<https://signal.org/blog/a-synchronized-start-for-linked-devices/>)

Published: 2025-01-27T00:00:00Z

Content type: article

Language: en

Sources: [Signal](<https://devfeed.tech/sources/signal-blog.md>)

Topics: [End-to-End Encryption](<https://devfeed.tech/topics/end-to-end-encryption.md>), [Android](<https://devfeed.tech/topics/android.md>), [iOS](<https://devfeed.tech/topics/ios.md>), [Encryption](<https://devfeed.tech/topics/encryption.md>), [App](<https://devfeed.tech/topics/app.md>), [data](<https://devfeed.tech/topics/data.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [communication](<https://devfeed.tech/tags/communication.md>), [devices](<https://devfeed.tech/tags/devices.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [feature](<https://devfeed.tech/tags/feature.md>), [ios](<https://devfeed.tech/tags/ios.md>), [media](<https://devfeed.tech/tags/media.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [production](<https://devfeed.tech/tags/production.md>), [releases](<https://devfeed.tech/tags/releases.md>), [video](<https://devfeed.tech/tags/video.md>)

### AI overview

Signal describes synchronized message and media transfer for linked Desktop and iPad devices. The feature preserves end-to-end encryption and privacy while allowing users to transfer chats and the last 45 days of media to a new linked device.

### Source excerpt

With Signal on Desktop and iPad, you can link your primary Android or iOS account with another device, letting you check and respond to messages in both places or conduct video meetings and calls from the comfort of a bigger screen. Signal's upcoming beta releases will also introduce the option to transfer your messages and media when you link your primary Signal device to a new Desktop or iPad. Instead of starting fresh, and having only new messages show up, you can choose to bring your chats and your last 45 days of media with you. Or, you can choose not to. Read more...

## Adaptive Layouts in Compose Multiplatform - Kevin Schildhorn

DevFeed: [Adaptive Layouts in Compose Multiplatform - Kevin Schildhorn](<https://devfeed.tech/articles/adaptive-layouts-in-compose-multiplatform-kevin-schildhorn-38155.md>)

Original publisher: [Read original article](<https://touchlab.co/adaptive-layouts-cmp>)

Published: 2024-12-12T00:00:00Z

Content type: tutorial

Language: en

Sources: [Touchlab](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [compose-multiplatform](<https://devfeed.tech/topics/compose-multiplatform.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [multiplatform](<https://devfeed.tech/topics/multiplatform.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [android](<https://devfeed.tech/tags/android.md>), [compose](<https://devfeed.tech/tags/compose.md>), [compose-multiplatform](<https://devfeed.tech/tags/compose-multiplatform.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [ios](<https://devfeed.tech/tags/ios.md>), [kotlin-multiplatform](<https://devfeed.tech/tags/kotlin-multiplatform.md>), [layout](<https://devfeed.tech/tags/layout.md>), [multiplatform](<https://devfeed.tech/tags/multiplatform.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [screen](<https://devfeed.tech/tags/screen.md>), [ui](<https://devfeed.tech/tags/ui.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

The article explains adaptive layouts in Compose Multiplatform, including navigation and canonical list-detail layouts. It describes how these layouts adapt interfaces across Android, iOS, Desktop, and Web, and compares them with the AndroidX API.

### Source excerpt

Adaptive Layouts is a way of adapting your UI to fit different display sizes on Android, and it's now available for Compose Multiplatform.

## Dynamic Layouts with ContextualFlowRow and ContextualFlowColumn

DevFeed: [Dynamic Layouts with ContextualFlowRow and ContextualFlowColumn](<https://devfeed.tech/articles/dynamic-layouts-with-contextualflowrow-and-contextualflowcolumn-25092.md>)

Original publisher: [Read original article](<https://dladukedev.com/articles/037_dynamic_rows_with_contextual_flow_row/>)

Published: 2024-06-06T00:00:00Z

Content type: tutorial

Language: en

Sources: [Donovan LaDuke - Developer](<https://devfeed.tech/sources/donovan-laduke-developer.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [compose](<https://devfeed.tech/tags/compose.md>), [devices](<https://devfeed.tech/tags/devices.md>), [examples](<https://devfeed.tech/tags/examples.md>), [google](<https://devfeed.tech/tags/google.md>), [google-i-o](<https://devfeed.tech/tags/google-i-o.md>), [layout](<https://devfeed.tech/tags/layout.md>), [screen](<https://devfeed.tech/tags/screen.md>)

### AI overview

A tutorial on using Compose's ContextualFlowRow and ContextualFlowColumn for dynamic row and column layouts. It explains how these components support fixed row or column counts, overflow policies, lazy layout, and adaptation to large-screen devices such as tablets and foldables.

### Source excerpt

Check out ContextualFlowRow and ContextualFlowColumn a new way to layout items in a row or column with a dynamic number of items that accounts for dynamic screen sizes automagically

## Crash course on the Android UI layer | Part 2

DevFeed: [Crash course on the Android UI layer | Part 2](<https://devfeed.tech/articles/crash-course-on-the-android-ui-layer-part-2-22599.md>)

Original publisher: [Read original article](<https://medium.com/bumble-tech/crash-course-on-the-android-ui-layer-part-2-2335171467e0?source=rss----6353b5325b1a---4>)

Author: Manuel Vivo

Published: 2023-12-19T15:58:45Z

Content type: article

Language: en

Sources: [Bumble Tech](<https://devfeed.tech/sources/bumble-tech.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [business logic](<https://devfeed.tech/topics/business-logic.md>), [Stateful](<https://devfeed.tech/topics/stateful.md>), [Large Screen](<https://devfeed.tech/topics/large-screen.md>), [parcelable](<https://devfeed.tech/topics/parcelable.md>)

Tags: [2023](<https://devfeed.tech/tags/2023.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [apis](<https://devfeed.tech/tags/apis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [blog](<https://devfeed.tech/tags/blog.md>), [blog-post](<https://devfeed.tech/tags/blog-post.md>), [business-logic](<https://devfeed.tech/tags/business-logic.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [decision-trees](<https://devfeed.tech/tags/decision-trees.md>), [droidcon](<https://devfeed.tech/tags/droidcon.md>), [format](<https://devfeed.tech/tags/format.md>), [logic](<https://devfeed.tech/tags/logic.md>), [save](<https://devfeed.tech/tags/save.md>), [saving](<https://devfeed.tech/tags/saving.md>), [series](<https://devfeed.tech/tags/series.md>), [state](<https://devfeed.tech/tags/state.md>), [talk](<https://devfeed.tech/tags/talk.md>), [types](<https://devfeed.tech/tags/types.md>), [ui](<https://devfeed.tech/tags/ui.md>), [video](<https://devfeed.tech/tags/video.md>), [viewmodel](<https://devfeed.tech/tags/viewmodel.md>)

### AI overview

State placement depends on what uses it and how long it must survive. Keep business logic and screen UI state in a screen-level state holder, usually `androidX.ViewModel`, which survives configuration changes and can keep `viewModelScope` work running while it remains in memory. Keep simple UI logic in the UI; move growing or reusable UI logic into a plain state holder scoped to the UI, which may hold lifecycle references. Hoist state to the lowest common ancestor that reads or writes it, except state needed by business logic, which belongs in the screen-level holder. SavedState APIs preserve transient UI state through configuration changes and system-initiated process death; persistent storage is for application data and can survive app dismissal. The excerpt also cautions that long-running ViewModel work may suit WorkManager better and testing `viewModelScope` requires replacing `MainDispatcher`.

### Source excerpt

Crash Course on the Android UI Layer | Part 2State Holders and Saving State This blog post series aims to summarise the Android Developer guidance on the UI layer. We'll explore all the entities involved in it, understand the role each part plays, and discuss best practices. By the end of this series, you will have a general understanding of what happens on the UI layer and how to best handle state and logic within it, the various APIs involved, and how to use them. Additionally, we'll provide decision trees to assist you when you're in doubt. In part 1, we covered the UI and the UI state. You should already know the different entities present on the UI layer, and how to think about the UI and UI state effectively. Crash course on the Android UI layer | Part 1 Now it's time for Part 2! We'll cover state holders and other UI layer-related topics such as where to hoist state and save UI state on Android. If you prefer to consume this content in video format, check out the talk I delivered at Droidcon London 2023: Peeling Back the Layers: Unmasking the UI-nknown! State holders State holders simplify the UI by handling logic and/or exposing UI state. In this section, we'll see how to implement state holders and the implementation details to consider. To determine the implementation details, we first need to identify the types of logic commonly found in an Android app. Types of logic We have already discussed that business logic involves implementing the product requirements that specify how application data is created, stored, and modified. When business logic is present in the UI layer, it's recommended to manage this logic at the screen level. We'll see more of this later. Another type of logic is the UI logic. UI logic determines how to display state changes on the screen. While business logic dictates what to do with data, UI logic determines how to visually display it. The UI logic is dependent on the UI configuration. For instance, in a typical app, displaying a d

[Next page](<https://devfeed.tech/topics/large-screen.md?cursor=WyIyMDIzLTEyLTE5VDE1OjU4OjQ1KzAwOjAwIiwgIjlkODQ2YzFlLTMwYTktNDZlZi04Y2JlLTE5NjhmYjU5NGUyNCJd>)