Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
150690 stories
·
33 followers

Media3 1.10 is out

1 Share

Posted by Andrew Lewis, Software Engineer



Media3 1.10 is out!
Media3 1.10 includes new features, bug fixes and feature improvements, including Material3-based playback widgets, expanded format support in ExoPlayer and improved speed adjustment when exporting media with Transformer. Read on to find out more, and check out the full release notes for a comprehensive list of changes.

Playback UI and Compose

We are continuing to expand the media3-ui-compose-material3 module to help you build Compose UIs for playback.

We've added a new Player Composable that combines a ContentFrame with customizable playback controls, giving you an out-of-the-box player widget with a modern UI.

This release also adds a ProgressSlider Composable for displaying player progress and performing seeks using dragging and tapping gestures. For playback speed management, a new PlaybackSpeedControl is available in the base media3-ui-compose module, alongside a styled PlaybackSpeedToggleButton in the Material 3 module.

We'll continue working on new additions like track selection utils, subtitle support and more customization options in the upcoming Media3 releases. We're eager to hear your feedback so please share your thoughts on the project issue tracker.

 Player Composable in the Media3 Compose demo app

Playback feature enhancements

Media3 1.10 includes a variety of additions and improvements across the playback modules:
  • Format support: ExoPlayer now supports extracting Dolby Vision Profile 10 and Versatile Video Coding (VVC) tracks in MP4 containers, and we've introduced MPEG-H UI manager support in the decoder_mpeghextension. The IAMF extension now seamlessly supports binaural output, either through the decoder viaiamf_tools or through the Android OS Spatializer, with new logic to match the output layout of the speakers.

  • Ad playback: Improvements to reliability, improved HLS interstitial support forX-PLAYOUT-LIMIT  and X-SNAP, and with the latest IMA SDK dependency you can control whether ad click-through URLs open in custom tabs with setEnableCustomTabs.

  • HLS: ExoPlayer now allows location fallback upon encountering load errors if redundant streams from different locations are available.
  • Session: MediaSessionService now extends LifecycleService, allowing apps to access the lifecycle scoping of the service.

One of our key focus areas this year is on playback efficiency and performance. Media3 1.10 includes experimental support for scheduling the core playback loop in a more efficient way. You can try this out by enabling experimentalSetDynamicSchedulingEnabled() via the ExoPlayer.Builder. We plan to make further improvements in future releases so stay tuned!

Media editing and Transformer

For developers building media editing experiences, we've made speed adjustments more robust. EditedMediaItem.Builder.setFrameRate()can now set a maximum output frame rate for video. This is particularly helpful for controlling output size and maintaining performance when increasing media speed with setSpeed().

New modules for frame extraction and applying Lottie effects

In this release we've split some functionality into new modules to reduce the scope of some dependencies:

  • FrameExtractor has been removed from the main media3-inspector module, so please migrate your code to use the new media3-inspector-framemodule and update your imports toandroidx.media3.inspector.frame.FrameExtractor.

  • We have also moved theLottieOverlayeffect to a separate media3-effect-lottie module. As a reminder, this gives you a straightforward way to apply vector-based Lottie animations directly to video frames.

Please get in touch via the issue tracker if you run into any bugs, or if you have questions or feature requests. We look forward to hearing from you!

Read the whole story
alvinashcraft
12 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Android developer verification: Rolling out to all developers on Play Console and Android Developer Console

1 Share

Posted by Matthew Forsythe, Director Product Management, Android App Safety

Android is for everyone. It’s built on a commitment to an open and safe platform. Users should feel confident installing apps, no matter where they get them from. However, our recent analysis found over 90 times more malware from sideloaded sources than on Google Play. So as an extra layer of security, we are rolling out Android developer verification to help prevent malicious actors from hiding behind anonymity to repeatedly spread harm. Over the past several months, we’ve worked closely with the community to improve the design so we account for the many ways people use Android to balance openness with safety.

Start your verification today

Today, we’re starting to roll out Android developer verification to all developers in both the new Android Developer Console and Play Console. This allows you to complete your verification and register your apps before user-facing changes begin later this year.

  • If you only distribute apps outside of Google Play, you can create an account in Android Developer Console today.
  • If you're on Google Play, check your Play Console account for updates over the next few weeks. If you’ve already verified your identity here, then you’re likely already set.

Most of your users’ download experience will not change at all

While verification tools are rolling out now, the experience for users downloading your apps will not change until later this year. The user side protections will first go live in Brazil, Indonesia, Singapore, and Thailand this September, before expanding globally in 2027. We’ve shared this timeline early to ensure you have ample time to complete your verification.

Following this deadline, for the vast majority of users, the experience of installing apps will stay exactly the same. It’s only when a user tries to install an unregistered app that they’ll require ADB or advanced flow, helping us keep the broader community safe while preserving the flexibility for our power users.

