13 Jun 2025
TalkAndroid
Anime Dungeon Fighters Codes – June 2025
Find all the latest Anime Dungeon Fighters codes here!
13 Jun 2025 3:19am GMT
Omniheroes Codes – June 2025
For all the latest Omniheroes Codes here! Keep reading for more!
13 Jun 2025 3:18am GMT
Dislyte Codes – June 2025
Find all the latest Dislyte Codes here! Keep reading for more!
13 Jun 2025 3:16am GMT
12 Jun 2025
Android Developers Blog
Upcoming changes to Wear OS watch faces
Posted by François Deschênes Product Manager - Wear OS 
Today, we are announcing important changes to Wear OS watch face development that will affect how developers publish and update watch faces on Google Play. As part of our ongoing effort to enhance Wear OS app quality, we are moving towards supporting only the Watch Face Format and removing support for AndroidX / Wearable Support Library (WSL) watch faces.
We introduced Watch Face Format at Google I/O in 2023 to make it easier to create watch faces that are customizable and power-efficient. The Watch Face Format is a declarative XML format, so there is no executable code involved in creating a watch face, and there is no code embedded in the watch face APK.
What's changing?
Developers will need to migrate published watch faces to the Watch Face Format by January 14, 2026. Developers using Watch Face Studio to build watch faces will need to resubmit their watch faces to the Play Store using Watch Face Studio version 1.8.7 or above - see below for more details.
When are these changes coming?
Starting January 27, 2025 (already in effect):
- No new AndroidX or Wearable Support Library (WSL) watch faces (legacy watch faces) can be published on the Play Store. Developers can still publish updates to existing watch faces.
Starting January 14, 2026:
- Availability: Users will not be able to install legacy watch faces on any Wear OS devices from the Play Store. Legacy watch faces already installed on a Wear OS device will continue to work.
- Updates: Developers will not be able to publish updates for legacy watch faces to the Play Store.
- Monetization: The following won't be possible for legacy watch faces: one-off watch face purchases, in-app purchases, and subscriptions. Existing purchases and subscriptions will continue to work, but they will not renew, including auto-renewals.
What should developers do next?
To prepare for these changes and to continue publishing watch faces to the Play Store, developers using AndroidX or WSL to build watch faces must migrate their watch faces to the Watch Face Format and resubmit to the Play Store by January 14, 2026.
Developers using Watch Face Studio to build watch faces will need to resubmit their watch faces to the Play Store using Watch Face Studio version 1.8.7 or above:
- Be sure to republish for all Play tracks, including all testing tracks as well as production.
- Remove any bundles from these tracks that were created using Watch Face Studio versions prior to 1.8.7.
Benefits of the Watch Face Format
Watch Face Format was developed to support developers in creating watch faces. This format provides numerous advantages to both developers and end users:
- Simplified development: Streamlined workflows and visual design tools make building watch faces easier.
- Enhanced performance: Optimized for battery efficiency and smooth interactions.
- Increased security: Robust security features protect user data and privacy.
- Forward-compatible: Access to the latest features and capabilities of Wear OS.
Resources to help with migration
To get started migrating your watch faces to the Watch Face Format, check out the following developer guidance:
We encourage developers to begin the migration process as soon as possible to ensure a seamless transition and continued availability of your watch faces on Google Play.
We understand that this change requires effort. If you have further questions, please refer to the Wear OS community announcement. Please report any issues using the issue tracker.
12 Jun 2025 4:00pm GMT
The Official Google Blog
Celebrating 10 years of Android Enterprise and looking ahead
Bringing you some milestones from the last decade, plus how we're building for the future of work.
12 Jun 2025 4:00pm GMT
5 things from I/O to try right now
These AI tools from Google I/O 2025 are available globally for your experimentation.
12 Jun 2025 4:00pm GMT
Weather Lab is an interactive website for sharing Google’s AI weather models.
Today Google DeepMind and Google Research are launching a public preview of Weather Lab, an interactive website for sharing our AIweather models, and debuting our newest…
12 Jun 2025 2:05pm GMT
11 Jun 2025
Android Developers Blog
Smoother app reviews with Play Policy Insights beta in Android Studio
Posted by Naheed Vora - Senior Product Manager, Android App Safety 
Making it easier for you to build safer apps from the start
We understand you want clear Play policy guidance early in your development, so you can focus on building amazing experiences and prevent unexpected delays from disrupting launch plans. That's why we're making it easier to have smoother app publishing experiences, from the moment you start coding.
With Play Policy Insights beta in Android Studio, you'll get richer, in-context guidance on policies that may impact your app through lint warnings. You'll see policy summaries, dos and don'ts to avoid common pitfalls, and direct links to details.
We hope you caught an early demo at I/O. And now, you can check out Play Policy Insights beta in the Android Studio Narwhal Feature Drop Canary release.
How to use Play Policy Insights beta in Android Studio
Lint warnings will pop up as you code, like when you add a permission. For example, if you add an Android API that uses Photos and requires READ_MEDIA_IMAGES permission, then the Photos & Video Insights lint warning will appear under the respective API call line item in Android Studio.
You can also get these insights by going to Code > Inspect for Play Policy Insights and selecting the project scope to analyze. The scope can be set to the whole project, the current module or file, or a custom scope.
In addition to seeing these insights in Android Studio, you can also generate them as part of your Continuous Integration process by adding the following dependency to your project.
Kotlin
lintChecks("com.google.play.policy.insights:insights-lint:<version>")
Groovy
lintChecks 'com.google.play.policy.insights:insights-lint:<version>'
Share your feedback on Play Policy Insights beta
We're actively working on this feature and want your feedback to refine it before releasing it in the Stable channel of Android Studio later this year. Try it out, report issues, and stop by the Google Play Developer Help Community to share your questions and thoughts directly with our team.
Join us on June 16 when we answer your questions. We'd love to hear about:
- How will this change your current Android app development and Google Play Store submission workflow?
- Which was more helpful in addressing issues: lint warnings in the IDE or lint warnings from CI build?
- What was most helpful in the policy guidance, and what could be improved?
Developers have told us they like:
- Catching potential Google Play policy issues early, right in their code, so they can build more efficiently.
- Seeing potential Google Play policy issues and guidance all in one-place, reducing the need to dig through policy announcements and issue emails.
- Easily discussing potential issues with their team, now that everyone has shared information.
- Continuously checking for potential policy issues as they add new features, gaining confidence in a smoother launch.
For more, see our Google Play Help Center article or Android Studio preview release notes.
We hope features like this will help give you a better policy experience and more streamlined development.
11 Jun 2025 4:00pm GMT
10 Jun 2025
Android Developers Blog
Developer preview: Enhanced Android desktop experiences with connected displays
Posted by Francesco Romano - Developer Relations Engineer on Android, and Fahd Imtiaz - Product Manager, Android Developer 
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.
Android has continued to evolve to enable users to be more productive on large screens.
Today, we're excited to share that connected displays support on compatible Android devices is now in developer preview with the Android 16 QPR1 Beta 2 release. As shown at Google I/O 2025, connected displays enable users to attach an external display to their Android device and transform a small screen device into a powerful tool with a large screen. This evolution gives users the ability to move apps beyond a single screen to unlock Android's full productivity potential on external displays.
The connected display update builds on our desktop windowing experience, a capability we previewed last year. Desktop windowing is set to launch later this year for users on compatible tablets running Android 16. Desktop windowing enables users to run multiple apps simultaneously and resize windows for optimal multitasking. This new windowing capability works seamlessly with split screen and other multitasking features users already love on Android and doesn't require switching to a special mode.
Google and Samsung have collaborated to bring a more seamless and powerful desktop windowing experience to large screen devices and phones with connected displays in Android 16 across the Android ecosystem. These advancements will enhance Samsung DeX, and also extend to other Android devices.
For developers, connected displays and desktop windowing present new opportunities for building more engaging and more productive app experiences that seamlessly adapt across form factors. You can try out these features today on your connected display with the Android 16 QPR1 Beta 2 on select Pixel devices.
What's new in connected displays support?
When a supported Android phone or foldable is connected to an external display through a DisplayPort connection, a new desktop session starts on the connected display. The phone and the external display operate independently, and apps are specific to the display on which they're running.
The experience on the connected display is similar to the experience on a desktop, including a task bar that shows running apps and lets users pin apps for quick access. Users are able to run multiple apps side by side simultaneously in freely resizable windows on the connected display.
When a desktop windowing enabled device (like a tablet) is connected to an external display, the desktop session is extended across both displays, unlocking an even more expansive workspace. The two displays then function as one continuous system, allowing app windows, content, and the cursor to move freely between the displays.
A cornerstone of this effort is the evolution of desktop windowing, which is stable in Android 16 and is packed with improvements and new capabilities.
Desktop windowing stable release
We've made substantial improvements in the stability and performance of desktop windowing in Android 16. This means users will encounter a smoother, more reliable experience when managing app windows on connected displays. Beyond general stability improvements, we're introducing several new features:
- Flexible window tiling: Multitasking gets a boost with more intuitive window tiling options. Users can more easily arrange multiple app windows side by side or in various configurations, making it simpler to work across different applications simultaneously on a large screen.
- Multiple desktops: Users can set up multiple desktop sessions to match their distinct productivity requirements and switch between the desktops using keyboard shortcuts, trackpad gestures, and Overview.
- Enhanced app compatibility treatments: New compatibility treatments ensure that even legacy apps behave more predictably and look better on external displays by default. This reduces the burden on developers while providing a better out-of-the-box experience for users.
- Multi-instance management: Users can manage multiple instances of supporting applications (for example, Chrome or, Keep) through the app header button or taskbar context menu. This allows for quick switching between different instances of the same app.
- Desktop persistence: Android can now better maintain window sizes, positions, and states across different desktops. This means users can set up their preferred workspace and have it restored across sessions, offering a more consistent and efficient workflow.
Best practices for optimal app experiences on connected displays
With the introduction of connected display support in Android, it's important to ensure your apps take full advantage of the new display capabilities. To help you build apps that shine in this enhanced environment, here are some key development practices to follow:
Build apps optimized for desktop
- Design for any window size: With phones now connecting to external displays, your mobile app can run in a window of almost any size and aspect ratio. This means the app window can be as big as the screen of the connected display but also flex to fit a smaller window. In desktop windowing, the minimum window size is 386 x 352 dp, which is smaller than most phones. This fundamentally changes how you need to think about UI. With orientation and resizability changes in Android 16, it becomes even more critical for you to update your apps to support resizability and portrait and landscape orientations for an optimal experience with desktop windowing and connected displays. Make sure your app supports any window size by following the best practices on adaptive development.
- Implement features for top productivity: You now have all the tools necessary to build mobile apps that match desktop, so start adding features to boost users productivity! Allow users to open multiple instances of the same app, which is invaluable for tasks like comparing documents, managing different conversations, or viewing multiple files simultaneously. Support data sharing with drag and drop, and maintain user flow across configuration changes by implementing a robust state management system.
Handle dynamic display changes
- Don't assume a constant Display object: The Display object associated with your app's context can change when an app window is moved to an external display or if the display configuration changes. Your app should gracefully handle configuration change events and query display metrics dynamically rather than caching them.
- Account for density configuration changes: External displays can have vastly different pixel densities than the primary device screen. Ensure your layouts and resources adapt correctly to these changes to maintain UI clarity and usability. Use density-independent pixels (dp) for layouts, provide density-specific resources, and ensure your UI scales appropriately.
Go beyond just the screen
- Correctly support external peripherals: When users connect to an external monitor, they often create a more desktop-like environment. This frequently involves using external keyboards, mice, trackpads, webcams, microphones, and speakers. If your app uses camera or microphone input, the app should be able to detect and utilize peripherals connected through the external display or a docking station.
- Handle keyboard actions: Desktop users rely heavily on keyboard shortcuts for efficiency. Implement standard shortcuts (for example, Ctrl+C, Ctrl+V, Ctrl+Z) and consider app-specific shortcuts that make sense in a windowed environment. Make sure your app supports keyboard navigation.
- Support mouse interactions: Beyond simple clicks, ensure your app responds correctly to mouse hover events (for example, for tooltips or visual feedback), right-clicks (for contextual menus), and precise scrolling. Consider implementing custom pointers to indicate different actions.
Getting started
Explore the connected displays and enhanced desktop windowing features in the latest Android Beta. Get Android 16 QPR1 Beta 2 on a supported Pixel device (Pixel 8 and Pixel 9 series) to start testing your app today. Then enable desktop experience features in the developer settings.
Support for connected displays in the Android Emulator is coming soon, so stay tuned for updates!
Dive into the updated documentation on multi-display support and window management to learn more about implementing these best practices.
Feedback
Your feedback is crucial as we continue to refine these experiences. Please share your thoughts and report any issues through our official feedback channels.
We're committed to making Android a versatile platform that adapts to the many ways users want to interact with their apps and devices. The improvements to connected display support are another step in that direction, and we can't wait to see the amazing experiences you'll build!
10 Jun 2025 6:02pm GMT