Posted by Patricia Correa, Director, Global Developer Marketing
During the month of June we received thousands of submissions for two of our annual developer programs - the Indie Games Accelerator and the Indie Games Festival. These programs support the growth of small games studios on Google Play.
Every year we’re impressed with the art and creativity of the entries. This year was no exception. Many thanks to everyone who submitted their game.
Today, we’re announcing the finalists of the Festivals in Europe, Japan, and South Korea… drumroll, please.
Beat Workers by NaturalPad Games, France
Bird Alone by George Batchelor, United Kingdom
Cats in Time by Pine Studio, Croatia
Figment by Bedtime Digital Games, Denmark
Froglike: The Frog Roguelike by Jimjum Studios, Israel
Garson by Anastasiya Shabunia, Belarus
Gumslinger by Itatake, Sweden
Lyxo by Emoak, Austria
Psychofunk by Tommy Søreide Kjær, Norway
Railways by Infinity Games, Portugal
Sticky Terms by kamibox, Germany
Sweet Sins Superstars by Platonic Games, Spain
Tiny Robots Recharged by Big Loop Studios, Bulgaria
Tofu Drifter by Roach Games, Russia
Towers by JOX Development, Ukraine
Unholy Adventure by Dali Games, Poland
Warplane Inc by Nuclear Games, Russia
Watch Me Stream My Mental Breakdown by Ultaan Games, Poland
Woof: The Good Boy Story by CHPV.GAMES, Russia
Zen Symmetry by 8tbl, Russia
Sign up to attend the European finals.
3D Chess: NOCCA NOCCA by Curiouspark, Inc.
5colors in Nate by NekodoraSoft
Amabie san by HARAPECORPORATION Inc.
Archer Battle Online by Takuya Fujieda
Cthulhu DreamStairs by Tenyu
ElectriarCode by ELECTRIAR LABO
Escape from the Closed Circle by Hanachiru
Heart of Sengoku by ZEN APP
Leaving Two Tiles Dojo by ScreenPocket
Living in the Ending World by illuCalab.
MAKOTO WAKAIDO’s Case Files “Executioner’s Wedge” by HafHaf-Oden（Sukashiuma-LAB）
Mini Mini Farm by CoffeeBreak
MonohakobiPro by CGO
Mousebusters by Odencat
Numpurr Card Wars by Nukenin
Parasite Days by Zxima
Quantum Transport by ruccho
Super Glitter Rush by tiny cactus studio
Survivor's guilt by aso
Wolf Chess by Baton
Sign up to attend the Japanese finals.
Angel Saga by Alchemist Games Inc.
Animal Card Royale by Banjihagames
Animal Doll Shop by Funnyeve
BattleLive: Zombie&Human by PLOTRICK
Box It Up! Inc. by team TAPE
CATS & SOUP by HIDEA
Cats are Cute: Pop Time by kkiruk studio
Detective Mio by 1N1
Dicast: Rules of Chaos by BSS COMPANY
Forest Island by Nanali Studios
Frontier of Fortune by Dotomchi Games Inc.
FUNKYGUNNER by FUNKY5
Group Project Simulator! by Studio806
Gun Tactics by Gimle Games
Hybrid Warrior: Dungeon of the Overlord by Cat Lab
Metro Blossom by The Sane Studio
Portal Dungeon by Oblique Line
Rush Hour Rally by Soen Games
The Way Home by CONCODE
Titan Slayer by Touchholic
Sign up to attend the South Korean finals.
This year the three Festivals are virtual, so everyone has the chance to explore the games, meet the developers who made them, cheer them on, and be the first to hear who the winners are.
Expect plenty of fun and some very special surprises. So, don’t miss out. Sign up now to virtually attend the events showcasing the finalists from Europe, Japan, and South Korea. The events are free to attend and will all take place in the same space, so sign up to one and you will be able to teleport to all events!
If you’re interested in knowing which developers are joining the 2021 class of the Indie Games Accelerator, sign up to attend the European Festival, where we will also announce the selected developers.
Posted by Amanda Alexander, Product Manager, Android
We are excited to announce that Android Studio Arctic Fox is now available to download in the stable release channel. This latest release brings to life Jetpack Compose 1.0, Android's new toolkit for building native UI. The release also focuses on devices, including Wear OS, and helps with developer productivity, with features like a new Background Task Manager. We used your feedback to create this suite of new Android Studio features that will help empower the developer community to create high quality, modern apps across devices faster!
Note: As we announced last year, we adjusted our version numbering of Android Studio to match the year and version of the IntelliJ IDEA that Android Studio is based on, plus our own patch number. We will be using code names (in alphabetical order); the first is Arctic Fox and the next is Bumblebee (currently in canary).Android Studio Arctic Fox (2020.3.1) updates Android Studio to version 2020.3 of the IntelliJ platform which adds a slew of new features including debugger interactive hints, VCS updates, and several new code editor enhancements to speed up your workflow. Learn more.
To support rapid design of modern UI, we added additional features for Jetpack Compose. Compose Preview lets you create previews of multiple components of your Compose UI to instantly see the impact of your changes across dimensions (such as themes, screen and font sizes, and more). The Deploy Preview to device feature enables deploying snippets of your Compose code directly to a device or emulator so you can quickly test small parts of your code. If you want to dive deeper into your Layouts, we added Compose support to the Layout Inspector to help you understand how your layouts are rendered. Additionally, we added Live Editing of literals so you can instantly see your Compose code changes in previews and when running your app on an emulator or physical device without the need for compilation.
For increased device support, we built a new Wear OS pairing assistant to simplify the pairing of Wear OS emulators with physical or virtual phones. To use the newest Wear OS version, you can now access the developer preview of the Wear OS 3 system image. When you run the Wear OS emulator, you will also find added support for the Heart Rate Sensor API. For apps targeting Google TV, we added the newest Google TV Remote Control features and updated the Google TV system images to reflect the latest UI design. Additionally, we have completed the development and testing workflow for the Automotive OS by enabling the emulator to use car sensor data to simulate driving use cases. For apps targeting tablets, we have updated all templates to support landscape out of the box. Whether you are developing for small or large screen devices, we have included new features to help you keep innovating and building amazing apps.
Lastly, in an effort to boost developer productivity, we have added features to help you work more efficiently. For example, we added lint checks for Android 12 to provide guidance on building apps for the next version of Android. To help you test your code, we added an Accessibility Scanner for Layout Editor so you can more easily identify accessibility issues in your layouts and the new Test Matrix lets you view test results in real time across multiple devices in parallel. Additionally, we added preview support for Apple Silicon (arm64) hardware and extended the emulator controls for wider coverage in testing. Lastly, for debugging, the new Background Task Inspector helps you to analyze your app's background workers.
There are many enhancements to Android Studio Arctic Fox. To see the full list of changes, view the Android Studio Arctic Fox (2020.3.1) Beta release blog and release notes. You can take a look below at some highlights of the changes.
What's new in Android Studio Arctic Fox
Use the @Preview annotation to generate previews of Compose code and visualize the different configurations of multiple components (e.g. devices or themes). Compose Preview can make it simpler for you to construct a mental mapping of the composables in your code.
Compose Preview
Layout Inspector for Compose
For both apps written fully in Compose and apps with some Compose alongside Views, Layout Inspector makes it possible to get more details on your layouts and troubleshoot. For example, you will be able to see the parameters and modifiers passed to each composable. There is an option to turn on Live Updates to stream data from your device as you develop your app.
Compose Layout Inspector
Live Edit of literals
You can now quickly edit literals (strings, numbers, booleans, etc.) inline and see the immediate results on the change on screen (previews, emulator, or physical device), without having to compile.
Live Edit of Literals: edit strings and see it reflected immediately in Preview
Wear OS Pairing
The new Wear OS Pairing assistant will help walk you through the pairing process to make pairing Wear OS emulators with virtual or physical phone simple. Note that this feature assists with pairing with Wear OS 2 companion; support for Wear OS 3 will be coming soon. Learn more.
Wear OS emulator pairing assistant dialog
Phone + Watch emulators paired successful state
Background Task Inspector
You can use the new Background Task Inspector to visualize, monitor, and debug your app's background workers when using WorkManager library 2.5.0 or higher on a device running API level 26 and higher. You can access it by selecting View > Tool Windows > App Inspection from the menu bar. Learn more.
To recap, Android Studio Arctic Fox (2020.3.1) Stable includes these new enhancements & features:
Check out the Android Studio release notes, Android Gradle plugin release notes, and the Android Emulator release notes for more details.
Download
You can download the latest version of Android Studio Arctic Fox from the download page and download the Apple Silicon preview build here. If you are using a previous release of Android Studio, you can simply update to the latest version of Android Studio. If you want to maintain a stable version of Android Studio, you can run the stable release version and canary release versions of Android Studio Arctic Fox at the same time. Learn more.
We appreciate any feedback on things you like, and issues or features you would like to see. If you find a bug or issue, feel free to file an issue. Follow us -- the Android Studio development team ‐ on Twitter and on Medium.
Posted by Anna-Chiara Bellini, Product Manager, Nick Butcher, Developer Relations
Today, we're launching version 1.0 of Jetpack Compose, Android's modern, native UI toolkit to help you build better apps faster. It's stable, and ready for you to adopt in production. We have been developing Compose in the open with feedback and participation from the Android community for the last two years. As we reach 1.0, there are already over 2000 apps in the Play Store using Compose - in fact, the Play Store app itself uses Compose! But that’s not all, we have been working with a number of top app developers and their feedback and support has helped us make the 1.0 release even stronger. Square, for instance, told us that by using Compose, they can “focus on things that are unique to Square and their UI infrastructure, rather than solving the broader issue of building a declarative UI framework”. Monzo said Compose allows them to “build higher quality screens more quickly”. And Twitter summed it up nicely: “We love it! ❤️”
We designed Compose to make it faster and easier to build native Android apps. With a fully declarative approach, you just describe your UI, and Compose takes care of the rest. As app state changes, your UI automatically updates, making it a lot simpler to build UI quickly. Intuitive Kotlin APIs help you build beautiful apps with way less code, and native access to all existing Android code means you can adopt at your own pace. Powerful layout APIs and code-driven UI make it easy to support different form factors, like tablets and foldables, and Compose support is coming for WearOS, Homescreen Widgets, and more!
This 1.0 release is ready for use in production, offering key features that you need:
The fully declarative approach in Jetpack Compose radically changes how you develop UI. To support new workflows and a different way of thinking, we are delivering new tools, designed specifically for Compose, and adding support for Compose to some of our existing tooling.
The new Compose Preview, available in Android Studio Arctic Fox allows you to see your Composables in different states, light and dark theme, or different font scalings, all at the same time, making component development easier, without having to deploy a whole app to your device. Enhanced with live editing of literals, you can see updates without recompiling your project.
If you ever wished to be able to test parts of the UI on a device, without having to navigate through your app to the screen you’re working on, you will like the new Deploy Preview: just create a preview for your Composable, and deploy it on your device for fast iteration.
Layout Inspector adds support for Composables, so that you can confidently mix Compose with existing Views.
Read more about Compose support in Android Studio Arctic Fox, here.
Adopting any new framework requires evaluation, especially something as far reaching as a new UI Toolkit. To help you to make an informed decision whether it’s the right time for you we’re publishing a public roadmap to share our plans to continue to build out Jetpack Compose.
To help you get composing, we’ve prepared an extensive set of resources for you and your team:
There’s a lot to learn! The Jetpack Compose Pathway provides a step-by-step journey through key codelabs, videos and docs to help guide you.
We really believe that Jetpack Compose is a huge leap forward, making it so much faster and easier to build great UIs; we can’t wait to see what you build with it. Now that Compose is stable at 1.0, it’s time to get started; there’s nothing better than getting right to the code. Happy Composing!
Posted by Suzanne Frey, VP, Product, Android Security and Privacy
Today, we’re announcing additional details for the upcoming safety section in Google Play. At Google, we know that feeling safe online comes from using products that are secure by default, private by design, and give users control over their data. This new safety section will provide developers a simple way to showcase their app’s overall safety. Developers will be able to give users deeper insight into their privacy and security practices, as well as explain the data the app may collect and why — all before users install the app.
Ultimately, all Google Play store apps will be required to share information in the safety section. We want to give developers plenty of time to adapt to these changes, so we’re sharing more information about the data type definitions, user journey, and policy requirements of this new feature.
Images are directional and subject to change
Users will see the new summary in an app’s store listing page. It’ll share the developer’s explanation of what data an app collects or shares and highlight safety details, such as whether:
Users can tap into the summary to see details like:
In designing our labels, we learned developers appreciate when they can provide context about their data practices and more detail on whether their app automatically collects data versus if that collection is optional. We also learned that users care about whether their data is shared with other companies, and why.
The final design is subject to change as we continue working with developers and designing for the best blend of developer and user experiences.
Policy changes to support the safety section
Today we announced new user data policies designed to provide more user transparency and to help people make informed choices about how their data is collected, protected and used.
This applies to all apps published on Google Play, including Google's own apps.
We want to provide developers with plenty of time and resources to get prepared.
Target Timeline. Dates subject to change.
Starting in October, developers can submit information in the Google Play Console for review. We encourage you to start early in case you have questions along the way. The new safety section will launch for apps in Google Play in Q1 2022.
We know that some developers will need more time to assess their apps and coordinate with multiple teams. So, you’ll have until April 2022 before your apps must have this section approved. Without an approved section, your new app submission or app update may be rejected.
If your app’s information is not approved by the time we launch the safety section in Google Play to users in Q1 2022, then it will display “No information available.”
We’ll continue to share more guidance, including specific dates, over the next few months.
Thank you for your continued partnership in building this feature alongside us and in making Google Play a safe and trustworthy platform for everyone.
Posted by Krish Vitaldevara, Director, Product Management
We are always looking to make Google Play a safer and more trustworthy experience for developers and consumers. Today, we’re announcing new policy updates to bolster user control, privacy, and security.
We’re sharing our new policy for the upcoming safety section in Google Play alongside additional information, like data definitions. Learn more.
We’ve long offered users meaningful controls with advertising ID, like being able to reset their identifier at any time or opt out of allowing the identifier to be used for ads personalization. We’re continuing to add more controls this year.
As we pre-announced to developers on June 2, we’re making a technical change as part of Google Play services update in late 2021. When users opt out of interest-based advertising or ads personalization, their advertising ID will be removed and replaced with a string of zeros. As a reminder, this Google Play services change will be a phased rollout, affecting apps running on Android 12 devices starting late 2021 and expanding to all apps running on devices that support Google Play in early 2022. Also, apps updating their target API level to Android 12 will need to declare a new Google Play services permission in the manifest file in order to use advertising ID.
We will also test a new feature that notifies developers and ad/analytics service providers of user opt-out preferences to help developers implement user choice and add to existing policy restrictions on how advertising ID can be used. When a user deletes their advertising ID, developers will receive a notification so they can promptly erase advertising IDs that are no longer in use.
In addition, we’re prohibiting linking persistent device identifiers to personal and sensitive user data or resettable device identifiers. This policy adds an additional layer of privacy protection when users reset their device identifiers or uninstall apps.
And last, we’re offering a developer preview of app set ID for essential use cases such as analytics or fraud prevention. App set ID is a unique ID that, on a given device, allows you to correlate usage or actions across a set of apps owned by your organization. You cannot use app set ID for ads personalization or ads measurement. It will also automatically reset if all the developers’ apps on the device are uninstalled or none of the apps have accessed the ID in 13 months.
As we introduce app set ID for analytics and fraud prevention, we are also making changes to further enhance privacy for kids. If an app is primarily directed to children, it cannot transmit identifiers like advertising ID. If an app’s audience is both kids and adults, then it needs to avoid transmitting these identifiers for kids.
Over the next several months, we’ll share more information for a smooth transition.
Security is fundamental to enabling privacy across our platform. We’re announcing a few policy updates to help keep user data secure.
First, Google Play remains a safer ecosystem when developers actively maintain their apps. So, we will close dormant accounts if the account is inactive or abandoned after a year. This includes accounts where the developer has never uploaded an app or accessed Google Play Console in a year.
We will continue supporting developers with actively growing apps. We won’t close accounts with apps that have 1000+ installs or have in-app purchases in the last 90 days. Developers whose accounts are closed can create new ones in the future, but they won’t be able to reactivate old accounts, apps, or data.
Second, it’s important for users to have an accessible experience that is secure. So, we’re adding new requirements on how AccessibilityService API and IsAccessibilityTool can be used. These tools help build accessible experiences, which often require access to user data and device functionality. Now, all apps that use the AccessibilityService API will need to disclose data access and purpose in Google Play Console and get approval. Learn more.
As we shared earlier in July, after careful consideration of feedback from both large and small developers, we are giving developers an option to request a 6-month extension until March 31, 2022 to comply with our Payments policy.
Thank you for helping us make Google Play an even more trustworthy platform for everyone.
Posted by Madan Ankapura, Product Manager
Building on our effort to enable developers to create app experiences across navigation, parking, and charging apps via Android for Cars App Library as part of Jetpack, today we’re announcing the availability of CarHardwareManager APIs as part of version 1.1 alpha02 to get developer feedback.
CarHardwareManager can be used to query the vehicle’s hardware data, such as model and make, fuel levels and other sensors. Currently, this feature is only available for Android Auto 6.7+ in the open-testing channel. Testing this in a desktop environment requires a new version of the Desktop Head Unit which will be released separately. Stay tuned here for details on when the new version becomes available.
For the entire list of changes in alpha02, please see the release notes. To start building your app for the car, check out our updated developer documentation, car quality guidelines and design guidelines. These library features are available for testing only with the Desktop Head Unit. We will announce when these features are available to run in cars in the future.
In addition, if you are a developer of a parking app, you can now integrate with Google Assistant to enable users to talk to Google to open their favorite parking app and find parking while driving.
If you’re interested in joining our Early Access Program in the future, please fill out this interest form. You can get started with the Android for Cars App Library today, by visiting g.co/androidforcars.
Posted by Purnima Kochikar, VP Play Partnerships
Every day we work with developers to help make Google Play a safe, secure and seamless experience for everyone, and to ensure that developers can build sustainable businesses. Last September, we clarified our Payments Policy to be more explicit about when developers should use Google Play’s billing system. While most developers already complied with this policy, we understood that some existing apps currently using an alternative billing system may need to make changes to their apps, and we gave one year for them to make these updates.
Many of our partners have been making steady progress toward the September 30 deadline. However, we continue to hear from developers all over the world that the past year has been particularly difficult, especially for those with engineering teams in regions that continue to be hard hit by the effects of the global pandemic, making it tougher than usual for them to make the technical updates related to this policy.
After carefully considering feedback from both large and small developers, we are giving developers an option to request a 6-month extension, which will give them until March 31, 2022 to comply with our Payments policy. Starting on July 22nd, developers can appeal for an extension through the Help Center and we will review each request and get back to requests as soon as possible.
Check out the Help Center and the Policy Center for details, timelines, and frequently asked questions. You can also check out Play Academy or watch the PolicyBytes video for additional information.
Platform
Android Studio
Google Play
Jetpack
Kotlin
Docs
News
