# Google Play Google Play is a Google-provided service and platform for distributing apps, games, and other digital content, with tools and services for developers to manage app releases and performance. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Elevating app quality: Reducing memory usage and improving device migration DevFeed: [Elevating app quality: Reducing memory usage and improving device migration]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-26T17:00:00Z Content type: news Language: en Sources: [Android Developers Blog]() Topics: [Android](), [Google Play](), [Optimization](), [Mobile]() Tags: [android](), [google-play](), [memory](), [onboarding](), [optimization]() ### AI overview Google Play is introducing Android app and game quality requirements covering memory footprint, code optimization, and secure device-migration login. The article describes new performance thresholds and Play Console tools intended to help developers identify and address excessive memory use. ### Source excerpt Posted by Raghavendra Hareesh Pottamsetty, GM, Google Play Developer & Monetization Maintaining a healthy Android ecosystem is a shared commitment where every app and game has a role to play. To help you deliver the premium experiences users expect, Google Play is introducing two new quality requirements: one focused on reducing app memory footprint, and another on providing a secure, seamless device migration experience. First, to help developers navigate industry-wide hardware constraints and Android's broader memory limits, Google Play is establishing new performance thresholds. Second, as part of our broader commitment to elevate app quality, we are introducing a new onboarding standard to simplify and secure login during device upgrades. Reducing app memory usage and optimizing code The mobile industry is navigating significant hardware supply constraints that are altering device memory availability that over time can negatively impact the user experience. Android is addressing this challenge head-on with broader memory limits that aim to protect the overall user experience from apps using excess memory and causing system-wide slowdowns. Building on this, today Google Play is establishing performance thresholds to help developers ensure their apps continue to deliver the premium experience users expect. This includes new thresholds across dynamic memory usage, bitmap usage, and code optimization to prevent unexpected on-device performance throttling and app terminations. Dynamic memory usage (anonymous RSS + swap): This tracks the memory used for your app's private data storage, including both active and compressed memory. It excludes files stored on the device, such as code or assets. We will assess this usage across different app states (like when your app is in use or running in the background) and device performance categories. Bitmap memory usage: This evaluates the memory consumed by bitmaps. While bitmaps occupy memory when your app is in the foreground, ## Ensuring Safety in the Generative AI Ecosystem: Protecting Users from Non-Consensual Intimate Content DevFeed: [Ensuring Safety in the Generative AI Ecosystem: Protecting Users from Non-Consensual Intimate Content]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-08-25T17:00:00Z Content type: article Language: en Sources: [Android Developers Blog]() Topics: [ai safety](), [Generative AI](), [Google Play](), [trust & safety](), [LineageOS]() Tags: [ai](), [ai-safety](), [generative-ai](), [google-play](), [policy](), [safety](), [testing](), [trust-safety]() ### AI overview Google Play outlines safety requirements and safeguards for generative AI apps to help prevent non-consensual intimate imagery and other harmful content. The guidance covers app-lifecycle reviews, guardrail visibility, adversarial testing, and Android safety practices. ### Source excerpt Posted by Ron Aquino, Senior Director, Trust & Safety, Chrome, Android, and Play At Google Play, user safety and developer success go hand in hand. We continue to see growth in apps with AI generated features, and indeed, adding generative AI into your apps is a great way to unlock incredible creative possibilities. However, AI features also bring new safety challenges - such as the rise of AI-facilitated generation of non-consensual intimate imagery (NCII). Google Play's policies prohibit the facilitation, creation, or distribution of non-consensual sexual content. Harmful applications designed to target, harass, or exploit individuals have absolutely no place on Google Play, and we are committed to enforcing our policies to keep the store a safe space for developers to thrive. We know that the vast majority of you are dedicated to building positive, ethical tools. To protect both your hard work and our shared user base, we are investing heavily in platform protections, technical defenses, and developer resources to stop abuse. How we're safeguarding our shared ecosystem Protecting the platform is a continuous effort. Bad actors attempt to exploit distribution channels, monetization paths, and model boundaries. To help keep the ecosystem fair and safe, we've put a multi-layered defense strategy in place: Safeguards across the app lifecycle: Generative AI features are dynamic and can be less predictable, so safety isn't just a one-time check when you submit your app. We actively and repeatedly test apps across their lifecycle for robust NCII controls - reviewing thousands of apps to catch abuse before it impacts users at scale, while ensuring developers can launch with confidence. Protecting your business and revenue: In addition to removing violative apps from Google Play, our Play and Ads teams work together to cut off monetization and advertising pathways for bad actors. Apps that are suspended or removed for attempting to generate or monetize harmful content suc ## Delivering safer, age-appropriate experiences on Google Play DevFeed: [Delivering safer, age-appropriate experiences on Google Play]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-07-29T13:00:00Z Content type: release Language: en Sources: [Android Developers Blog]() Topics: [Google Play](), [API](), [Google](), [App](), [Availability]() Tags: [api](), [app](), [australia](), [availability](), [brazil](), [canada](), [developers](), [features](), [google](), [google-play](), [privacy](), [safety]() ### AI overview Google Play is expanding the privacy-preserving Play Age Signals API to all Play developers globally. After existing availability in Brazil, the rollout will begin in Australia and Canada and later reach users worldwide, allowing parents and adults to share age ranges with apps so developers can tailor safety experiences and content. ### Source excerpt Posted by Paul Feng, VP of Product Management, Google Play Providing a safe online experience and protecting users from harm is a top priority at Google Play. We take this responsibility seriously and have been investing continuously to offer baseline protections on our platform while also empowering parents with the tools they need to make decisions for their families. Importantly, we also want to empower Play developers with the capabilities to deliver age-appropriate experiences based on their app's content. To support this, today, we are taking another big step in our ongoing partnership with parents and developers by announcing the expansion of the Google Play Age Signals API to all Play developers globally. Building on current availability in Brazil, we will expand this experience first to users in Australia and Canada by mid-August, with a full global rollout to all users later this year. Empowering developers to create age-appropriate experiences The Play Age Signals API is a privacy-preserving tool that puts parents in the driver's seat allowing them to share their child's age range (e.g. 16-17) directly with apps. It also enables adults to easily share their age when prompted by the app developer. In turn, developers receive the signals they need to tailor their own in-app safety experiences and content for users in an age-appropriate way. We want to give developers the ability to choose the right protections for the nature of their app. A weather app, for example, shouldn't need the same safety settings as entertainment or media apps. Rather than enforcing one-size-fits-all rules, we give developers the flexibility to choose how they integrate safety signals. With this reliable signal, you retain complete agency to tailor your app's content, features, and settings to match your audience. Users have a choice to share their age range in a privacy-friendly way Simplifying controls for parents Parents shouldn't have to manage complex safety settings across do ## Store Submissions As Code: App Store, Google Play, And Huawei AppGallery DevFeed: [Store Submissions As Code: App Store, Google Play, And Huawei AppGallery]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-13T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [App](), [Google Play](), [Tooling](), [Git](), [Code]() Tags: [app](), [code](), [git](), [google-play](), [huawei](), [tooling]() ### AI overview The article presents automated store submissions for Codename One apps. Its build pipeline uploads binaries and release metadata to the App Store, Google Play, and Huawei AppGallery, while versioning store listings in Git. It also explains the manual setup that remains necessary for app records, privacy and content-rating questionnaires, pricing, and in-app purchases. ### Source excerpt One-click delivery to the App Store, Google Play, and Huawei AppGallery, with your listing versioned in git and pushed with mvn cn1:metadata-push. ## Promies: Managing and Distributing Promo Codes for Android Apps DevFeed: [Promies: Managing and Distributing Promo Codes for Android Apps]() Original publisher: [Read original article]() Author: Mike Yerou Published: 2026-05-21T12:24:10Z Content type: article Language: en Sources: [Rock and Null]() Topics: [App](), [android-apps](), [Google Play]() Tags: [android](), [android-apps](), [app](), [customizable](), [google-play](), [ios](), [promotion]() ### AI overview Promies is a system for organizing, distributing, and tracking promo codes for Android app giveaways. It uses batches and dedicated promotion URLs, with options such as email verification and pricing displays. ### Source excerpt A smarter way to manage and distribute your app promo codes with the all-new Promies. Effortlessly build customizable promotion pages, protect your codes from bot abuse, and get free organic exposure to kickstart your app's growth. ## Android 15 and 16 are now live on Maestro Cloud DevFeed: [Android 15 and 16 are now live on Maestro Cloud]() Original publisher: [Read original article]() Author: Manu Armani Published: 2026-05-21T12:00:00Z Content type: release Language: en Sources: [mobile.dev - Medium]() Topics: [Android](), [Mobile Testing](), [Testing](), [Google Play](), [releases]() Tags: [android](), [android-16](), [google-play](), [maestro](), [mobile-testing](), [pixel](), [releases](), [testing]() ### AI overview Maestro Cloud now supports automated mobile tests on Android 15 and Android 16. The release adds five device profiles, including pixel_6_stock, with configurations aligned to Android Studio defaults to improve local-to-cloud parity. ### Source excerpt Maestro Cloud now supports automated mobile testing on Android 15 and Android 16, with new Pixel device profiles including Pixel 9, Pixel 9 Pro XL... ## A tool for generating Google Play feature graphics DevFeed: [A tool for generating Google Play feature graphics]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2026-05-07T13:41:05Z Content type: release Language: en Sources: [Effective Android]() Topics: [Google Play](), [App](), [Google](), [Publishing]() Tags: [app](), [color](), [feature](), [generate](), [google-play](), [publishing]() ### AI overview The article introduces a tool for generating Google Play feature graphics. Users provide an app name and brief description, then choose a brand color. ### Source excerpt Introducing the fastest way to generate feature graphic for Google Play out there 🔥 ## Monitoring Android Vitals with the Play Developer Reporting API DevFeed: [Monitoring Android Vitals with the Play Developer Reporting API]() Original publisher: [Read original article]() Author: Julien Salvi Published: 2026-03-19T12:41:51Z Content type: tutorial Language: en Sources: [Stories by Julien Salvi on Medium]() Topics: [Android](), [API](), [Google Play](), [Gradle](), [CI/CD Pipeline](), [Google Cloud Platform (GCP)](), [Slack]() Tags: [aircall](), [android](), [android-app-development](), [anr](), [api](), [ci-cd-pipeline](), [crash](), [google-play-developer](), [gradle](), [reporting](), [slack]() ### AI overview This tutorial explains how Aircall uses the Google Play Developer Reporting API in a Gradle task to retrieve Android Vitals, including ANR and crash metrics, and deliver daily health reporting to Slack. It covers metric-set queries, timeline aggregations, service-account authentication, data modeling, and health thresholds. ### Source excerpt At Aircall, we built an automated reporting tool that fetches our Android Vitals metrics thanks to the Play Developer Reporting API and delivers a daily health dashboard straight to Slack. All of this powered by a simple Gradle task. Discovering the API The Google Play Developer Reporting API gives programmatic access to the same quality metrics you see in the Google Play Console. It covers the core Android Vitals: ANR rate, crash rate, slow start rate, and stuck background wakelocks, the signals Google uses to determine whether your app meets the bad behavior thresholds. The API is organized around metric sets that you query with a timeline specification. Each metric set returns daily, 7-day, and 28-day user-weighted aggregates, giving you the full picture from short-term regressions to long-term trends. The key advantage over scraping the Console UI is that you can automate the entire flow and integrate it into your existing CI/CD pipeline. You will find the complete API reference in the official documentation. Build with Play VitalsSetting up the dependency We chose to implement this as a Gradle task inside our build-logic module. This keeps the reporting logic close to the project without polluting the app code. First, let's add the dependency: # libs.versions.toml googleApiReporting = "v1beta1-rev20230803-2.0.0" buildLogic-plugin-google-play-developer-reporting = { module = "com.google.apis:google-api-services-playdeveloperreporting", version.ref = "googleApiReporting" } Which can then be added to the build.gradle.kts of your build-logic module: dependencies { // API to get Google Play store vitals metrics implementation(libs.buildLogic.plugin.google.play.developer.reporting) }Authenticating with a Service Account To access the API, you need a Google Cloud Service Account with the Play Developer Reporting scope. We pass the credentials as an environment variable to keep secrets out of the repository. The Reporting client initializes the API with these credentia ## get12testers.com Helps Android Developers Meet Google Play's 12-Testers-for-14-Days Requirement DevFeed: [get12testers.com Helps Android Developers Meet Google Play's 12-Testers-for-14-Days Requirement]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2026-03-14T13:57:35Z Content type: release Language: en Sources: [Effective Android]() Topics: [Android](), [Google Play](), [App]() Tags: [android](), [days](), [free](), [google-play]() ### AI overview The article introduces get12testers.com, a credit-based platform where Android developers test one another's apps to help meet Google Play's requirement for 12 testers over 14 continuous days. It describes checkpoints, credits, testing reports, and pre-filled production access form answers. ### Source excerpt A platform where Android devs help other Android devs to overcome this hard requirement from the Google Play console. ## Keeping Google Play & Android app ecosystems safe in 2025 DevFeed: [Keeping Google Play & Android app ecosystems safe in 2025]() Original publisher: [Read original article]() Author: Edward Fernandez (noreply@blogger.com) Published: 2026-02-19T17:00:00Z Content type: article Language: en Sources: [Google Online Security]() Topics: [Google Play](), [Google](), [Android](), [Artificial Intelligence](), [Malware](), [data]() Tags: [2025](), [ai](), [android](), [android-security](), [app-ecosystem](), [data](), [google](), [google-play](), [google-play-protect](), [malware](), [none](), [safety]() ### AI overview Google describes its 2025 efforts to protect the Google Play and Android app ecosystems, including preventing more than 1.75 million policy-violating apps from being published, banning over 80,000 harmful developer accounts, and expanding AI-assisted detection and privacy protections. ### Source excerpt Posted by Vijaya Kaza, VP and GM, App & Ecosystem Trust The Android ecosystem is a thriving global community built on trust, giving billions of users the confidence to download the latest apps. In order to maintain that trust, we're focused on ensuring that apps do not cause real-world harm, such as malware, financial fraud, hidden subscriptions, and privacy invasions. As bad actors leverage AI to change their tactics and launch increasingly sophisticated attacks, we've deepened our investments in AI and real-time defenses over the last year to maintain the upper hand and stop these threats before they reach users. Upgrading Google Play's AI-powered, multi-layered user protections We've seen a clear impact from these safety efforts on Google Play. In 2025, we prevented over 1.75 million policy-violating apps from being published on Google Play and banned more than 80,000 bad developer accounts that attempted to publish harmful apps. These figures demonstrate how our proactive protections and push for a more accountable ecosystem are discouraging bad actors from publishing malicious apps, while our new tools help honest developers build compliant apps more easily. Initiatives like developer verification, mandatory pre-review checks, and testing requirements have raised the bar for the Google Play ecosystem, significantly reducing the paths for bad actors to enter. User safety is at the core of everything we build. Over the years, we've continually introduced ways to help users stay safe and make informed app choices -- from parental controls to data safety transparency and app badges. We're constantly improving our policies and protections to encourage safe, high-quality apps on Google Play and stop bad actors before they cause harm. Apps on Google Play undergo rigorous reviews for safety and compliance with our policies. Last year, we shared that Google Play runs over 10,000 safety checks on every app we publish, and we continue to check and recheck apps after they'v ## Now in Android #120 DevFeed: [Now in Android #120]() Original publisher: [Read original article]() Author: Daniel Galpin Published: 2025-08-06T21:01:41Z Content type: article Language: en Sources: [Android Developers - Medium]() Topics: [Android](), [Beta channel](), [Android Studio](), [Artificial Intelligence](), [Google Play](), [CI/CD](), [Image]() Tags: [agentic-ai](), [android](), [android-development](), [android-studio](), [androidcanary](), [canary-release](), [continuous-integration](), [developer-preview](), [featured](), [google-play](), [now-in-android](), [pixel]() ### AI overview Now in Android #120 is a roundup of Android development updates covering the new Canary release channel, Agent Mode in Android Studio, Google Play changes including 16 KB Page Size requirements, Play Games updates, Android 16 devices, and Compose tips. ### Source excerpt Canary Channel, Agentic AI in Android Studio, 16 KB Pages, Policy Changes, Compose Tips, Play Games Welcome to Now in Android, your ongoing guide to what's new and notable in the world of Android development. This edition features the Android platform Canary Channel, the first release of Agentic AI in Android Studio, Play updates including 16 KB Page Size requirements and other policy changes, new capabilities around one-time purchases, Play Games Services v2, and Google Play Games on PC, I/O recaps on AI and dev productivity, next gen Samsung devices running Android 16, Compose tips, and more. https://medium.com/media/2034f6e8beea3e321d4483d4ee77ebdf/hrefhttps://medium.com/media/0247cb404c27e0b8725bc258c35923bc/href Most of the content of this post is available in the form of a video or podcast, so feel free to watch or listen rather than read on. (Or do all three to help you remember! There won't be a quiz.) Evolving Android's early-access programs: Introducing the Canary channel 🐦 Android has introduced a new Canary release channel for its early-access programs, replacing the previous developer preview model. This channel provides earlier and more consistent access to in-development platform features throughout the year. The new Canary channel offers continuous, rolling over-the-air (OTA) updates for supported Pixel devices, addressing previous limitations where previews required manual flashing and the preview program ended once a platform version reached Beta, requiring manual flashing to enter it again for the next cycle. You can use the Canary channel to: Access new features and potential behavior changes in their earliest stages. Integrate builds into your Continuous Integration (CI) systems to identify app compatibility issues early. Download Canary SDKs through the SDK Manager and access builds via the Android Studio Canary channel for development and testing. The Canary channel operates in parallel with the existing Beta program. Canary builds are bleedin ## How to verify a Google Play account without publicly exposing a home address and phone number DevFeed: [How to verify a Google Play account without publicly exposing a home address and phone number]() Original publisher: [Read original article]() Author: Jake Lee Published: 2025-01-19T00:00:00Z Content type: tutorial Language: en Sources: [Jake Lee's Programming Blog]() Topics: [Google Play](), [account](), [App](), [Android](), [console]() Tags: [android](), [androiddev](), [app](), [company](), [google-play](), [how-to](), [payments](), [privacy](), [verification]() ### AI overview This tutorial explains how a Google Play developer can avoid publicly exposing a home address and phone number during verification. It describes forming a company with a forwarding address, creating a new Organisation Google Play profile, verifying it with the company's information, and transferring apps and associated services. ### Source excerpt In 2023, Google began requiring verification for Google Play, especially if earning any money. Unfortunately, this required publicly exposing your home address and phone number! Here's how to earn money without revealing this info. ## Bloco's 2024 Android app development update and return to client work DevFeed: [Bloco's 2024 Android app development update and return to client work]() Original publisher: [Read original article]() Author: Sérgio Published: 2025-01-09T18:12:32Z Content type: opinion Language: en Sources: [Blog - Bloco]() Topics: [android-apps](), [Android](), [Google Play](), [QR Code](), [App]() Tags: [about](), [android](), [android-apps](), [app](), [dependencies](), [google-play](), [performance](), [qr-code](), [update]() ### AI overview Bloco describes its 2024 shift toward developing Android apps, including the release of a Caderno remake and the launch of QR Friend. The company also fixed bugs, updated dependencies, improved performance, experimented with Google Play listings, and returned to client work while continuing to invest in its apps. ### Source excerpt You may have noticed we've been sharing less about us. At the end of 2023 we decided to shake things up at Bloco. ## Improving an Android app's Google Play rating with in-app review prompts DevFeed: [Improving an Android app's Google Play rating with in-app review prompts]() Original publisher: [Read original article]() Author: Jake Lee Published: 2024-12-26T00:00:00Z Content type: article Language: en Sources: [Jake Lee's Programming Blog]() Topics: [Android](), [Google Play](), [App](), [Library](), [Google]() Tags: [android](), [app](), [google](), [google-play](), [in-app-review](), [kotlin](), [library](), [play-store](), [reviews](), [time]() ### AI overview This article describes how the Seatfrog app's Google Play rating improved after stability work reduced one-star reviews and an in-app review prompt made it easier for satisfied users to submit ratings. It also discusses using Google Play Console ratings data and per-version averages to assess the results. ### Source excerpt I recently worked on an app, Seatfrog, that had been rated between 1 and 2 stars for months, despite no major issues. The solution? In-app rating prompts! ## Use Google Play Instant To Handle Deep Links -- A Real World Scenario DevFeed: [Use Google Play Instant To Handle Deep Links -- A Real World Scenario]() Original publisher: [Read original article]() Author: Mehdi Satei Published: 2024-11-07T12:29:53Z Content type: tutorial Language: en Sources: [Volvo Cars Engineering - Medium]() Topics: [Google Play](), [App](), [Authentication](), [account]() Tags: [account](), [android](), [app](), [apps](), [authentication](), [deep-link-android](), [google](), [google-play](), [google-play-instant]() ### AI overview This developer article describes the deep-linking and authentication challenges in the Volvo Cars App's co-driving invitation flow. It explains the intended user journey when recipients have the app installed, are signed in, lack an account, or need to install the app from Google Play. ### Source excerpt Use Google Play Instant To Handle Deep Links -- A Real World ScenarioDiving Deep into Deep Linking with Volvo Cars App Picture this: You've just settled into the driver's seat of your brand-new Volvo car. You swiftly install the Volvo Cars Application, set up an account, and link your car. The experience is exhilarating, and you can't wait to share the same experience and let your partner or your children to co-drive and relish the same thrill. With Volvo Cars App you can do this now! If you're a Volvo car owner, you can now generate a co-drive invitation link, send it over, and once they tap on it, they're all set. From a user's perspective, it sounds dreamy. But, if you switch the lens to that of a developer building this feature, the narrative takes a rather, let's say, 'complex' turn. Tapping on the generated co-drive invitation link is something that we know as deep link. Deep linking is the art of taking a user directly to a particular screen inside the app via a universal URL (a.k.a App Link). It sounds straightforward, but implementing it can give even seasoned developers a run for their money. One significant speed bump in many apps is authentication. Before accessing content, in most cases, a user needs to be authenticated. So, when clicking on the app link, the user needs to have the app installed and be signed in, and only then can the app navigate them directly to the specific content. Now, throw in the unpleasant scenario of the user not having an account, and the plot thickens. The app must intelligently handle the sign-up dance before gracefully resuming the deep link dance. Despite being a bit challenging, when the user taps on a deep link, Volvo Cars App could handle the authentication flow. But at Volvo Cars, we also throw the curveball of "Can we deliver a great user experience for a co-driving scenario, with the generated deep link for the users who don't have our app installed?" If a user taps on a deep link without having the app installed, gui ## Introducing our new QR Friend app DevFeed: [Introducing our new QR Friend app]() Original publisher: [Read original article]() Author: Sérgio Published: 2024-10-17T16:33:21Z Content type: release Language: en Sources: [Blog - Bloco]() Topics: [QR Code](), [App](), [Android](), [Google Play](), [Risk]() Tags: [android](), [app](), [dark-mode](), [google-play](), [projects](), [qr-code](), [risk]() ### AI overview Bloco released QR Friend, an Android app for scanning QR codes without ads or accounts. It supports WiFi, contact, GPS location, and barcode scans, with scan history, favorites, optional premium features, and link safety checks using Google's Web Risk service. ### Source excerpt We released a new app for scanning QR codes: QR Friend. ## How to publish a Kotlin Multiplatform Android app on Play Store with GitHub Actions DevFeed: [How to publish a Kotlin Multiplatform Android app on Play Store with GitHub Actions]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2024-04-30T00:00:00Z Content type: tutorial Language: en Sources: [Posts on Marco Gomiero]() Topics: [Kotlin Multiplatform](), [GitHub Actions](), [Android](), [Google Play](), [GitHub]() Tags: [android](), [github](), [github-actions](), [how-to](), [kotlin](), [kotlin-multiplatform](), [play-store](), [releases]() ### AI overview A tutorial showing how to use GitHub Actions to publish a Kotlin Multiplatform Android app to Google Play. It covers release triggers based on platform-specific tags and the setup of the repository, JDK, and Gradle, including encrypted Gradle configuration caching. ### Source excerpt SERIES: Publishing a Kotlin Multiplatform Android, iOS, and macOS app with GitHub Actions. Part 1: How to publish a Kotlin Multiplatform Android app on Play Store with GitHub Actions Part 2: How to publish a Kotlin Multiplatform iOS app on App Store with GitHub Actions Part 3: How to publish a Kotlin Multiplatform macOS app on GitHub Releases with GitHub Actions How to publish a Kotlin Multiplatform macOS app on App Store with GitHub Actions It's been almost a year since I started working on FeedFlow, an RSS Reader available on Android, iOS, and macOS, built with Jetpack Compose for the Android app, Compose Multiplatform for the desktop app, and SwiftUI for the iOS app. ## Testing with Accessibility Scanner DevFeed: [Testing with Accessibility Scanner]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2024-02-16T03:38:54.088000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Testing](), [Android](), [App](), [Google Play](), [Flutter](), [React Native](), [PWA]() Tags: [accessibility](), [accessibility-testing](), [android](), [flutter](), [google-play](), [pwa](), [react-native](), [test-automation](), [testing]() ### AI overview This tutorial explains how to use Accessibility Scanner for semi-automated accessibility testing of Android apps. The tool can identify issues involving content labels, touch target size, clickable items, and text and image contrast, but it cannot detect every accessibility problem, so manual testing remains necessary. It can be used with native Android apps, Flutter and React Native apps, and PWAs. ### Source excerpt When I talk about accessibility with Android developers, I often hear that some easy-to-use tests should automatically catch every possible accessibility issue. And I get it. That would make the whole topic of accessibility so much easier and straightforward. But the truth is that automated testing only catches some things. Studies suggest that the maximum percentage of caught accessibility issues is 40-50%. Deque, the company that develops the aXe accessibility tool, claims that the number is 57% in their study of automated accessibility tools. These studies have been performed with websites, but based on my experience, I have no reason to believe that the number would be higher on Android. So manual testing is always needed. But for that 40-57% (or whatever the exact number is on Android accessibility testing), there are some tools to use. One of them is Accessibility Scanner, and in this blog post, I'll discuss how to test your app with it. Let's start with what it is. What Is Accessibility Scanner Accessibility Scanner is a helpful tool for semi-automated accessibility testing. It's an app which can catch issues from the following categories: Content labels Touch target size Clickable items Text and image contrast It also suggests how to fix some of its findings and provides more info about the issues. However, it does not find every possible accessibility issue and thus does not guarantee the accessibility of your app. Manual testing is still needed. I keep saying this because I've seen these claims so many times that "Well, our test automation didn't find any accessibility issues, so our app is accessible". One great thing is that you can use Accessibility Scanner with any Android app - it can be a native Android app or built with cross-platform technologies such as Flutter or React Native. Or it can even be a PWA - Progressive Web App. Using Accessibility Scanner Installation To use the Accessibility Scanner, you must first download it from Google Play: Acces ## How My App Won the 2nd Place in the WWCode App Deploy Hackathon DevFeed: [How My App Won the 2nd Place in the WWCode App Deploy Hackathon]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2023-12-14T04:01:52.720000Z Content type: article Language: en Sources: [Eevis Blog]() Topics: [Hackathon](), [Android](), [Development](), [Google Play](), [PaLM API]() Tags: [android](), [app](), [code](), [google-play](), [hackathon](), [palm-api]() ### AI overview The author describes participating in the Women Who Code App Deploy Hackathon, where the goal was to build an Android app using Google APIs. The author says the app won second place and explains the planning behind an app for documenting work accomplishments and generating text for performance reviews. The app had not yet been published on Google Play at the time of writing. ### Source excerpt A few weeks ago, I participated in my first mobile hackathon; it was so much fun! This hackathon was also the first more traditional (so, just over the weekend) for me and the second in general. The first was the Github Actions hackathon in 2020, organized by Dev.to, and it spanned throughout weeks. The hackathon I participated in was App Deploy Hackathon from Women Who Code, and the goal was to build an Android app and use any of the Google APIs available. WWCode organized the hackathon in partnership with Google Play. I can already share that I won second place in the hackathon! You can read more from Women Who Code's Winner announcement blog post. I'll share my journey from planning to submission in this blog post. You'll also find links to the code and a video demonstrating the app. I haven't yet published the app in Google Play because there was not enough time to jump through all the hoops, but I will probably release it sometime at the beginning of next year. Planning for the Hackathon I registered for the hackathon about two weeks before the event. Those two weeks were hectic, but I had some time to think about the hackathon app idea. I spent quite a bit of time with the Google API Explorer and tried to come up with some ideas. I came up with two more concrete ideas: a menstruation-tracking app with the features I'd love to have with Google Health Connect, or an app for documenting accomplishments and wins at work and generating a text for a performance review cycle from those items. That second one would use the PaLM API (or so I thought). When the start of the hackathon came closer, I decided to go with the second idea. I researched and had my building plan (or the general lines) ready for action. The Story Behind the App Idea The app idea was something that had been on my mind for a long, long time. Someone shared Julia Evans' blog post "Get your work recognized: write a brag document" a long time ago, and I loved the idea. I have often started writing my ## Presenting Cabinet to the World! DevFeed: [Presenting Cabinet to the World!]() Original publisher: [Read original article]() Author: Cláudia Published: 2022-11-30T17:17:35Z Content type: article Language: en Sources: [Blog - Bloco]() Topics: [App](), [Android](), [Jetpack Compose](), [Mobile](), [Google Play](), [Ktor](), [User experience (UX)](), [Template]() Tags: [android](), [android-development](), [app](), [design](), [development](), [directory](), [games](), [google-play](), [internship](), [jetpack-compose](), [ktor](), [launch](), [open-source](), [template]() ### AI overview Bloco introduces Cabinet, a paid Android app directory designed to help users discover hand-picked apps and alternatives without download-based rankings or false marketing. The article describes its categories, launch results, business goals, and implementation with technologies including Jetpack Compose, Paging 3, DataStore, Ktor, and Coil. ### Source excerpt Presenting Cabinet, Bloco's new app! Cabinet helps you discover amazing new apps and alternatives to the ones you use every day. ## About the Android Makers app, security and google-services.json DevFeed: [About the Android Makers app, security and google-services.json]() Original publisher: [Read original article]() Author: Martin Bonnin Published: 2022-05-06T13:45:38Z Content type: article Language: en Sources: [Martin Bonnin's blog]() Topics: [Android](), [API keys](), [Security](), [Firebase](), [APK](), [Android Studio](), [Google](), [Google Play]() Tags: [android](), [android-studio](), [api](), [apk](), [firebase](), [google-cloud](), [google-play](), [security]() ### AI overview The article explains why an Android API key in google-services.json is accessible in an app and can be retrieved from a published APK. It discusses the apparent contradiction between that accessibility and warnings about exposing the key in GitHub or Google Play. ### Source excerpt Android Makers is over! With over 650 participants and 50 sessions over 2 days in Paris, it was a lot of fun! It was nice to see everyone in person again and discuss all the Android things (and 🍻 too)! This year, we decided to rewrite the Android a... ## Diagnosing Android ANRs with Runtime Traces and APM Data DevFeed: [Diagnosing Android ANRs with Runtime Traces and APM Data]() Original publisher: [Read original article]() Author: Amanjeet Singh Gurtatta Published: 2022-01-21T17:52:38Z Content type: tutorial Language: en Sources: [Amanjeet Singh]() Topics: [Android](), [observability](), [Application Performance Management (APM)](), [debug](), [Traces](), [Crashlytics](), [Google Play]() Tags: [android](), [android-vitals](), [anr](), [apm](), [crashlytics](), [debug](), [firebase](), [google-play](), [mobile-performance](), [trace]() ### AI overview This article explains why Android Application Not Responding events are difficult to reproduce and diagnose. It describes how the Android runtime responds with SIGQUIT and ANR traces, then introduces approaches APM libraries can use to collect ANR data, including watchdog monitoring. ### Source excerpt Solving the ANRs Riddle on Android ## Reducing Android app size in practice at LinkedIn DevFeed: [Reducing Android app size in practice at LinkedIn]() Original publisher: [Read original article]() Author: Chao Zhang Published: 2021-11-23T16:53:49Z Content type: tutorial Language: en Sources: [Stories by Chao Zhang on Medium]() Topics: [Android](), [App](), [Google Play](), [APK](), [modules](), [Azure]() Tags: [android](), [android-app-bundle](), [android-app-development](), [apk](), [app-size](), [azure](), [google-play](), [jetpack-compose](), [modules](), [optimization](), [sdk]() ### AI overview This article explains how LinkedIn reduced Android app download size in practice. It distinguishes download, install, and storage sizes, then discusses Android App Bundle optimizations and Play Feature Delivery, including their use with the Azure Communication Services SDK for Native Video Meeting. ### Source excerpt Photo: Daniel Romero from Unsplash App size is a key metric impacting user acquisition and retention: If the app is too large to download, users may skip installation or cancel the installation during downloading; if the app takes too much storage space after use, users may choose to uninstall. There are also different measurements of Android app sizes: Download size: The compressed size of the release downloaded by users at install time. Install size: The approximate size of the recent release on the user's device after installation, but before the app is opened for the first time. Space used shown in Storage Settings: Sizes of files under cache directory and other directories under /data/data/com.app.package.name This post mainly focuses on the download size. This is displayed directly in the Google Play console for developers, and also displayed in the about this app section in Play Store. The official documentation on Android Developers already covers many different ways to optimize the app size. However, in this blog post, we would like to emphasize some of the less known yet powerful techniques to reduce app size. These techniques helped LinkedIn to minimize its app size in recent years. Play Feature Deliverya.k.a Dynamic Features, Dynamic Modules, or On-Demand modules Android App Bundle, as a publishing format in Google Play, was recently escalated to the requirement for publishing new applications in August 2021. The app bundle is used to generate multiple optimized APKs. Then the user will only download the specific APK set optimized for their device. The download size savings come from: ABI libraries that do not match the device's processor architecture Resource files that do not match screen density Language resources that do not match the user's device language Application size savings from Android App Bundle (Google I/O 2018) -- https://youtu.be/flU42CTF3MQ Migrating to an Android App Bundle should be a streamlined process. At least this was the case for ## How I made beautiful screenshots for Google Play (Developer experience) DevFeed: [How I made beautiful screenshots for Google Play (Developer experience)]() Original publisher: [Read original article]() Author: Yahor Urbanovich Published: 2021-07-10T11:24:12Z Content type: tutorial Language: en Sources: [Stories by Yahor Urbanovich on Medium]() Topics: [Google Play](), [Android](), [App](), [Mobile](), [pixel]() Tags: [android](), [android-studio](), [developer](), [google-play](), [google-play-developer](), [personal-experience](), [photoshop](), [play-store](), [screenshots]() ### AI overview A developer shares a workflow for creating polished Google Play screenshots, comparing device-mockup tools and online services with a do-it-yourself approach using Google Play guidelines, Photoshop, mobile tools, and Android Studio. ### Source excerpt Comparison of the initial and final result Every developer who has an application in Play Store worries about user engagement before the application install. This metric can be simply improved by adding beautiful and informative screenshots. I want to share my own experience of how I made it for my pet project. Let's begin. Originally I prepared screenshots for Google Play using a simple approach: Make a screenshot of the application Add it into Device Mockup to make it more natural Publish to Google Play For this purpose, I used Screener: https://play.google.com/store/apps/details?id=de.toastcode.screener&hl=en_US The tool is useful, contains a different amount of phone frames and manufacturers, and fully customizable. Screenshot after rendering The main lack for me that the application didn't update since 2018 and doesn't contain new Android devices, especially Google Pixel's latest model. Screener app info from Google PlayFind the other solutions. If you are lazy and don't want to spend your free time, the best way to organize screenshots is through online services. Few of them, which I have tried: https://mockups.pixeltrue.com/ 2. https://previewed.app/ 3. https://theapplaunchpad.com/ 4. https://screen.traction.one/ 5. https://www.launchmatic.app/ The main drawbacks of online services for me: To unlock more themes and functionalities you need to have paid subscription Limited customization Can't adjust the screenshot for mockup, the content cropped unexpectedly from different sides Some services focus only on iPhone or several Android devices How to deal with a problem? Do It Yourself! What we need: Official guidelines Adobe Photoshop and basic editing skills Creativity and inspiration Official Google Play guidelines: https://support.google.com/googleplay/android-developer/answer/9866151?hl=en The most important for us from the Screenshots section: Edit excess elements in the notification bar before submitting. Do not show service providers or notifications. The [Next page]()