Beyond the smartphone: How JioHotstar optimized its UX for foldables and tablets

Posted by Prateek Batra, Developer Relations Engineer, Android Adaptive Apps



Beyond Phones: How JioHotstar Built an Adaptive UX

JioHotstar is a leading streaming platform in India, serving a user base exceeding 400 million. With a vast content library encompassing over 330,000 hours of video on demand (VOD) and real-time delivery of major sporting events, the platform operates at a massive scale.

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.




To accomplish this, also using the Material 3 Adaptive library, the same currentWindowAdaptiveInfo() can be used to query for the tabletop mode. Once the device is held in tabletop mode, a change of layout to match the top and bottom half of the posture can be done with a column to place the player in the top half and the controllers in the bottom half:

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

Better suggestions for meeting times with Gemini in Google Calendar

Users have a new way to get suggested times when creating a meeting in Calendar. Gemini in Google Calendar helps you identify the best times to meet for all attendees if you have access to their calendar.  When creating an event, click Suggested times and let Gemini analyze attendee availability, working hours, and potential conflicts.  Then, you can quickly review and select the most suitable time slot. 

For meeting organizers, if multiple attendees decline your invite, we’re also making it easier to reschedule your meeting. When you open the event, you’ll see a banner with a time when everyone is available, letting you update the invite with the click of a button.


Suggested meeting times in Google Calendar

Getting started

Rollout pace

Availability

  • Business Standard and Plus
  • Enterprise Standard and Plus
  • Google AI Pro for Education add-on

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. 


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. 


New admin controls for "Take notes for me" sharing settings in Google Meet

We are introducing two new admin settings to give you more control over how meeting notes generated by "Take notes for me" are shared within your organization. These settings allow you to:

  • Set a default sharing value: Choose who should receive access to the Take notes for me document and the recap email by default.
  • Restrict host overrides: Decide whether meeting hosts and co-hosts have the ability to change these sharing settings during a meeting.
Previously, sharing settings for Take notes for me were primarily managed by meeting hosts in-call. These updates allow administrators to set defaults and restrictions based on company policies.

Getting started

Rollout pace

Availability

  • Business Standard and Plus
  • Enterprise Standard and Plus
  • Frontline Plus
  • Google AI Pro for Education

Resources

Campaign Manager 360 API v4 Sunset Reminder

Campaign Manager 360 API v4 will be sunset on February 26, 2026. Starting on this date, all v4 API requests will begin to fail. If you’re still using this version, we strongly encourage you to migrate to v5 as soon as possible to avoid service interruptions.

See the migration guide for details on how to upgrade. In most cases, you will just need to upgrade to the latest version of your preferred client library. We also recommend reviewing the release notes for important changes that may affect your implementation.

If you have questions, please contact Campaign Manager 360 API support.