ICYMI, Android Dev Summit returned last week after a four-year hiatus (Oct. 28–29), featuring over 50 sessions covering agentic development workflows (Android CLI, Agent Client Protocol support in Android Studio [i.e. Bring Your Own Agent], and declarative builds with Lightbuild), on-device and hybrid AI (Gemini Nano 4, Gemma 4, and Android MCP), our shift to a Compose-first UI architecture, and building across form factors like Googlebook and Android XR. If you couldn't make it out in person, the recorded session VODs are now live on YouTube so you can catch up on the talks relevant to your stack at your own pace—I've rounded up all of the links and descriptions by track below so everything is in one place.
Also worth noting if you'd rather skim or feed sessions straight into your coding workflow: the Android Dev Summit site is set up for agents this year:
📄 Download any talk as Markdown: Includes a summary, resource links, a speaker-labeled transcript, and code blocks in one file—drop a few into your agent and ask what changed for your app.
🗂️ Point an agent at one JSON feed: Structured metadata covering every session.
🧩 Grab theAgent Skills: Install the modular instruction sets each talk references.
If you're short on time and want to quickly catch up on the biggest announcements from ADS, start with the Android Dev Summit 2026 Keynote and check out these three recap posts on the Android Developers Blog:
Android is evolving into an intelligence system where agents like Gemini orchestrate tasks across apps. To unlock new user experiences and participate in these agentic workflows, your app must expose its core capabilities.
This session is a practical guide to integrating your app with Android's intelligence layer. We'll survey key integration paths - including on-device Android MCP, server-side MCP, and Task Automation - and provide a decision framework for choosing the right path for your use case. We'll also explore proactive experiences with Personal Context.
You will learn how to:
* Select the optimal integration path for your app's needs.
* Implement both reactive and proactive intelligence features.
* Balance performance and security in agentic integrations.
Gemma 4 brings capable, multimodal AI directly to Android devices. In this session, we'll trace how Gemma evolved into a model family built for efficiency and explore what the edge-optimized E2B and E4B models can do on-device, from vision and audio understanding to agentic function calling. We'll cover the architecture behind that efficiency, including Per-Layer Embeddings (PLE), and show how Gemma and Gemini Nano work together through AICore. You'll learn how Quantization-Aware Training (QAT) preserves model capability within 1.1–3.5 GB RAM footprints, while Multi-Token Prediction (MTP) accelerates decoding speeds 1.5x–3x for responsive, real-time experiences.
In this session, we'll explore different GenAI use cases using ML Kit APIs to understand when on-device GenAI is ideal for an app and also understand how to evaluate existing GenAI use cases to see if on-device models can satisfy their quality bar.
Building production-ready generative AI into Android apps requires more than connecting to an LLM—it demands enterprise-grade security and cost controls. In this session, discover how Firebase AI Logic empowers developers to deploy secure, budget-conscious AI experiences at scale.
We will cover from security foundations and Firebase App Check, cost management, dynamic model routing to leveraging the multimodal capabilities.
Explore how to connect your applications seamlessly to Gemini, Search and the Android intelligence system.
The new Connected Apps Platform lets you integrate your app's services directly into Gemini, AI Mode in Search, and the Android intelligence system. This session provides a practical guide to getting started. Using code examples and learning from real-life case studies, we’ll walk through the development lifecycle: building, testing, and publishing your first connected app to reach users within their AI-powered workflows.
By the end of this session, you'll be able to:
* Integrate your service with the Connected Apps Platform.
* Test your integration across different AI surfaces.
* Publish your app’s features into users' AI workflows.
Stop choosing between plug-and-play AI convenience and custom model flexibility—you can deploy both in a single, ultra-lean app without adding megabytes of binary bloat.
In this session, we’ll demonstrate how to build this exact dual-stack architecture in a single Android app. You’ll see how to leverage ML Kit for ready-to-use classical ML tasks (like doc scan) alongside LiteRT standalone in Play services for your custom computer vision or audio workloads. We’ll dive deep into how both implementation paths unite under the hood to utilize the modern LiteRT runtime, giving your app seamless, hardware-accelerated performance on CPU and GPUs with a virtually zero-byte download footprint.
Key takeaways for developers:
* Uncompromised performance: Both turnkey and custom models are hardware-accelerated automatically using the unified CompiledModel API.
* Micro-APKs: Dramatically reduce your app’s download size by offloading both the ML Kit and LiteRT runtimes to Play services.
* Hybrid integration: Master running multiple ML workflows side-by-side in production without resource conflicts.
Take your Android AI features to the next level by building autonomous on-device agents. In this session, we dive into ML Kit’s new agentic APIs, built directly on top of the direct model access APIs you already know.
Using the open-source Jetpacker app, you’ll learn how to chain multi-step actions across local data, manage stateful multi-turn sessions with isolated contexts, and wire up Android MCP to power both in-app assistants and Android system-level surfaces with a single codebase.
While large frontier models dominate the headlines, small language models (SLMs) like Gemma 4 offer low-latency, cost-effective, and fully offline intelligence to augment daily developer workflows.
This talk explores practical patterns for integrating small models into Android development, from smart task routing to cost optimization, using Gemma 4 as our primary hands-on case study to demonstrate real-world use cases and how to configure developer tools and agentic workflows.
A2UI is transitioning from web-centric components to native Android. The new Jetpack Compose renderer for A2UI v0.9 enables developers to render dynamic, LLM-generated UI natively. Instead of webviews, it leverages a Coroutine-driven actor framework, sealed-class lifecycles, and native Material 3 integration.
This session walks through the new architecture, explaining how server-driven component trees translate into reactive Compose nodes, and how built-in layout transitions handle structural updates smoothly without blocking the UI.
A racing car is a demanding environment of high speed, heat, and telemetry constraints. How can an on-device agent help process real-time vehicle data for sports and engineering applications?
This technical session explores an experimental hybrid architecture combining edge hardware and cloud agents. We'll walk through a research proof-of-concept using a Raspberry Pi to stream CAN bus telemetry, a Pixel phone running an on-device conversational agent powered by ML Kit and Gemini Nano, and an agent-to-agent (A2A) Cloud connection for post-race workflows.
Stop copy-pasting into AI chat windows and start delegating to your agent. This practical, example-driven session shows you how to level up your agentic engineering using Claude Code and the Android CLI. We will walk through a complete workflow to automate complex development tasks and ship features faster.
You will learn to:
* Optimize the token efficiency of your harness using Android CLI, Skills, Hooks and MCP.
* Offload and parallelize long-running tasks to subagents.
* Set up continuous verification loops that stop early termination and run until tests pass.
Discover what’s next for Android development across Android Studio and the terminal with Android CLI. In this session, we unveil the latest in Android Studio Canary and Stable—from AI-assisted code migrations to Compose and Agent Client Protocol (ACP) support, to Lightbuild’s declarative architecture. We’ll also dive into the latest updates to the Android CLI toolchain. Learn how you can use it to automate your inner-loop workflows with improved access to devices, diagnostics tools for local and production issues, profiling workflows that let your agents test and validate optimizations and much more.
As Android apps grow and AI coding assistants become essential, using executable code to configure your build can create bottlenecks with slow sync times, fragile logic, and added complexity.
Enter Lightbuild: Google's declarative, config-driven interface to the build engine, designed for modern Android development.
In this session, we'll explore Lightbuild's new approach to managing builds and how to use it to build a demo app. Learn how decoupling build config from execution delivers faster project opens with lightning-fast sync in Android Studio, while offering a predictable schema for safer, more reliable AI editing. We’ll also cover Lightbuild's agent-friendly CLI tools for creating reproducible builds across local machines, teams, and CI/CD pipelines.
This presentation explores the strategic shift from viewing AI as a generic coding assistant to leveraging it as a context-aware, automated security peer reviewer integrated directly into the Android development lifecycle. We discuss how specialized AI agents, connected to the Android toolchain via skills, can help improve app security. By bridging the gap between raw LLM capabilities and deep project context, this approach empowers development teams to maintain high-velocity feature delivery without compromising rigorous security and policy standards.
Optimizing Android apps requires deep visibility into concurrent workflows and coroutine suspensions. While local profiling offers a useful snapshot, scaling these insights to production without overhead remains a challenge.
This session delivers an architectural blueprint for a continuous performance feedback loop:
* androidx.tracing 2.0: Swap backends dynamically and propagate coroutine contexts (Perfetto flows) across threads.
* Smart Instrumentation: Use local ART tracing to find hotspots, then automate the injection of low-overhead trace points.
* Macrobenchmarking: Track regressions and verify performance gains on physical devices in CI.
* Field Tracing: Go beyond local and CI tracing, with ProfilingManager.
Android apps often ship under-optimized due to overly conservative keep rules often from third-party libraries, leading to bloated APKs, slower cold starts, and degraded runtime performance.
With Google Play’s new performance thresholds for DEX optimization, app visibility now directly depends on staying ahead of the optimization curve.
This talk introduces a modern R8 workflow to tackle rule bloat. You will learn to:
* Use the R8 config analyzer and skill to identify legacy rule overhead.
* Transition from broad wildcard keep rules to precise, type-safe, generated annotations.
* Prevent optimization regressions with new Android CLI tools.
As AI tools rapidly reshape modern software engineering, this panel will explore how developers are leveraging AI-assisted coding, automated agents and specialized developer tooling in their daily workflows. We aim to highlight practical applications, discuss measurable productivity improvements and candidly address the challenges engineering teams face when integrating AI at scale.
Keep your app's memory footprint lean-and-mean and non-segfaulty with Firebase Crashlytics. This session explores our comprehensive suite of memory troubleshooting tools available in the Firebase console and in Android Studio. We’ll start by covering how to leverage ANR insights and GWP-ASan reports to diagnose elusive memory bugs and then dive into our latest tooling for Out-Of-Memory (OOM) and Memory Limiter Kill (MLK) events, designed specifically to help you navigate and adapt to the new memory limits introduced in Android 17.
As the Android ecosystem expands across wrists, living rooms, vehicles, and XR, the opportunity to reach users on new screens is growing. However, distributing across Wear OS, Android TV, Android Auto, Android Automotive OS, or Android XR introduces distinct considerations for testing, store listings, and app reviews.
This session explores how to effectively utilize Google Play Console for non-mobile form factors to help streamline a predictable multi-device launch. We will cover key distribution decisions, including how to structure track strategies and package names, configure targeted testing tracks, and tailor store listings. You'll get a practical walkthrough of form-factor App Quality guidelines to help avoid common review pitfalls and publish on Google Play with greater confidence.
Android Developer Verification is crucial for a safer ecosystem. This session breaks down the compliance pathways for all developers, from large studios to hobbyists. We will outline the key requirements for publishing on Google Play and third-party app stores. The talk will feature a live demo of the new Limited Distribution accounts, showing how students and hobbyists can easily and safely share apps.
By the end of this session, you will be able to:
* Understand the 3 main developer verification paths.
* See the new Limited Distribution account flow live.
* Identify your specific next steps for compliance.
Jetpack Compose makes it easy to design high-quality user interfaces, but it can be difficult to track down issues that affect UI performance. These kinds of issues can lead to problems that your users notice, like startup latency, and dropped frames that appear as scroll jank or choppy animations.
In this talk, we’ll introduce tools to uncover what’s impacting your UI’s performance, focusing on Perfetto and (re-)composition tracing. We’ll then explore specific anti-patterns you may be using that are secretly costing you, how you can find them in your code, and what positive patterns you can replace them with. By the end of this talk, you’ll understand how to think in Compose with a performance mindset, and how to profile, analyze, and verify performance optimizations in your app.
Managing Bitmap memory is critical for mitigating Out-Of-Memory (OOM) risks in visually rich Android apps. While developers know to reduce image sizes, achieving long-term app stability comes from mastering two other key pillars: Reuse and Recycle. This session delivers a practical playbook for optimizing memory performance using modern tools, open-source libraries like Glide and Coil, and system-level APIs.
In this session, you will learn how to diagnose real-world memory regressions using Android Vitals, implement advanced caching (Reuse) patterns with Glide and Coil, and proactively release memory (Recycle) using the onTrimMemory callback.
AI models can generate entire features in minutes, but is the code correct? We built Android Bench, our AI evaluation benchmark, to answer this question after analyzing thousands of generated code changes.
This talk shares insights from our journey, including all the ways we saw models cheats, how prompt specificity leads to higher code quality and how different agents approach the same task.
The Android ecosystem is vast, with users shifting seamlessly across phones, tablets, foldables, and desktop environments. Now that we are Compose First, this session explores how to architect your app for resizable windows and diverse aspect ratios—where traditional layout assumptions break down, leading to stretched UIs and lost state.
Explore how the latest capabilities in Jetpack Compose, Navigation 3, and WindowManager can help you build dynamic layouts that naturally scale from compact screens to dual-pane displays. Walk away with strategies to accelerate your development workflow using Gemini and our skills, like the adaptive skill, to automatically refactor legacy codebases for larger screens.
This year, Android officially became Compose-first for building all UI, placing legacy Views into maintenance mode. For Google Play, that journey began back in 2020. Across an engineering footprint spanning nearly two decades and billions of users, migrating to Jetpack Compose was achieved through proven best practices, close collaboration with the core Compose team and continuous tooling evolution.
Discover how modernizing Google Play with Compose delivered measurable improvements in velocity and long-term stability. The session walks through connecting agentic Figma design workflows with Compose implementation, automating quality to prevent unnecessary recompositions and crafting expressive interfaces with dynamic color, rich typography and layered shapes. You will leave with tested strategies to triage bugs faster and scale your own Compose migration with confidence.
Ready to take your Android UI from "it works" to "it’s a work of art"?
Join us for a tour of the latest graphics capabilities in Jetpack Compose. We’ll show you how to build new visual effects, from delightful mesh gradients to progressive blurs, and using the powerful new graphics features in Android. We will also show you how to improve the performance of your graphics features, without sacrificing battery life or frame rates.
As in-car displays expand across Android Auto and Android Automotive OS vehicles, developers face a unique dual challenge: delivering rich, adaptive experiences while parked, and driver-safe, template-driven experiences while driving. In this comprehensive 30-minute technical session, we explore the end-to-end architecture and development approaches to adapting Android apps to cars.
From the fundamentals of designing apps for use in cars, to the newest approaches for building media experiences that shift from audio to video as the car shifts from drive to park, you'll leave with everything you need to know to get your app on the road.
Users expect third-party apps to capture photos and videos with the same high fidelity as their device's native camera, regardless of lighting conditions or hardware tier. Delivering this consistency across the expanding Android ecosystem comes with key architectural considerations. This session demonstrates how to construct robust, professional capture pipelines that maximize device capabilities while remaining reliable across all form factors.
We will explore the latest advancements in CameraX, showing you how to integrate cutting-edge capabilities like Motion Photos and on-device AI enhancements through Google Play services, alongside spatial experiences using the Jetpack XR SDK. We will also look at our CameraX skill, which allows the coding agent of your choice to automatically implement the concepts in this talk, and more!
Media consumption accounts for a large portion of user time spent on mobile devices, which requires the playback experience to be flawless, highly efficient and mindful of battery life. Furthermore, users expect these experiences to seamlessly transition across their devices, from phones to living room TVs and beyond.
Explore how architectural updates in Media3 and ExoPlayer power seamless playback across form factors. The discussion centers on crafting responsive interfaces with the Media3 Compose UI toolkit, eliminating buffering in feeds using the new PreloadManager and extending your app to living room screens and Android XR with CastPlayer and spatial audio.
The journey to reliable text editing in Compose culminated in the complete rewrite of BasicTextField. This shift to a buffer-driven architecture eliminated IME race conditions once and for all. This session unpacks why legacy input syncing had to go and how TextFieldState keeps keyboard updates in sync. From there, take a deep dive into formatted editing to explore the mechanics of TrackedRange, the performance costs of edit blocks, and the real-world catches behind style boundaries, before taking an early peek at Markdown rendering.
Remote Compose introduces a new way to project expressive and interactive UI onto remote surfaces like widgets. By serializing layouts into compact binary payloads, RemoteCompose decouples UI from host execution to deliver significant advantages.
Key benefits include edge interactivity that enables high-performance rendering through local execution on the remote device, fluid scaling that allows UIs to reflow across diverse form factors via remote-side component evaluations, and a unified developer workflow that removes the need for platform-specific remote UI frameworks through familiar Jetpack Compose APIs.
This session unpacks these benefits and provides live production examples, including modern Wear OS Widgets and the glanceable Wear Workout Tracker experience in Runkeeper.
The launch of Googlebook opens up a new frontier for high-fidelity, desktop-grade experiences. In this session, we go behind the scenes with two pioneering partners who built for this platform from the ground up.
Notability will share their journey creating a desktop-class Android app using Jetpack Compose. Learn about their journey moving from other app platforms with desktop top-of-mind. Second, Logitech will dive into the hardware side, discussing how they are building and customizing peripherals to integrate seamlessly with Googlebook. Join the session to get practical, real-world insights on optimizing inputs, leveraging large-screen APIs, and delivering a premium, cohesive user experience across hardware and software.
As new form factors move beyond the touchscreen, Compose's input system has evolved to meet the challenge. Its layered architecture provides the foundation for supporting everything from advanced trackpad gestures to novel hardware inputs seamlessly.
Through clear architectural breakdowns and hands-on code examples, follow the lifecycle of an input event all the way from the OS platform layer up to Compose gesture detectors and UI components. You will discover how to trace events across the entire stack, apply key architectural patterns for emerging input types, and confidently debug complex gesture interactions in your own apps.
Compose’s snapshot runtime, automatic dependency tracking, and atomic updates don’t have to stop at the UI layer. Jetpack AppState lets you move Compose state upstream—streamlining what reaches your screens by hoisting and deriving state with the snapshot system before it ever hits the UI.
In this session, you’ll learn about AppState’s two foundational libraries. We’ll dive into StateStore for hoisting state, and Transform for using composition to derive state with plain Kotlin control flow—eliminating complex Flow combine chains and keeping your UI effortlessly in sync.
As the industry moves away from passwords and physical wallets, delivering a modern user journey demands both seamless authentication and trusted identity verification. While passkeys establish secure one tap logins, switching devices remains one of the largest drop off points in user engagement. Learn how to reduce migration friction using the Restore Credentials API to meet the new Google Play Zero Tap Sign In standard.
This session explores how a single integration with Android Credential Manager unifies passkeys, silent device restoration, and Digital Credentials, allowing you to verify identity attributes directly from the device and build an effortless, secure onboarding flow.
In this session, we will take a technical deep dive into the evolution from full-screen Tiles to dynamic, partial-height Wear Widgets.
We will explore the technical benefits of the unified Jetpack Glance API and the new Remote Compose engine, detailing how they seamlessly align with Modern Android Development.
Finally, we will share the latest UX guidance and walk through practical migration strategies to help you build the next generation of glanceable UI.
Managing deep links across modular Android apps can easily lead to broken routes and runtime surprises. This session unpacks Jetpack Navigation 3’s new type-safe deep linking architecture for Compose to help you build a robust and scalable routing system. We'll explore how to implement out-of-the-box deep link matching APIs, write custom serializers for complex type-safe arguments, and construct dynamic hierarchical back stacks that keep user navigation predictable.
Hear directly from WhatsApp engineers on how they upgraded their Wear OS app at scale. This session covers the architectural and UX decisions behind integrating Material 3 and adopting Wear Widgets.
Gain direct insight into the lessons, patterns and tools the team used to update their app and deliver a cohesive user experience.
As users move between phones, wearables, and audio peripherals, delivering fluid cross-device experiences has become essential for engagement. However, relying on standard networking approaches often leads to battery drain, latency spikes, and fragmented user sessions.
This deep dive introduces specialized Android APIs built for multi-device communication, offering memory- and power-efficient patterns to keep transitions between devices instant, reliable, and intuitive.
Learn how to integrate 3D game engines (Godot & Unity) with Jetpack Compose into a single codebase for mobile and Android XR. We'll explore embedding 3D scenes into spatial containers, setting up Kotlin-to-engine communication—featuring an exclusive look into how the NBA built their live basketball experience on Android XR.
Go beyond screen-space and anchor your apps in the real world with Android XR. This session teaches you how to build geospatially aware Android XR experiences using Jetpack Compose Glimmer and ARCore's Geospatial API. We will start by covering how to get a device's geospatial pose with ARCore. Then, you'll see how Glimmer’s minimal UI components can be anchored to real-world locations via the Visual Positioning System (VPS). We'll combine these to build a simple, location-aware spatial experience.
Discover how to anchor and persist 3D experiences in the real world using Unity and Android XR. This session covers the Spatial Entities framework, Cloud Anchors, and Geospatial APIs, demonstrating how to build context-aware apps that remember physical placements and sync multi-user spatial data across sessions.
We will examine the architecture behind spatial entities, understand how to anchor digital assets to physical objects, surfaces, and geographic locations. You will walk away with practical Unity workflows for mapping spaces, persisting content across sessions, and creating shared, location-aware AR/XR experiences.
Bringing conversational AI into immersive experiences opens up huge possibilities, yet there’s a constant friction between low response latency and sustainable cloud costs. In this session, Devin Reimer (Founder & CEO of AstroBeam) breaks down how the team behind Stellar Cafe achieved industry-leading voice interaction response times (1.15s–1.4s) while keeping the business model commercially sustainable.
Explore the hybrid architecture behind these low latency pipelines, focusing on intelligent orchestration between on-device models and optimized cloud inference to cut expensive API calls without degrading dialogue. You’ll walk away with a practical blueprint covering Time-to-First-Token optimization across Speech-to-Text and streaming Text-to-Speech pipelines, parallel safety guardrails that bypass latency overhead, and unit economics per active user session.
When we say XR is for everyone, that principle has to guide how we build from day one. In this introductory guide for developers new to XR, Jazmin Cano shares the foundational accessibility principles honed at Owlchemy Labs. Engine-agnostic and universally applicable to both games and apps, this session explores how early consideration of motor, visual, auditory, and cognitive needs leads to better experiences for all users. Discover how to build an inclusive development culture, conduct meaningful testing, and design spatial interactions that remove barriers without sacrificing quality.
Discover how to build robust, hands-free audio experiences powered by on-device AI. We’ll cover everything you need: setting up your glasses activity, capturing mic and camera feeds, and using voice along with other audio cues as your ultimate UI. Through an exciting real-world showcase of the open-source XR Language Teacher built in the Google AI Edge Gallery app, learn to orchestrate Gemini Nano 4 (built on Gemma 4 and optimized for Android devices), and ML Kit, and leverage the LiteRT runtime to build fast XR experiences that hear, see, and speak naturally.
Transitioning your Android applications from traditional 2D screens into spatial environments requires a new approach to constructing shapes.
In this session, we will explore the Custom Mesh API in the Jetpack XR SDK, which allows you to programmatically generate procedural 3D geometry directly at runtime. We will walk through the core workflow, from defining vertex layouts to rendering dynamic objects seamlessly within the user's physical space.
By the end of this talk, you will have the practical skills to build interactive, custom 3D geometry completely from code.
Which sessions or announcements stood out to you this year? Let us know what you're testing out in the comments!
Comment here to discuss the recent trend of long Play Store review times for app submissions and updates.
Do not make a new post about this subject, as it will be removed.
This is an unofficial developer community, so we are not on the Play team and cannot help your app/update pass review. No, we don't have tips to speed things up.
Yes, Play Store developer support is present on this sub and may answer questions or assist you on a case-by-case basis. The mod team is not affiliated with and has no influence over that account. We make no guarantees as to their effectiveness, but we are grateful they exist and that they continue to communicate with users here.
I put my app up on my personal google account and had my friends test it in Closed testing. Eventually I got myself an organization account, and I uploaded the game to the new account, fresh. A lot changed from the old version, we re-organized a lot, so it's basically a new app except for the name and icon. Those are the same.
So my "new" app is on the play store in Pre Registration. I sent my husband to pre-register, but on his phone, it shows "Install." But he isn't a tester on the organization account, and never has been. I only have 2 testers on this account, me (my personal account) and another friend.
I sent it to his brother. He also has Install.
These two guys were on my old account's tester list, so I am wondering if... the name of the app is cached...? The "com" package name is different, though.
If I swap my google account, it shows Pre Register. And in Google Play Console, it shows it's in Pre Registration.
I just don't know why my husband and his brother see Install, and can't Pre Register themselves.
Unfortunately, I don't have any friends I haven't already forced to be on my tester group! So I can't check. I don't know if it counts as self promo here either so I won't post it. I guess I'm just wondering if anyone else has encountered this issue?
I work in IoT by day and kept seeing the same gap: billions of cheap BLE sensors (asset tags, shipment trackers, environmental monitors) need a phone nearby to reach the cloud. Apple solved this for AirTags with a billion iPhones. Everything else relies on open coverage networks, and those networks are short on phones.
Meanwhile thousands of apps already hold ACCESS_FINE_LOCATION and BLUETOOTH_SCAN for their real features: OBD readers, cycling computers, golf GPS, delivery apps. The radio sits idle between the features that earned those permissions.
So I built an SDK that borrows it. Passive scan for sensor beacons, stamp each packet with a fresh GPS fix, relay it upstream. The app's owner earns 1 satoshi per unique device heard per day.
The engineering constraints were the interesting part. It's a guest in someone else's app, so the rules are frozen API:
- It never prompts. start() without the grants parks in an awaiting-permissions state and advances on its own when your permission flow completes. Revoke mid-run and it parks again.
- It can't crash the host. No exceptions escape, no force-unwraps, nothing to catch.
- It starts no services and declares no background modes. It rides whatever foreground service or background mode the app already runs.
- Battery gating: it pauses below 20% unless charging, and pauses when the fix stream goes stale (scanning while location is dead just burns battery).
- Zero dependencies beyond the Kotlin stdlib. minSdk 26.
On privacy, since that's the first fair question: the beacon payloads are encrypted by the sensor owner's key before the phone ever hears them. We can't read them and neither can the host app. What travels in the clear is the location stamp that proves where coverage happened, used to pay bounties and draw the coverage map.
The whole integration is two lines from your existing service. I'd value this sub's take on the guest-SDK constraints, and if you run an app that holds these permissions and want to try it, I'll help you troubleshoot your integration.
Anyone interested to try a new revenue stream that's not ads or paid subscriptions?
I installed the apk of my own app to be able to use on my phone but even though it installs (unknown sources permission is granted), opening the app sends me directly to Google Play. The problem is app is not there.
Even though Play Protect Settings are off, is there a solution?
If you use worktrees to run parallel agents, you probably also ran into the issue that even though the code is separated, the emulators/simulators the agent needs to run the app are not, and different agents touch the same device. It's also a pain to manage launching/creating devices manually.
I built a tool that "leases" devices from a shared pool, and only the agent that requested the device can touch it until it's released back to the pool again. There is a cap on the number of parallel devices so it doesn't eat up your RAM, and if none are available, the agent waits until one is released and continues automatically afterwards. Devices are lightweight clones of a master device, where you can set up initial data that gets copied to each device. It can also run headlessly, so you don't have too many windows open.
Disclaimer: It's ofc built with AI, but it works great for me. Also, I am sure there are similar tools like this (because everyone vibe codes the same tool these days); I just haven't found anything that fits my use case when I decided to build this. If you already have a solution to this, lmk what you use in the comments!
I wanted to tunnel Telegram traffic through WireGuard without claiming Android's single VpnService slot or affecting other apps.
The approach hooks the app's socket/network calls via Xposed/LSPatch and forwards them into an embedded wireguard-go + gVisor userspace netstack compiled as a native library, with DoH for DNS resolution.
Things that bit me: keeping the native bridge stable across different Android ABIs and handling non-root LSPatch environments cleanly.
I'm reading reports about what percent of free mobile games are uninstalled same day and within 30 days, especially if brought in through advertising like Google ads. Some reports say uninstall rates are sometimes as high as 45%-50% loss within a day and some even as high as 95% by day 30. That is all types of apps mind you.
What have you found your own personal loss rate to be for your game?
Each tester is a Claude Code agent with its own emulator on a free GitHub Actions Linux runner, playing a persona: device profile, API level, locale, font scale, dark mode.
On LocalSend (100k-star app): at Android 14’s 200% font, all six Send buttons overflow and cut their labels. On the Pixel Tablet, the keyboard covers the address dialog’s Cancel and Confirm. 47 issues from the 10 Android testers.
I'm a founder from India preparing to launch my startup's Android app through a newly created Google Play Console Organization account (Private Limited Company).
My developer says the entire process, including organization verification, app review, and possible rejections, could take 1–2 months.
I have a few questions:
How long did it take you to get your first app LIVE using a new Organization account in 2025/2026?
Have there been any major changes in Google Play policies since 2018 that could delay publishing?
Is launching within 2–4 weeks realistically possible if all documents and app requirements are ready?
How frequently do new organization accounts face rejection during verification or app review?
Would love to hear from founders or developers who have recently published their first app using a new Organization account, especially in India.
I've been curious about how Android developers are incorporating AI into their daily workflow lately.
Tools like ChatGPT, GitHub Copilot, and other AI coding assistants have become much more capable, but I'm wondering how useful they really are for actual Android development.
Personally, I think AI can be great for:
Generating boilerplate code.
Explaining unfamiliar APIs and libraries.
Writing unit tests.
Debugging common issues.
Exploring different implementation approaches.
However, I'm still not entirely comfortable relying on AI for more complex architecture decisions, performance optimization, or debugging tricky Android-specific issues.
I'm curious about your experiences:
Do you use AI coding assistants regularly, occasionally, or not at all?
Which tasks do you trust AI with the most?
Have AI tools genuinely made you more productive, or do you spend just as much time reviewing and fixing generated code?
Do you think AI will significantly change the Android developer role over the next few years?
Would love to hear some real-world experiences, especially from developers working on production Android apps.
I've been looking into different approaches to state management in Jetpack Compose, and one thing I'm still interested in is deciding which state should live inside a Composable and which should be managed by a ViewModel.
For example, consider a screen with:
A search field.
A filter bottom sheet.
A list of items loaded from a repository.
Sorting and filtering options.
Loading, error, and empty states.
Some state seems clearly UI-related, such as whether a bottom sheet is expanded. Other state, like the list data and loading status, belongs naturally in the ViewModel.
But there are cases where the boundary isn't so obvious. Should search queries and selected filters always live in the ViewModel? What about tab selection, temporary form inputs, or pagination state?
I understand the general principles of state hoisting and unidirectional data flow, but I'm curious how other developers apply them in larger production apps.
A few things I'd like to discuss:
Do you generally keep most screen state in a single ViewModel, or split it into smaller state holders?
What kinds of state do you prefer keeping local to Composables?
Have you run into problems with overly large ViewModels or unnecessary recompositions because of your state management approach?
Do you follow a particular architecture pattern for complex Compose screens?
I'd be interested in hearing how people handle this in real-world projects, especially as screens become more complex.
I've recently encountered a situation that I honestly never expected to deal with, especially as a small independent developer launching my own product.
I've been working on an expense-tracking app that originally started as a personal project back in 2021.
Over the years, it went through multiple repositories, two name changes, and countless iterations before finally becoming the product I wanted to release.
I also established my own indie studio in June 2025, with a distinctive green hedgehog as its mascot.
In April 2026, my application received its final name and branding, both inspired by my studio.
Fast forward to October 2026.
I publicly posted in a subreddit to recruit testers for Google Play's mandatory closed testing.
My post included the app's name, branding, functionality, and positioning.
Five days later, another developer posted in the EXACT SAME subreddit, recruiting testers for an application with:
The exact same name.
A hedgehog featured in the app icon and a green color scheme.
The same niche: expense tracking and budgeting.
Essentially the same positioning.
And here's the cherry on top: both applications were released on Google Play on the exact same day.
Now, when someone searches for my application's name, they can find two expense trackers with almost indistinguishable branding concepts.
And the other developer has already started promoting their application under that name on social media.
What's particularly concerning is that this doesn't appear to be an isolated incident. After recruiting testers, the developer had not posted anything else on Reddit. However, less than 24 hours after I published the development history of my app, the same developer resumed posting and began promoting their app in another subreddit targeting a similar audience.
I'm not claiming ownership of expense tracking as a concept. There are thousands of expense trackers out there, and that's perfectly fine.
But copying the name, mascot, and positioning of another indie product is an entirely different matter.
What makes this particularly frustrating is that I spent years developing this project, building its identity, and going through all the hurdles of getting it published.
And now I suddenly have to defend the identity of my own product instead of focusing on improving it.
I have dated Git commits, original branding materials, previous repositories, screenshots, and public posts documenting the entire timeline.
I've already filed an impersonation report with Google Play. Their support team confirmed that it's under review, but there's no way for me to track its progress.
So, fellow indie developers, what would you do in this situation?
Has anyone successfully dealt with something similar?
Are there any practical and affordable ways to protect an indie product's identity once something like this has already happened, without turning it into a public war?
I'm looking for actual advice from people who've been through this.
I’m a solo developer from India, and I’ve been building a small Image to PDF Converter app. It got its first 100+ downloads, but I know my Play Store screenshots
The problem with the old screenshots
Heavy dark red design, which felt dated
Nothing in them made a stranger want to tap Install
What I learned: AI is great for speed and options, but you still need to decide what’s good.
Your screenshots are your real “landing page” on the Play Store. Most people never read the description.
Writing the headline first, then designing around it, works better than the reverse.
It’s too early to say how much this will change my installs, so I’ll update this post in a few weeks with real numbers
Hi everyone,
I’m developing an Android-only app designed to record audio while the user sleeps (to track snoring and sleep talking). Important context on data & connectivity: All audio recordings are stored strictly locally on the user's device—nothing is ever uploaded to my servers or the cloud. However, the app will use internet access solely to serve ads (AdMob) and handle a one-time in-app purchase to remove them.
My main concerns are Google Play review guidelines and legal disclaimers regarding privacy and third-party consent (for example, if a user sleeps next to a partner or roommate who gets recorded in the background).
For those who have published similar audio-recording apps on Google Play:Any advice or experience passing Google Play review with a setup like this would be greatly appreciated. Thanks!
I've been shipping Android apps since 2023 and kept hitting the same small problems. What's making this APK large. Generating every icon density again. Working out which permissions Play is going to make me justify.
Every web tool for this wants you to upload the file. I'm not uploading an unreleased build to a stranger's server to find out how big it is.
So these run entirely in the browser. No server, no upload, no account:
APK/AAB size analyser — reads the ZIP central directory, so a 200MB build measures instantly instead of transferring. Breaks down lib/, res/, assets/ and dex, with an estimate of what a device actually downloads from an App Bundle.
App icon generator — one image to every density, adaptive layers, the <monochrome> drawable for Android 13 themed icons, and the 512px Play icon, in a correct res/ structure. Draws the 72dp safe zone so you can see what a launcher will clip.
Manifest permission explainer — paste a manifest, get what each permission actually grants, which ones need a runtime prompt, and which ones Play restricts.
Play listing preview — where your title gets truncated at real search widths, and the feature-graphic alpha channel trap.
Screenshot framer — device frame, background and caption, exported at sizes Play accepts.
dp ↔ px converter — flags values that land on half a pixel and render soft.
There are also four write-ups on the things behind the tools: where APK size actually goes, what a launcher does to your icon, the Play Console permission declarations, and how much of a store listing gets cut off.
Free, no signup, no file size caps. The calculations are covered by tests. Being upfront: the site carries ad code to cover the domain cost.
Happy to hear what's wrong with any of it — particularly the App Bundle delivery estimate, which is a model of what Play would deliver rather than a measurement.
I wanted to see how small a complete, playable Android chess app could get (originally built it for my very old android devices but works for all android versions)
The engine :
full FIDE : Tracks state on a classic 128-square 0x88 array with compact integer pieces, with castling, en passant, promotions, threefold repetition, the 50-move rule, insufficient material, and strict king-safety validations
Search system: Pairs iterative-deepening alpha-beta and Principal Variation Search (PVS) with a 65,536-entry Zobrist transposition table + null-move pruning + late-move reductions, killer moves + capture/promotion quiescence search .
positional evaluation: it scores using piece-square tables and bishop-pair bonuses.
Levels: Easy (2 ply / 140 ms) - Medium (4 ply / 320 ms) - Hard (6 ply / 680 ms) and Expert (16 ply / 1,450 ms) !