27 Jan 2026
TalkAndroid
This secret settings menu transforms your driving experience—how to unlock it today
Think Android Auto is draining your phone like a vampire at a blood drive? Or maybe the display…
27 Jan 2026 7:30am GMT
Boba Story Lid Recipes – 2026
Look no further for all the latest Boba Story Lid Recipes. They are all right here!
27 Jan 2026 3:38am GMT
Dice Dreams Free Rolls – Updated Daily
Get the latest Dice Dreams free rolls links, updated daily! Complete with a guide on how to redeem the links.
27 Jan 2026 3:38am GMT
Android Developers Blog
Beyond the smartphone: How JioHotstar optimized its UX for foldables and tablets
Posted by Prateek Batra, Developer Relations Engineer, Android Adaptive Apps
To help ensure a premium experience for its vast audience, JioHotstar elevated the viewing experience by optimizing their app for foldables and tablets. They accomplished this by following Google's adaptive app guidance and utilizing resources like samples, codelabs, cookbooks, and documentation to help create a consistently seamless and engaging experience across all display sizes.
JioHotstar's large screen challenge
JioHotstar offered an excellent user experience on standard phones and the team wanted to take advantage of new form factors. To start, the team evaluated their app against the large screen app quality guidelines to understand the optimizations required to extend their user experience to foldables and tablets. To achieve Tier 1 large screen app status, the team implemented two strategic updates to adapt the app across various form factors and differentiate on foldables. By addressing the unique challenges posed by foldable and tablet devices, JioHotstar aims to deliver a high-quality and immersive experience across all display sizes and aspect ratios.
What they needed to do
JioHotstar's user interface, designed primarily for standard phone displays, encountered challenges in adapting hero image aspect ratios, menus, and show screens to the diverse screen sizes and resolutions of other form factors. This often led to image cropping, letterboxing, low resolution, and unutilized space, particularly in landscape mode. To help fully leverage the capabilities of tablets and foldables and deliver an optimized user experience across these device types, JioHotstar focused on refining the UI to ensure optimal layout flexibility, image rendering, and navigation across a wider range of devices.
What they did
For a better viewing experience on large screens, JioHotstar took the initiative to enhance its app by incorporating WindowSizeClass and creating optimized layouts for compact, medium and extended widths. This allowed the app to adapt its user interface to various screen dimensions and aspect ratios, ensuring a consistent and visually appealing UI across different devices.
JioHotstar followed this pattern using Material 3 Adaptive library to know how much space the app has available. First invoking the currentWindowAdaptiveInfo() function, then using new layouts accordingly for the three window size classes:
val sizeClass = currentWindowAdaptiveInfo().windowSizeClass if(sizeClass.isWidthAtLeastBreakpoint(WIDTH_DP_EXPANDED_LOWER_BOUND)) { showExpandedLayout() } else if(sizeClass.isHeightAtLeastBreakpoint(WIDTH_DP_MEDIUM_LOWER_BOUND)) { showMediumLayout() } else { showCompactLayout() }
The breakpoints are in order, from the biggest to the smallest, as internally the API checks for with a greater or equal then, so any width that is at least greater or equal then EXPANDED will always be greater than MEDIUM.
JioHotstar is able to provide the premium experience unique to foldable devices: Tabletop Mode. This feature conveniently relocates the video player to the top half of the screen and the video controls to the bottom half when a foldable device is partially folded for a handsfree experience.
val isTabletTop = currentWindowAdaptiveInfo().windowPosture.isTabletop
if(isTabletopMode) {
Column {
Player(Modifier.weight(1f))
Controls(Modifier.weight(1f))
}
} else {
usualPlayerLayout()
}
JioHotstar is now meeting the Large Screen app quality guidelines for Tier 1. The team leveraged adaptive app guidance, utilizing samples, codelabs, cookbooks, and documentation to incorporate these recommendations.
To further improve the user experience, JioHotstar increased touch target sizes, to the recommended 48dp, on video discovery pages, ensuring accessibility across large screen devices. Their video details page is now adaptive, adjusting to screen sizes and orientations. They moved beyond simple image scaling, instead leveraging window size classes to detect window size and density in real time and load the most appropriate hero image for each form factor, helping to enhance visual fidelity. Navigation was also improved, with layouts adapting to suit different screen sizes.
Now users can view their favorite content from JioHotstar on large screens devices with an improved and highly optimized viewing experience.
Achieving Tier 1 large screen app status with Google is a milestone that reflects the strength of our shared vision. At JioHotstar, we have always believed that optimizing for large screen devices goes beyond adaptability, it's about elevating the viewing experience for audiences who are rapidly embracing foldables, tablets, and connected TVs.
Leveraging Google's Jetpack libraries and guides allowed us to combine our insights on content consumption with their expertise in platform innovation. This collaboration allowed both teams to push boundaries, address gaps, and co-create a seamless, immersive experience across every screen size.
Together, we're proud to bring this enhanced experience to millions of users and to set new benchmarks in how India and the world experience streaming.
Sonu Sanjeev
Senior Software Development Engineer
27 Jan 2026 3:30am GMT
26 Jan 2026
The Official Google Blog
How animators and AI researchers made ‘Dear Upstairs Neighbors’
Today, our animated short film, "Dear Upstairs Neighbors," previews at the Sundance Film Festival.
26 Jan 2026 6:00pm GMT
We’re announcing the 12 recipients of our AI for Science fund
A look at the 12 recipients of the first AI for Science fund.
26 Jan 2026 5:00pm GMT
Android Developers Blog
Trade-in mode on Android 16+
Supporting Longevity through Faster Diagnostics
Posted by Rachel S, Android Product Manager
Trade-in mode: faster assessment of a factory-reset phone or tablet, bypassing setup wizard, a new feature on Android 16 and above.
Supporting device longevity
Android is committed to making devices last longer. With device longevity comes device circularity: phones and tablets traded-in and resold. GSMA reported that secondhand phones have around 80-90% lower carbon emissions than new phones. The secondhand device market has grown substantially both in volume and value, a trend projected to continue.
Android 16 and above offers an easy way to access device information on any factory reset phone or tablet via the new tradeinmode parameter, accessed via adb commands. This means you can view quality indicators of a phone or tablet, skipping each setup wizard step. Simply connect a phone or tablet with adb, and use tradeinmode commands to get information about the device.
Trade-in mode: What took minutes, now takes seconds
Faster trade-in processing - By bypassing setup wizard, trade-in mode improves device trade ins. The mode enables immediate access to understand the 'health' of a device, helping everyone along the secondhand value chain check the quality of devices that are wiped. We've already seen significant increases in processing secondhand Android devices!
Secure evaluation - To ensure the device information is only accessed in secure situations, the device must 1) be factory reset, 2) not have cellular service, 3) not have connectivity or a connected account, and 4) be running a non-debuggable build.
Get device health information with one command - You can view all the below device information with adb command from your workstation adb shell tradeinmode getstatus, skipping setup wizard:
-
Device information
-
-
Device IMEI(s)
-
Device serial number
-
Brand
-
Model
-
Manufacturer
-
Device model, e.g., Pixel 9
-
Device brand, e.g., Google
-
Device manufacturer, e.g., Google
-
Device name, e.g., tokay
-
API level to ensure correct OS version, e.g., launch_level : 34
-
-
Battery heath
-
-
Cycle count
-
Health
-
State, e.g., unknown, good, overheat, dead, over_voltage, unspecified_failure, cold, fair, not_available, inconsistent
-
Battery manufacturing date
-
Date first used
-
Serial number (to help provide indication of genuine parts, if OEM supported)
-
Part status, e.g., replaced, original, unsupported
-
-
Storage
-
-
Useful lifetime remaining
-
Total capacity
-
-
Screen Part status, e.g., replaced, original, unsupported
-
Foldables (number of times devices has been folded and total fold lifespan)
-
Moisture intrusion
-
UICCS information i.e., Indication if there is an e-SIM or removable SIM and the microchip ID for the SIM slot
-
Camera count and location, e.g., 3 cameras on front and 2 on back
-
Lock detection for select device locks
-
And the list keeps growing! Stay up to date here.
Run your own tests - Trade-in mode enables you to run your own diagnostic commands or applications by entering the evaluation flow using tradeinmode evaluate. The device will automatically factory reset on reboot after evaluation mode to ensure nothing remains on the device.
Ensure the device is running an approved build - Further, when connected to the internet, with a single command tradeinmode getstatus --challenge CHALLENGE you can test the device's operating system (OS) authenticity, to be sure the device is running a trusted build. If the build passes the test, you can be sure the diagnostics results are coming from a trusted OS.
There's more - You can use commands to factory reset, power off, reboot, reboot directly into trade-in mode, check if trade-in mode is active, revert to the previous mode, and pause tests until system services are ready.
Want to try it? Learn more about the developer steps and commands.
26 Jan 2026 5:00pm GMT
22 Jan 2026
The Official Google Blog
See the newest product features in January’s Demand Gen Drop.
Learn more about the enhancements Demand Gen is launching, just in time for the new year.
22 Jan 2026 5:00pm GMT
21 Jan 2026
Android Developers Blog
Ready to review some changes but not others? Try using Play Console’s new Save for later feature

Posted by Georgia Doyle, Senior UX Writer and Content Designer, and Kanu Tibrewal, Software Engineer
We've launched a new Save for later feature on Google Play Console's Publishing overview to give you more control over when you send changes for review.
In the past, changes to your app were bundled together before being sent for review. This presented challenges if you needed to reprioritize changes, or if the changes were no longer relevant. For example, updates to your test tracks grouped with marketing changes that need to be rescheduled. This lack of flexibility meant that if some changes were ready for review but not others, you could end up delaying urgent fixes, or publishing changes that you weren't quite ready to make.
Now, you have the ability to hold back the changes you're not ready to have reviewed.
How it works
In the 'Changes not yet sent for review' section of the Publishing overview page, select 'Save for later' on the groups of changes that you don't want to include in your next review. You can view and edit the list of saved changes, and return them to the Publishing overview if you change your mind. Once the review has started, your saved changes will be added back to 'Changes not yet sent for review'.
- If issues are isolated to an individual track, we'll show you an error beside that change, so you know what to save for later in order to proceed to review with your other changes.
- If you have issues that affect your whole app, for example, App content issues, Save for later will be unavailable and you will need to fix them before you can send any changes for review.
Greater flexibility in your workflows
Our goal for Save for later is to give you greater flexibility over your release schedule. With this feature you can manage what changes you send for review, and address issues affecting individual tracks without holding up ready-to-release changes, so you can iterate faster and minimize the impact of rejections on your release timeline.
So, what's next?
We're excited to see how Save for later helps you to streamline your release process and bring your app innovations to users even faster.
21 Jan 2026 5:00pm GMT