Developers can still choose where to distribute their apps. Most users’ download experience will not change

Tailoring the verification experience to your feedback

To balance the need for safety with our commitment to openness, we’ve improved the verification experience based on your feedback. We’ve streamlined the developer experience to be more integrated with existing workflows and maintained choice for power users.

  • For Android Studio developers: In the next two months, you’ll see your app's registration status right in Android Studio when you generate a signed App Bundle or APK.

You’ll see your app's registration status in Android Studio when you generate a signed App Bundle or APK.

  • For Play developers: If you've completed Play Console's developer verification requirements, your identity is already verified and we'll automatically register eligible Play apps for you. In the rare case that we are unable to register your apps for you, you will need to follow the manual app claim process. Over the next couple of weeks, more details will be provided in the Play Console and through email. Also, you’ll be able to register apps you distribute outside of Play in the Play Console too.

The Android developer verification page in your Play Console will show the registration status for each of your apps.

  • For students and hobbyists: To keep Android accessible to everyone, we're building a free, no government ID required, limited distribution account so you can share your work with up to 20 devices. You only need an email account to get started. Sign up for early access. We’ll send invites in June.
  • For power users: We are maintaining the choice to install apps from any source. You can use the new advanced flow for sideloading unregistered apps or continue using ADB. This maintains choice while protecting vulnerable users.

What’s next?

We’re rolling this out carefully and working closely with developers, users, and our partners. In April, we’ll introduce Android Developer Verifier, a new Google system service that will be used to check if an app is registered to a verified developer.

  • April 2026: Users will start to see Android Developer Verifier in their Google Systems services settings.
  • June 2026: Early access: Limited distribution accounts for students and hobbyists.
  • August 2026: 
  • September 30, 2026: Apps must be registered by verified developers in order to be installed and updated on certified Android devices in Brazil, Indonesia, Singapore, and Thailand. Unregistered apps can be sideloaded with ADB or advanced flow.
  • 2027 and beyond: We will roll out this requirement globally.

We’re committed to an Android that is both open and safe. Check out our developer guides to get started today.

Read the whole story
alvinashcraft
23 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Get ready with the latest beta releases

1 Share

The beta versions of iOS 26.5, iPadOS 26.5, macOS 26.5, tvOS 26.5, visionOS 26.5, and watchOS 26.5 are now available. Get your apps ready by confirming they work as expected on these releases. And make sure to build and test with Xcode 26.5 beta to take advantage of the advancements in the latest SDKs.

View downloads and release notes

Learn about testing a beta OS

Learn about sending feedback

Read the whole story
alvinashcraft
34 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Deploy JavaScript apps

1 Share
Learn the main production deployment models for Vite and JavaScript frontends in Aspire.
Read the whole story
alvinashcraft
56 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Announcing Windows 11 Insider Preview Build for Canary Channel 29558.1000

1 Share
Hello Windows Insiders, today we’re releasing Windows Insider Preview Build 29558.1000 to the Windows 11 Insider Canary Channel on the optional 29500 build series.

What’s new in Canary Build 29558.1000

Changes and Improvements gradually being rolled out with toggle on*

  • This update includes platform changes in moving to a new active development build.

[Command Line (Console Host) Improvements]

