دسته: اخبار اندروید

  • Google Play’s Indie Games Fund in Latin America returns for its 4th year



    Posted by Daniel Trócoli – Google Play Partnerships

    We’re thrilled to announce the return of Google Play’s Indie Games Fund (IGF) in Latin America for its fourth consecutive year! This year, we’re once again committing $2 million to empower another 10 indie game studios across the region. With this latest round of funding, our total investment in Latin American indie games will reach an impressive $8 million USD.

    Since its inception, the IGF has been a cornerstone of our commitment to fostering growth for developers of all sizes on Google Play. We’ve seen firsthand the transformative impact this support has had, enabling studios to expand their teams, refine their creations, and reach new audiences globally.

    What’s in store for the Indie Games Fund in 2025?

    Just like in previous years, selected small game studios based in Latin America will receive a share of the $2 million fund, along with support from the Google Play team.

    As Vish Game Studio, a previously selected studio, shared: “The IGF was a pivotal moment for our studio, boosting us to the next level and helping us form lasting connections.” We believe in fostering these kinds of pivotal moments for all our selected studios.

    The program is open to indie game developers who have already launched a game, whether it’s on Google Play, another mobile platform, PC, or console. Each selected recipient will receive between $150,000 and $200,000 to help them elevate their game and realize their full potential.

    Check out all eligibility criteria and apply now! Applications will close at 12:00 PM BRT on July 31, 2025. To give your application the best chance, remember that priority will be given to applications received by 12:00 PM BRT on July 15, 2025.

    Google Play logo




    Source link

  • Get ready for the next generation of gameplay powered by Play Games Services



    Posted by Chris Wilk – Group Product Manager, Games on Google Play

    To captivate players and grow your game, you need tools that enhance discovery and retention. Play Games Services (PGS) is your key to unlocking a suite of services that connect you with over 2 billion monthly active players. PGS empowers you to drive engagement through features like achievements and increase retention with promotions tailored to each gameplay progress. These tools are designed to help you deliver relevant and compelling content that keeps players coming back.

    We are continuously evolving gaming on Play, and this year, we’re introducing more PGS-powered experiences to give you deeper player insights and greater visibility in the Play Store. To access these latest advancements and ensure continued functionality, you must migrate from PGS v1 to PGS v2 by May 2026. Let’s take a closer look at what’s new:

    https://www.youtube.com/watch?v=v-6b_wWF96U

    Drive discovery and engagement by rewarding gameplay progress

    We’re fundamentally transforming how achievements work in the Play Store, making them a key driver for a great gaming experience. Now deeply embedded across the store, achievements are easily discoverable via search filters and game detail pages, and further drive engagement when offered with Play Points.

    At a minimum, you should have at least 15 achievements spread across the lifetime of the game, in the format of incremental achievements to show progress. Games that enable players to earn at least 5 achievements in the first 2 hours of gameplay are most successful in driving deeper engagement*.

    The most engaging titles offer 40 or more achievements with diverse types of goals including leveling up characters, game progression, hidden surprises, or even failed attempts. To help you get the most out of achievements, we’ve made it easier to create achievements with bulk configuration in Play Console.

    For eligible titles*, Play activates quests to reward players for completing achievements – for example with Play Points. Supercell activated quests for Hay Day, leading to an average 177% uplift in installs*. You can tailor your quests to achieve specific campaign objectives, whether it’s attracting high-value players or driving spend through repeated engagement, all while making it easy to jump back into your game.

    Achievement-based quests allowing users to grow their farm and earn Play Points in the mobile game Hay Day on Google Play

    Hay Day boosted new installs with achievement-based quests

    Increase retention with tailored promotions

    Promotional content is a vital tool for you to highlight new events, major content updates, and exciting offers within your game. It turns Play into a direct marketing channel to re-engage with your players. We’ve enhanced audience targeting capabilities so you can tailor your content to reach and convert the most relevant players.

    By integrating PGS, you can use the Play Grouping API to create custom segments based on gameplay context*. Using this feature, Kabam launched promotional content to custom audiences for Marvel Contest of Champions, resulting in a 4x increase in lapsed user engagement*.

    Marvel Contest of Champions increased retention with targeted promotional content on Google Play

    Marvel Contest of Champions increased retention with targeted promotional content

    Start implementing PGS features today

    PGS is designed to make the sign-in experience more seamless for players, automatically syncing their progress and identity across Android devices. With a single tap, they can pick up where they left off or start a new game from any screen. Whether you use your own sign-in solution, services from third parties, or a combination of both, we’ve made it easier to integrate Play Games Services with the Recall API.

    To ensure a consistent sign-in experience for all players, we’re phasing out PGS v1.

    All games currently using PGS v1 must migrate to PGS v2 by May 2026. After this date, you will no longer be able to publish or update games that use the v1 SDK.

    Below you’ll find the timeline to plan your migration:

    Migration guide

    May 2025 As announced at I/O, new apps using PGS v1 can no longer be published. While existing apps can release updates with v1 and the APIs are still functional, you’ll need to migrate by May 2026, and APIs will be fully shut down in 2028.
    May 2026
    APIs are still functional for users, but are no longer included in the SDK. New app versions compiled with the most recent SDK would fail in the build process if your code still uses the removed APIs. If your app still relies on any of these APIs, you should migrate to PGS v2 as soon as possible.
    Q3 2028 APIs are no longer functional and will fail when a request is sent by an app.

    Looking ahead, more opportunities powered by PGS

    Coming soon, players will be able to generate unique, AI-powered avatars within their profiles – creating fun, diverse representations of their gaming selves. With PGS integration, developers can allow players to carry over their avatar within the game. This enables players to showcase their gaming identity across the entire gameplay experience, creating an even stronger motivation to re-engage with your game.

    Gen AI avatar profiles create player-centric experiences on Google Play

    Gen AI avatar profiles create more player-centric experiences

    PGS is the foundational tool for maximizing your business growth on Play, enabling you to tailor your content for each player and access the latest gameplay innovations on the platform. Stay tuned for more PGS features coming this year to provide an even richer player experience.

    * To be eligible, the title must participate in Play Points, integrate Play Games Services v2, and have achievements configured in Play Console.

    * Data source from partner. Average incremental installs over a 14-day period.

    * Data source from partner.

    * The Play Grouping API provides strong measures to protect privacy for end users, including user-visible notification when the API is first used, and opt-out options through My Activity.

    Google Play logo



    Source link

  • Top announcements to know from Google Play at I/O ‘25



    Posted by Raghavendra Hareesh Pottamsetty – Google Play Developer and Monetization Lead

    At Google Play, we’re dedicated to helping people discover experiences they’ll love, while empowering developers like you to bring your ideas to life and build successful businesses. This year, Google I/O was packed with exciting announcements designed to do just that. For a comprehensive overview of everything we shared, be sure to check out our blog post recapping What’s new in Google Play.

    Today, we’ll dive specifically into the latest updates designed to help you streamline your subscriptions offerings and maximize your revenue on Play. Get a quick overview of these updates in our video below, or read on for more details.

    https://www.youtube.com/watch?v=Cny82VuONU4

    #1: Subscriptions with add-ons: Streamlining subscriptions for you and your users

    We’re excited to announce multi-product checkout for subscriptions, a new feature designed to streamline your purchase flow and offer a more unified experience for both you and your users. This enhancement allows you to sell subscription add-ons right alongside your base subscriptions, all while maintaining a single, aligned payment schedule.

    The result? A simplified user experience with just one price and one transaction, giving you more control over how your subscribers upgrade, downgrade, or manage their add-ons. Learn more about how to create add-ons.

    base subscriptions and add-ons together in a single, streamlined transaction on Google Play

    You can now sell base subscriptions and add-ons together in a single, streamlined transaction

    #2: Showcasing benefits in more places across Play: Increasing visibility and value

    We’re also making it easier for you to retain more of your subscribers by showcasing subscription benefits in more key areas across Play. This includes the Subscriptions Center, within reminder emails, and even during the purchase and cancellation processes. This increased visibility has already proved effective, reducing voluntary churn by 2%. To take advantage of this powerful new capability, be sure to enter your subscription benefits details in Play Console.

    value notifications across subscriptions center, email reminders, and during purchase transactions, shown across form factors on Google Play

    To help reduce voluntary churn, we’re showcasing your subscriptions benefits across Play

    #3: New grace period and account hold duration: Decreasing involuntary churn

    Another way we’re helping you maximize your revenue is by extending grace periods and account hold durations to tackle unintended subscription losses, which often occur when payment methods unexpectedly decline.

    Now, you can customize both the grace period (when users retain access while renewal is attempted) and the account hold period (when access is suspended). You can set a grace period of up to 30 days and an account hold period of up to 60 days. However, the total combined recovery period (grace period + account hold) cannot exceed 60 days.

    This means instead of an immediate cancellation, your users have a longer window to update their payment information. Developers who’ve already extended their decline recovery period—from 30 to 60 days—have seen impressive results, with an average 10% reduction in involuntary churn for renewals. Ready to see these results for yourself? Adjust your grace period and account hold durations in Play Console today.

    a ten percent reduction in involuntary churn on Google Play according to internal Google data

    Developers who extend their decline recovery period see an average 10% reduction in involuntary churn

    But that’s not all. We’re constantly investing in ways to help you optimize conversion throughout the entire buyer lifecycle. This includes boosting purchase-readiness by prompting users to set up payment methods and verification right from device setup, and we’ve integrated these prompts into highly visible areas like the Play and Google account menus. Beyond that, we’re continuously enabling payments in more markets and expanding payment options. Our AI models are even working to optimize in-app transactions by suggesting the right payment method at the right time, and we’re bringing buyers back with effective cart abandonment reminders.

    That’s it for our top announcements from Google I/O 2025, but there’s so many more updates to discover from this year’s event. Check out What’s new in Google Play to learn more, and to dive deeper into the session details, view the Google Play I/O playlist for all the announcements.

    https://www.youtube.com/watch?v=T41OD37tI54

    Google Play logo



    Source link

  • Agentic AI takes Gemini in Android Studio to the next level



    Posted by Sandhya Mohan – Product Manager, and Jose Alcérreca – Developer Relations Engineer

    Software development is undergoing a significant evolution, moving beyond reactive assistants to intelligent agents. These agents don’t just offer suggestions; they can create execution plans, utilize external tools, and make complex, multi-file changes. This results in a more capable AI that can iteratively solve challenging problems, fundamentally changing how developers work.

    At Google I/O 2025, we offered a glimpse into our work on agentic AI in Android Studio, the integrated development environment (IDE) focused on Android development. We showcased that by combining agentic AI with the built-in portfolio of tools inside of Android Studio, the IDE is able to assist you in developing Android apps in ways that were never possible before. We are now incredibly excited to announce the next frontier in Android development with the availability of ‘Agent Mode’ for Gemini in Android Studio.

    These features are available in the latest Android Studio Narwhal Feature Drop Canary release, and will be rolled out to business tier subscribers in the coming days. As with all new Android Studio features, we invite developers to provide feedback to direct our development efforts and ensure we are creating the tools you need to build better apps, faster.

    Agent Mode

    Gemini in Android Studio’s Agent Mode is a new experimental capability designed to handle complex development tasks that go beyond what you can experience by just chatting with Gemini.

    With Agent Mode, you can describe a complex goal in natural language — from generating unit tests to complex refactors — and the agent formulates an execution plan that can span multiple files in your project and executes under your direction. Agent Mode uses a range of IDE tools for reading and modifying code, building the project, searching the codebase and more to help Gemini complete complex tasks from start to finish with minimal oversight from you.

    To use Agent Mode, click Gemini in the sidebar, then select the Agent tab, and describe a task you’d like the agent to perform. Some examples of tasks you can try in Agent Mode include:

      • Build my project and fix any errors
      • Extract any hardcoded strings used across my project and migrate to strings.xml
      • Add support for dark mode to my application
      • Given an attached screenshot, implement a new screen in my application using Material 3

    The agent then suggests edits and iteratively fixes bugs to complete tasks. You can review, accept, or reject the proposed changes along the way, and ask the agent to iterate on your feedback.

    moving image showing Gemini breaking tasks down into a plan with simple steps, and the list of IDE tools it needs to complete each step

    Gemini breaks tasks down into a plan with simple steps. It also shows the list of IDE tools it needs to complete each step.

    While powerful, you are firmly in control, with the ability to review, refine and guide the agent’s output at every step. When the agent proposes code changes, you can choose to accept or reject them.

    screenshot of Gemini in Android Studio showing the Agent prompting the user to accept or reject a change

    The Agent waits for the developer to approve or reject a change.

    Additionally, you can enable “Auto-approve” if you are feeling lucky 😎 — especially useful when you want to iterate on ideas as rapidly as possible.

    You can delegate routine, time-consuming work to the agent, freeing up your time for more creative, high-value work. Try out Agent Mode in the latest preview version of Android Studio – we look forward to seeing what you build! We are investing in building more agentic experiences for Gemini in Android Studio to make your development even more intuitive, so you can expect to see more agentic functionality over the next several releases.

    moving image showing that Gemini understanding the context of an app

    Gemini is capable of understanding the context of your app

    Supercharge Agent Mode with your Gemini API key

    screenshot of Gemini API key prompt in Android Studio

    The default Gemini model has a generous no-cost daily quota with a limited context window. However, you can now add your own Gemini API key to expand Agent Mode’s context window to a massive 1 million tokens with Gemini 2.5 Pro.

    A larger context window lets you send more instructions, code and attachments to Gemini, leading to even higher quality responses. This is especially useful when working with agents, as the larger context provides Gemini 2.5 Pro with the ability to reason about complex or long-running tasks.

    screenshot of how to add your API Key in the Gemini settings

    Add your API key in the Gemini settings

    To enable this feature, get a Gemini API key by navigating to Google AI Studio. Sign in and get a key by clicking on the “Get API key” button. Then, back in Android Studio, navigate to the settings by going to File (Android Studio on macOS) > Settings > Tools > Gemini to enter your Gemini API key. Relaunch Gemini in Android Studio and get even better responses from Agent Mode.

    Be sure to safeguard your Gemini API key, as additional charges apply for Gemini API usage associated with a personal API key. You can monitor your Gemini API key usage by navigating to AI Studio and selecting Get API key > Usage & Billing.

    Note that business tier subscribers already get access to Gemini 2.5 Pro and the expanded context window automatically with their Gemini Code Assist license, so these developers will not see an API key option.

    Model Context Protocol (MCP)

    Gemini in Android Studio’s Agent Mode can now interact with external tools via the Model Context Protocol (MCP). This feature provides a standardized way for Agent Mode to use tools and extend knowledge and capabilities with the external environment.

    There are many tools you can connect to the MCP Host in Android Studio. For example you could integrate with the Github MCP Server to create pull requests directly from Android Studio. Here are some additional use cases to consider.

    In this initial release of MCP support in the IDE you will configure your MCP servers through a mcp.json file placed in the configuration directory of Studio, using the following format:

    {
      "mcpServers": {
        "memory": {
          "command": "npx",
          "args": [
            "-y",
            "@modelcontextprotocol/server-memory"
          ]
        },
        "sequential-thinking": {
          "command": "npx",
          "args": [
            "-y",
            "@modelcontextprotocol/server-sequential-thinking"
          ]
        },
        "github": {
          "command": "docker",
          "args": [
            "run",
            "-i",
            "--rm",
            "-e",
            "GITHUB_PERSONAL_ACCESS_TOKEN",
            "ghcr.io/github/github-mcp-server"
          ],
          "env": {
            "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
          }
        }
      }  
    }
    
    Example configuration with two MCP servers

    For this initial release, we support interacting with external tools via the stdio transport as defined in the MCP specification. We plan to support the full suite of MCP features in upcoming Android Studio releases, including the Streamable HTTP transport, external context resources, and prompt templates.

    For more information on how to use MCP in Studio, including the mcp.json configuration file format, please refer to the Android Studio MCP Host documentation.

    By delegating routine tasks to Gemini through Agent Mode, you’ll be able to focus on more innovative and enjoyable aspects of app development. Download the latest preview version of Android Studio on the canary release channel today to try it out, and let us know how much faster app development is for you!

    As always, your feedback is important to us – check known issues, report bugs, suggest improvements, and be part of our vibrant community on LinkedIn, Medium, YouTube, or X. Let’s build the future of Android apps together!





    Source link

  • How Mecha BREAK is driving PC-only growth on Google Play Games



    Posted by Kosuke Suzuki – Director, Games on Google Play

    On July 1, Amazing Seasun Games is set to unveil its highly anticipated action shooting game – Mecha BREAK, with a multiplatform launch across PC and Console. A key to their PC growth strategy is Google Play Games on PC, enabling the team to build excitement with a pre-registration campaign, maximize revenue with PC earnback, and ensure a secure, top-tier experience on PC.

    Building momentum with pre-registration

    With a legacy of creating high-quality games since 1995, Amazing Seasun Games has already seen Mecha BREAK attract over 3.5 million players during the last beta test. To build on this momentum, the studio is bringing their game to Google Play Games on PC to open pre-registration and connect with its massive player audience.

    “We were excited to launch on Google Play Games on PC. We want to make sure all players can enjoy the Mecha BREAK experience worldwide.”

    – Kris Kwok, Executive Producer of Mecha BREAK and CEO of Amazing Seasun Games

    screenshot of Mecha BREAK's pre-registration on Google Play Games on PC homepage

    Mecha BREAK pre-registration on Google Play Games on PC homepage

    Accelerating growth with the Native PC program

    Mecha BREAK‘s launch strategy includes leveraging the native PC earnback, a program that gives native PC developers the opportunity to unlock up to 15% in additional earnback.

    Beyond earnback, the program offers comprehensive support for PC game development, distribution, and growth. Developers can manage PC builds in Play Console, simplifying the process of packaging PC versions, configuring releases, and managing store listings. Now, you can also view PC-specific sales reports, providing a more precise analysis of your game’s financial performance.

    Delivering a secure and high quality PC experience

    Mecha BREAK is designed to deliver an intense and high-fidelity experience on PC. Built on a cutting-edge, proprietary 3D engine, the game offers players three unique modes of fast-paced combat on land and in the air.

      • Diverse combat styles: Engage in six-on-six hero battles, three-on-three matches, or the unique PvPvE extraction mode “Mashmak”.
      • Free customization options: Create personalized characters with a vast array of colors, patterns and gameplay styles, from close-quarters brawlers to long-range tactical units.

    moving image of Mecha BREAK's gameplay on Google Play Games on PC

    Mecha BREAK offers a high-fidelity experience on PC

    The decision to integrate with Google Play Games on PC was driven by the platform’s robust security infrastructure, including tools such as Play Integrity API, supporting large-scale global games like Mecha BREAK.

    “Mecha BREAK’s multiplayer setting made Google Play Games a strong choice, as we expect exceptional operational stability and performance. The platform also offers advanced malware protection and anti-cheat capabilities.”

    – Kris Kwok, Executive Producer of Mecha BREAK and CEO of Amazing Seasun Games

    Bring your game to Google Play Games on PC

    This year, the native PC program is open to all PC games, including PC-only titles. If you’re ready to expand your game’s reach and accelerate its growth, learn more about the eligibility requirements and how to join the program today.



    Source link

  • Top 3 Updates for Android Developer Productivity @ Google I/O ‘25



    Posted by Meghan Mehta – Android Developer Relations Engineer

    https://www.youtube.com/watch?v=-GikklXjkgM

    #1 Agentic AI is available for Gemini in Android Studio

    Gemini in Android Studio is the AI-powered coding companion that makes you more productive at every stage of the dev lifecycle. At Google I/O 2025 we previewed new agentic AI experiences: Journeys for Android Studio and Version Upgrade Agent. These innovations make it easier for you to build and test code. We also announced Agent Mode, which was designed to handle complex, multi-stage development tasks that go beyond typical AI assistant capabilities, invoking multiple tools to accomplish tasks on your behalf. We’re excited to see how you leverage these agentic AI experiences which are now available in the latest preview version of Android Studio on the canary release channel.

    You can also use Gemini to automatically generate Jetpack Compose previews, as well as transform UI code using natural language, saving you time and effort. Give Gemini more context by attaching images and project files to your prompts, so you can get more relevant responses. And if you’re looking for enterprise-grade privacy and security features backed by Google Cloud, Gemini in Android Studio for businesses is now available. Developers and admins can unlock these features and benefits by subscribing to Gemini Code Assist Standard or Enterprise editions.

    https://www.youtube.com/watch?v=KXKP2tDPW4Y

    #2 Build better apps faster with the latest stable release of Jetpack Compose

    Compose is our recommended UI toolkit for Android development, used by over 60% of the top 1K apps on Google Play. We released a new version of our Jetpack Navigation library: Navigation 3, which has been rebuilt from the ground up to give you more flexibility and control over your implementation. We unveiled the new Material 3 Expressive update which provides tools to enhance your product’s appeal by harnessing emotional UX, making it more engaging, intuitive, and desirable for your users. The latest stable Bill of Materials (BOM) release for Compose adds new features such as autofill support, auto-sizing text, visibility tracking, animate bounds modifier, accessibility checks in tests, and more! This release also includes significant rewrites and improvements to multiple sub-systems including semantics, focus and text optimizations.

    These optimizations are available to you with no code changes other than upgrading your Compose dependency. If you’re looking to try out new Compose functionality, the alpha BOM offers new features that we’re working on including pausable composition, updates to LazyLayout prefetch, context menus, and others. Finally, we’ve added Compose support to CameraX and Media3, making it easier to integrate camera capture and video playback into your UI with Compose idiomatic components.

    https://www.youtube.com/watch?v=89UusPuz8q4

    #3 The new Kotlin Multiplatform (KMP) shared module template helps you share business logic

    KMP enables teams to deliver quality Android and iOS apps with less development time. The KMP ecosystem continues to grow: last year alone, over 900 new KMP libraries were published. At Google I/O we released a new Android Studio KMP shared module template to help you craft and manage business logic, updated Jetpack libraries and new codelabs (Getting started with Kotlin Multiplatform and Migrating your Room database to KMP) to help you get started with KMP. We also shared additional announcements at KotlinConf.

    https://www.youtube.com/watch?v=gP5Y-ct6QXI

    Learn more about what we announced at Google I/O 2025 to help you build better apps, faster.



    Source link

  • Top 3 things to know for AI on Android at Google I/O ‘25



    Posted by Kateryna Semenova – Sr. Developer Relations Engineer

    AI is reshaping how users interact with their favorite apps, opening new avenues for developers to create intelligent experiences. At Google I/O, we showcased how Android is making it easier than ever for you to build smart, personalized and creative apps. And we’re committed to providing you with the tools needed to innovate across the full development stack in this evolving landscape.

    This year, we focused on making AI accessible across the spectrum, from on-device processing to cloud-powered capabilities. Here are the top 3 announcements you need to know for building with AI on Android from Google I/O ‘25:

    #1 Leverage the efficiency of Gemini Nano for on-device AI experiences

    https://www.youtube.com/watch?v=mP9QESmEDls

    For on-device AI, we announced a new set of ML Kit GenAI APIs powered by Gemini Nano, our most efficient and compact model designed and optimized for running directly on mobile devices. These APIs provide high-level, easy integration for common tasks including text summarization, proofreading, rewriting content in different styles, and generating image description. Building on-device offers significant benefits such as local data processing and offline availability at no additional cost for inference. To start integrating these solutions explore the ML Kit GenAI documentation, the sample on GitHub and watch the “Gemini Nano on Android: Building with on-device GenAI” talk.

    #2 Seamlessly integrate on-device ML/AI with your own custom models

    https://www.youtube.com/watch?v=xLmJJk1gbuE

    The Google AI Edge platform enables building and deploying a wide range of pretrained and custom models on edge devices and supports various frameworks like TensorFlow, PyTorch, Keras, and Jax, allowing for more customization in apps. The platform now also offers improved support of on-device hardware accelerators and a new AI Edge Portal service for broad coverage of on-device benchmarking and evals. If you are looking for GenAI language models on devices where Gemini Nano is not available, you can use other open models via the MediaPipe LLM Inference API.

    Serving your own custom models on-device can pose challenges related to handling large model downloads and updates, impacting the user experience. To improve this, we’ve launched Play for On-Device AI in beta. This service is designed to help developers manage custom model downloads efficiently, ensuring the right model size and speed are delivered to each Android device precisely when needed.

    For more information watch “Small language models with Google AI Edge” talk.

    #3 Power your Android apps with Gemini Flash, Pro and Imagen using Firebase AI Logic

    https://www.youtube.com/watch?v=U8Nb68XsVY4

    For more advanced generative AI use cases, such as complex reasoning tasks, analyzing large amounts of data, processing audio or video, or generating images, you can use larger models from the Gemini Flash and Gemini Pro families, and Imagen running in the cloud. These models are well suited for scenarios requiring advanced capabilities or multimodal inputs and outputs. And since the AI inference runs in the cloud any Android device with an internet connection is supported. They are easy to integrate into your Android app by using Firebase AI Logic, which provides a simplified, secure way to access these capabilities without managing your own backend. Its SDK also includes support for conversational AI experiences using the Gemini Live API or generating custom contextual visual assets with Imagen. To learn more, check out our sample on GitHub and watch “Enhance your Android app with Gemini Pro and Flash, and Imagen” session.

    These powerful AI capabilities can also be brought to life in immersive Android XR experiences. You can find corresponding documentation, samples and the technical session: “The future is now, with Compose and AI on Android XR“.

    Flow cahrt demonstrating Firebase AI Logic integration architecture

    Figure 1: Firebase AI Logic integration architecture

    Get inspired and start building with AI on Android today

    We released a new open source app, Androidify, to help developers build AI-driven Android experiences using Gemini APIs, ML Kit, Jetpack Compose, CameraX, Navigation 3, and adaptive design. Users can create personalized Android bot with Gemini and Imagen via the Firebase AI Logic SDK. Additionally, it incorporates ML Kit pose detection to detect a person in the camera viewfinder. The full code sample is available on GitHub for exploration and inspiration. Discover additional AI examples in our Android AI Sample Catalog.

    moving image of the Androidify app on a mobile device, showing a fair-skinned woman with blond hair wearing a red jacket with black shirt and pants and a pair of sunglasses converting into a 3D image of a droid with matching skin tone and blond hair wearing a red jacket with black shirt and pants and a pair of sunglasses

    The original image and Androidifi-ed image

    Choosing the right Gemini model depends on understanding your specific needs and the model’s capabilities, including modality, complexity, context window, offline capability, cost, and device reach. To explore these considerations further and see all our announcements in action, check out the AI on Android at I/O ‘25 playlist on YouTube and check out our documentation.

    We are excited to see what you will build with the power of Gemini!



    Source link

  • 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):

    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.




    Source link

  • Smoother app reviews with Play Policy Insights beta in Android Studio



    Posted by Naheed Vora – Senior Product Manager, Android App Safety

    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.

    a screenshot of Play Policy Insights in Android Studio

    Play Policy Insights beta in Android Studio shows rich, in-context guidance

    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.

    a screenshot of Specify Inspection Scope menu in Play Policy Insights in Android Studio

    Get Play Policy Insights beta for the whole project, the current module or file, or a custom scope and see the results along with details for each insights in the Problems tool window.

    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.



    Source link

  • Android Developers Blog: Android 16 is here



    Posted by Matthew McCullough – VP of Product Management, 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, 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.

    Today we’re releasing Android 16 and making it available on most supported Pixel devices. Look for new devices running Android 16 in the coming months.

    This also marks the availability of the source code at the Android Open Source Project (AOSP). You can examine the source code for a deeper understanding of how Android works, and our focus on compatibility means that you can leverage your app development skills in Android Studio with Jetpack Compose to create applications that thrive across the entire ecosystem.

    Major and minor SDK releases

    With Android 16, we’ve added the concept of a minor SDK release to allow us to iterate our APIs more quickly, reflecting the rapid pace of the innovation Android is bringing to apps and devices.

    Android 16 2025 SDK release timeline

    We plan to have another release in Q4 of 2025 which also will include new developer APIs. Today’s major release will be the only release in 2025 to include planned app-impacting behavior changes.
    In addition to new developer APIs, the Q4 minor release will pick up feature updates, optimizations, and bug fixes.

    We’ll continue to have quarterly Android releases. The Q3 update in-between the API releases is providing much of the new visual polish associated with Material Expressive, and you can get the Q3 beta today on your supported Pixel device.

    Camera and media APIs to empower creators

    Android 16 enhances support for professional camera users, allowing for night mode scene detection, hybrid auto exposure, and precise color temperature adjustments. It’s easier than ever to capture motion photos with new Intent actions, and we’re continuing to improve UltraHDR images, with support for HEIC encoding and new parameters from the ISO 21496-1 draft standard. Support for the Advanced Professional Video (APV) codec improves Android’s place in professional recording and post-production workflows, with perceptually lossless video quality that survives multiple decodings/re-encodings without severe visual quality degradation.

    Also, Android’s photo picker can now be embedded in your view hierarchy, and users will appreciate the ability to search cloud media.

    More consistent, beautiful apps

    Android 16 introduces changes to improve the consistency and visual appearance of apps, laying the foundation for the upcoming Material 3 Expressive changes. Apps targeting Android 16 can no longer opt-out of going edge-to-edge, and ignores the elegantTextHeight attribute to ensure proper spacing in Arabic, Lao, Myanmar, Tamil, Gujarati, Kannada, Malayalam, Odia, Telugu or Thai.

    Adaptive Android apps

    With Android apps now running on a variety of devices and more windowing modes on large screens, developers should build Android apps that adapt to any screen and window size, regardless of device orientation. For apps targeting Android 16 (API level 36), Android 16 includes changes to how the system manages orientation, resizability, and aspect ratio restrictions. On displays with smallest width >= 600dp, the restrictions no longer apply and apps will fill the entire display window. You should check your apps to ensure your existing UIs scale seamlessly, working well across portrait and landscape aspect ratios. We’re providing frameworks, tools, and libraries to help.

    Side by side displays of non-adaptive app UI with on the left with text reading Goodbye 'mobile-only' apps and adaptive app UI on the right with text reads Hello adaptive apps

    You can test these overrides without targeting using the app compatibility framework by enabling the UNIVERSAL_RESIZABLE_BY_DEFAULT flag. Read more about changes to orientation and resizability APIs in Android 16.

    Predictive back by default and more

    Apps targeting Android 16 will have system animations for back-to-home, cross-task, and cross-activity by default. In addition, Android 16 extends predictive back navigation to three-button navigation, meaning that users long-pressing the back button will see a glimpse of the previous screen before navigating back.

    To make it easier to get the back-to-home animation, Android 16 adds support for the onBackInvokedCallback with the new PRIORITY_SYSTEM_NAVIGATION_OBSERVER. Android 16 additionally adds the finishAndRemoveTaskCallback and moveTaskToBackCallback for custom back stack behavior with predictive back.

    Consistent progress notifications

    Android 16 introduces Notification.ProgressStyle, which lets you create progress-centric notifications that can denote states and milestones in a user journey using points and segments. Key use cases include rideshare, delivery, and navigation. It’s the basis for Live Updates, which will be fully realized in an upcoming Android 16 update.

    side-by-side screenshots of a Pixel device showing progress notifications on the homescreen on the left and the updated progress notification in the notification menu on the right

    Custom AGSL graphical effects

    Android 16 adds RuntimeColorFilter and RuntimeXfermode, allowing you to author complex effects like Threshold, Sepia, and Hue Saturation in AGSL and apply them to draw calls.

    Help to create better performing, more efficient apps and games

    From APIs to help you understand app performance, to platform changes designed to increase efficiency, Android 16 is focused on making sure your apps perform well. Android 16 introduces system-triggered profiling to ProfilingManager, ensures at most one missed execution of scheduleAtFixedRate is immediately executed when the app returns to a valid lifecycle for better efficiency, introduces hasArrSupport and getSuggestedFrameRate(int) to make it easier for your apps to take advantage of adaptive display refresh rates, and introduces the getCpuHeadroom and getGpuHeadroom APIs along with CpuHeadroomParams and GpuHeadroomParams in SystemHealthManager to provide games and resource-intensive apps estimates of available GPU and CPU resources on supported devices.

    JobScheduler updates

    JobScheduler.getPendingJobReasons in Android 16 returns multiple reasons why a job is pending, due to both explicit constraints you set and implicit constraints set by the system. The new JobScheduler.getPendingJobReasonsHistory returns the list of the most recent pending job reason changes, allowing you to better tune the way your app works in the background.

    Android 16 is making adjustments for regular and expedited job runtime quota based on which apps standby bucket the app is in, whether the job starts execution while the app is in a top state, and whether the job is executing while the app is running a Foreground Service.

    To detect (and then reduce) abandoned jobs, apps should use the new STOP_REASON_TIMEOUT_ABANDONED job stop reason that the system assigns for abandoned jobs, instead of STOP_REASON_TIMEOUT.

    16KB page sizes

    Android 15 introduced support for 16KB page sizes to improve the performance of app launches, system boot-ups, and camera starts, while reducing battery usage. Android 16 adds a 16 KB page size compatibility mode, which, combined with new Google Play technical requirements, brings Android closer to having devices shipping with this important change. You can validate if your app needs updating using the 16KB page size checks & APK Analyzer in the latest version of Android Studio.

    ART internal changes

    Android 16 includes the latest updates to the Android Runtime (ART) that improve the Android Runtime’s (ART’s) performance and provide support for additional language features. These improvements are also available to over a billion devices running Android 12 (API level 31) and higher through Google Play System updates. Apps and libraries that rely on internal non-SDK ART structures may not continue to work correctly with these changes.

    Privacy and security

    Android 16 continues our mission to improve security and ensure user privacy. It includes Improved security against Intent redirection attacks, makes MediaStore.getVersion unique to each app, adds an API that allows apps to share Android Keystore keys, incorporates the latest version of the Privacy Sandbox on Android, introduces a new behavior during the companion device pairing flow to protect the user’s location privacy, and allows a user to easily select from and limit access to app-owned shared media in the photo picker.

    Local network permission testing

    Android 16 allows your app to test the upcoming local network permission feature, which will require your app to be granted NEARBY_WIFI_DEVICES permission. This change will be enforced in a future Android major release.

    An Android built for everyone

    Android 16 adds features such as Auracast broadcast audio with compatible LE Audio hearing aids, Accessibility changes such as extending TtsSpan with TYPE_DURATION, a new list-based API within AccessibilityNodeInfo, improved support for expandable elements using setExpandedState, RANGE_TYPE_INDETERMINATE for indeterminate ProgressBar widgets, AccessibilityNodeInfo getChecked and setChecked(int) methods that support a “partially checked” state, setSupplementalDescription so you can provide text for a ViewGroup without overriding information from its children, and setFieldRequired so apps can tell an accessibility service that input to a form field is required.

    Outline text for maximum text contrast

    Android 16 introduces outline text, replacing high contrast text, which draws a larger contrasting area around text to greatly improve legibility, along with new AccessibilityManager APIs to allow your apps to check or register a listener to see if this mode is enabled.

    side-by-side screenshots of a Pixel device showing text with enhanced contrast before and after Android 16's new outline text accessbility feature

    Text with enhanced contrast before and after Android 16’s new outline text accessibility feature

    Get your apps, libraries, tools, and game engines ready!

    If you develop an SDK, library, tool, or game engine, it’s even more important to prepare any necessary updates now to prevent your downstream app and game developers from being blocked by compatibility issues and allow them to target the latest SDK features. Please let your developers know if updates to your SDK are needed to fully support Android 16.

    Testing involves installing your production app or a test app making use of your library or engine using Google Play or other means onto a device or emulator running Android 16. Work through all your app’s flows and look for functional or UI issues. Review the behavior changes to focus your testing. Each release of Android contains platform changes that improve privacy, security, and overall user experience, and these changes can affect your apps. Here are several changes to focus on that apply, even if you aren’t yet targeting Android 16:

      • Broadcasts: Ordered broadcasts using priorities only work within the same process. Use another IPC if you need cross-process ordering.
      • ART: If you use reflection, JNI, or any other means to access Android internals, your app might break. This is never a best practice. Test thoroughly.
      • 16KB Page Size: If your app isn’t 16KB-page-size ready, you can use the new compatibility mode flag, but we recommend migrating to 16KB for best performance.

    Other changes that will be impactful once your app targets Android 16:

    Get your app ready for the future:

      • Local network protection: Consider testing your app with the upcoming Local Network Protection feature. It will give users more control over which apps can access devices on their local network in a future Android major release.

    Remember to thoroughly exercise libraries and SDKs that your app is using during your compatibility testing. You may need to update to current SDK versions or reach out to the developer for help if you encounter any issues.

    Once you’ve published the Android 16-compatible version of your app, you can start the process to update your app’s targetSdkVersion. Review the behavior changes that apply when your app targets Android 16 and use the compatibility framework to help quickly detect issues.

    Get started with Android 16

    Your Pixel device should get Android 16 shortly if you haven’t already been on the Android Beta. If you don’t have a Pixel device, you can use the 64-bit system images with the Android Emulator in Android Studio. If you are currently on Android 16 Beta 4.1 and have not yet taken an Android 16 QPR1 beta, you can opt out of the program and you will then be offered the release version of Android 16 over the air.

    For the best development experience with Android 16, we recommend that you use the latest Canary build of Android Studio Narwhal. Once you’re set up, here are some of the things you should do:

    Thank you again to everyone who participated in our Android developer preview and beta program. We’re looking forward to seeing how your apps take advantage of the updates in Android 16, and have plans to bring you updates in a fast-paced release cadence going forward.

    For complete information on Android 16 please visit the Android 16 developer site.



    Source link