The Windows Console is part of the open-source Windows Terminal project, receiving updates from its open-source community. With this release, we are bringing all the changes from the open-source project back into Windows. Most of these updates come from Windows Insiders and community contributors, whose names can be found in the Windows Terminal blog posts on the Windows Command Line Blog. We are bringing these updates to Windows:
  • Optional new Atlas/Direct3D rendering path (UseDx): available behind a registry key (HKCU\Console, DWORD UseDx=1). (GitHub #19848)
  • Regular Expression search: the Find dialog now supports regular expressions. (GitHub #17316)
  • Bold font rendering: the original rendering engine now supports bold fonts. (GitHub #19441)
  • Paste reliability improvement: resolves a longstanding issue where some pasted characters could be dropped when the output code page couldn’t represent them. (GitHub #19511)
  • Accessibility improvements: rewritten legacy MSAA integration and parts of UI Automation support. (GitHub #19344)
  • Snap-on-input behavior: now only enabled by default when VT processing is enabled.
  • More reliable snap on input/output in WSL and PowerShell. (GitHub #19247, #17453)
  • Clipboard enhancements: supports OSC 52 (Manipulate Selection Data) for writing selection data to the clipboard. (GitHub #18949)
  • Graphical content: adds support for Sixel-based images.
  • Alt + Numpad + clipboard text fix: avoids mistranslating Codepage 936 text when generating Alt + Numpad events for clipboard content. (GitHub #17635)
  • Performance: scrolling text performance improvements (up to ~10x in some scenarios). (GitHub #16333)
  • Rectangular selection: fixes rectangular copy via Edit > Mark. (GitHub #16197)
What you’ll see: [caption id="attachment_178835" align="alignnone" width="1350"]The Windows Console can now display inline images, allowing tools like WinGet, for example, to display application icons. The Windows Console can now display inline images, allowing tools like WinGet, for example, to display application icons.[/caption]
  • We have also changed how the pop-up dialogs look inside the console to improve their compatibility with screen readers, assistive technologies, and other terminal emulators. This includes the F7 history window as well as the F2 and F4 line editing windows.
[caption id="attachment_178834" align="alignnone" width="1350"]New “pop-up” history window view. New “pop-up” history window view.[/caption] FEEDBACK: Please file feedback in Feedback Hub (WIN + F) under Developer Platform > Command Line.

[Authentication]

  • Fixed an authentication error when trying to connect to Azure Virtual Desktop impacting Insiders in the latest Canary flights.

[Settings]

  • Improved performance of configuring power options in Settings > System > Power & Battery.

[Other]

  • Updated chkdsk to now support specifying volumes with spaces if you have the path encased in quotes (for example, chkdsk “C:\My Volume\SD Card”).
  • Removed unexpected error message when opening Group Policy Editor in the previous two flights.

Reminders for Windows Insiders in the Canary Channel

  • These builds can be unstable and may be released with limited documentation. Join Windows Insider – Get early access to Windows 11 features & updates
  • The builds we release to the Canary Channel represent the latest platform changes early in the development cycle and should not be seen as matched to any specific release of Windows. Features and experiences included in these builds may never get released as we try out different concepts and get feedback. Features may change over time, be removed, or replaced and never get released beyond Windows Insiders. Some of these features and experiences could show up in future Windows releases when they’re ready.
  • Many features in the Canary Channel are rolled out using Control Feature Rollout technology, starting with a subset of Insiders and ramping up over time as we monitor feedback to see how they land before pushing them out to everyone in this channel.
  • The desktop watermark shown at the lower right corner of the desktop is normal for Windows Insider pre-release builds.
  • Some features may show up in the Dev and Beta Channels first before showing up in the Canary Channel.
  • For Windows Insiders who want to be the first to get features gradually rolled out to you, you can turn ON the toggle to get the latest updates as they are available via Settings > Windows Update*. Over time, we will increase the rollouts of features to everyone with the toggle turned on. Should you keep this toggle off, new features will gradually be rolled out to your PC over time once they are ready.
  • Some features in active development we preview with Windows Insiders may not be fully localized and localization will happen over time as features are finalized. As you see issues with localization in your language, please report those issues to us via Feedback Hub.
  • To get off the Canary Channel, a clean install of Windows 11 will be required.
  • Check out Flight Hub for a complete look at what build is in which Insider channel.
Thanks, Windows Insider Program Team
Read the whole story
alvinashcraft
1 minute ago
reply
Pennsylvania, USA
Share this story
Delete

Announcing Windows 11 Insider Preview Build 28020.1797 (Canary Channel)

1 Share
Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 28020.1797 to the Canary Channel. (KB 5079490)

What’s new in Canary Build 28020.1797

Changes and Improvements gradually being rolled out with toggle on*

  • This update includes a small set of general improvements and fixes that improve the overall experience for Insiders running this build on their PCs.

Reminders for Windows Insiders in the Canary Channel

  • Many features in the Canary Channel are rolled out using Control Feature Rollout technology, starting with a subset of Insiders and ramping up over time as we monitor feedback to see how they land before pushing them out to everyone in this channel.
  • The desktop watermark shown at the lower right corner of the desktop is normal for Windows Insider pre-release builds.
  • Some features may show up in the Dev and Beta Channels first before showing up in the Canary Channel.
  • For Windows Insiders who want to be the first to get features gradually rolled out to you, you can turn ON the toggle to get the latest updates as they are available via Settings > Windows Update*. Over time, we will increase the rollouts of features to everyone with the toggle turned on. Should you keep this toggle off, new features will gradually be rolled out to your PC over time once they are ready.
  • Some features in active development we preview with Windows Insiders may not be fully localized and localization will happen over time as features are finalized. As you see issues with localization in your language, please report those issues to us via Feedback Hub.
  • To get off the Canary Channel, a clean install of Windows 11 will be required. As a reminder - Insiders can’t switch to a channel that is receiving builds with lower build numbers without doing a clean installation of Windows 11 due to technical setup requirements.
  • Check out Flight Hub for a complete look at what build is in which Insider channel.
Thanks, Windows Insider Program Team
Read the whole story
alvinashcraft
1 minute ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories