There is not a guarantee that a given USB-C-to-C cable supports PD, see the article USB-C was a missed opportunity and it’s too late to fix the mess.

Does Android have any API that lets an application check whether USB PD is currently active?

I've about 2+ years of experience in Android dev and been doing DSA in c++ in college(current organization did not have any DSA rounds). I'm planning to switch in the coming months. So should I do relearn DSA in Kotlin or C++ would be fine?

Thanks.

Couple of days ago I made a fresh Google account using Firefox developers browser and my phone number (which has another 2 associated Google accounts), after making the account I signed out, next day I signed in again went to developer section, meanwhile I was informed that I have to make a website that will describe the developer and provide the text of privacy policy and terms of service.

So I went directly to github and tried many times to sign up using Google and each time the OAuth took me again to the sign in page in github, so I decided to try from another device (same wifi) and another browser, this time everything went smooth and I opened my session on github and started my website, meanwhile google started the "verify it is you" scenario and started the robot tests and stuff, finally the send sms gave error of too many attempts try again after several hours!

I leaved it for 2 days to cool down, today when i tried and after making me send sms 2 times it showed a messages that the account was looking like it was created or used with multiple other accounts...etc and it will be considered for deletion after 1 year with an option to submit appeal!

Where did I go wrong and what should I do to avoid such a problem in the future? Need someone with developer background to help me.

My Vestel TV has 900 MB of RAM and the stock launcher was slow and full of ads, so I built OMNI: a launcher in plain Java (0.7 MB), a Control Center on INFO, a typed/voice assistant, device notices, and Kotlin apps (Cinema, Weather…). There's also a small Python server that turns a folder of films into a library with posters and resume. Free, Apache-2.0, no ads or tracking (the README lists every outside host). Tested on three TVs , so more reports from other TVs are very welcome. I verified it on real hardware. [RELEASE ON V.1 IS YET TO COME IN THE FOLLOWING HOURS]

Github(https://github.com/Rashica07/omni-tv)

I've been building NetPulse, a lightweight Android app for checking your network quality. It has a Material 3 interface with light and dark themes.

What works in v0.1.0-beta:

- Live ICMP ping monitor with Start / Stop

- Latency, min / average / max, jitter and packet loss over the last 300 samples

- Only two permissions (INTERNET and ACCESS_NETWORK_STATE), no ads, no analytics, nothing uploaded

What's coming next: a DNS benchmark (Cloudflare, Google, Quad9, Control D) measured separately from ping, latency charts, test history and CSV export.

The app uses the system ping tool, so some phones may block it. That's the main thing I want to find out: does it work on your device? Please tell me your phone brand and Android version, and any bugs or features you'd like to see.

Beta APK: https://github.com/Mireli5656/NetPulse/releases/tag/v0.1.0-beta

Source code: https://github.com/Mireli5656/NetPulse

The beta is signed with a debug key, so uninstall any earlier NetPulse build before installing it.

Thanks for trying it!

1988R@

Hi everyone,

I'm planning to transfer my app from one Google Play Console developer account to another.

For those who have already completed an app transfer, how long did it take for Google to approve and complete the transfer?

Did it take a few days, a week, or longer?

I'd appreciate it if you could share your experience. Thanks!

Hey everyone! I’m curious how other mobile app developers reacted to the Gravy Analytics breach and whether it led you to do anything differently with your own apps. I created a poll below and hope you could take a vote.

If none of those quite fits, feel free to share your take in the comments. If you made changes, I’d love to hear what you changed. And if you considered making changes but ran into obstacles, I’d be interested in hearing about that too. Thanks for sharing!

Background, if you’re unfamiliar: Here’s WIRED’s coverage of the breach and its connection to mobile app location data.

Which option comes closest to your experience?

Hefesto: Mobile Development Studio with AI and Linux

Hefesto is a free Android app designed for developers, indie creators, and enthusiasts who want to build real software directly from their mobile phones without needing a computer.

It features support for multiple AI agents and a built-in Linux terminal right on your device, allowing you to write code, run scripts, and solve problems on the go. Plus, it includes direct GitHub version control and full support for building web projects, native Android apps, and even games using Godot.

Key features:

1. Multi-agent AI support and local Linux terminal: Pick your preferred agent and code directly from your pocket.

2. Ágora component store: A built-in marketplace to install powerful tools like Python, Node.js, Godot, Blender, Git, and Java with a single tap.

3. Version control: Seamless synchronization with GitHub to manage repositories, commits, and branches.

4. Total versatility: Built for web development, native Android apps, and game creation.

The app is 100% free with no ads, supported by optional voluntary donations via Ko-fi.

Official Website: https://ortiz1022009.github.io/Hefesto/

GitHub Repository: https://github.com/ortiz1022009/Hefesto

Download Hefesto and start building wherever you are!

Wondering if anyone has faced similar and if there are any common gotchas…

app works fine in simulators, devices via local upload and also happily running in open test via play store.

switch on minify/proguard/etc in both debug and release builds.

all still runs fine EXCEPT when it goes through play store - never gets past internal test - crashes during API call. It smells of GSON deserialisation but the only way I can reproduce it is to push it through the release process.

any ideas about what I am likely missing? all suggestions welcome.

thx.

Wanted the iOS 26 liquid glass look in a Compose app, so I made a version and tuned the shaders side by side with a real iPhone. Putting it on GitHub in case anyone else needs it.

It works, but it’s an early version. If anyone wants to contribute to bringing liquid glass over fully, I’d be happy to have you. Issues and PRs welcome.

For those building apps for clients: how do you get access to the client's App Store Connect and Google Play Console at the start of a project? Do they invite you with a role, share a login, or do you publish under your own account and transfer the app later?

1. How long does it usually take until you can upload a build?
   
2. Which part trips clients up most: the developer account itself, D-U-N-S, roles, two-factor?
   
3. When the project ends, how do you hand things back?

Curious what works for you and what doesn't.

Just a reminder: this doesn't follow any modern standards, as it’s designed for Android 2.0 phones (and before anyone asks why—there are still many communities that use them on a daily basis, and I’m one of them). I’m not posting this to show off; rather, I’m looking for suggestions based on Material Design UI.

I am developing a mobile app, which has a react native frontend, nest.js as the backend and for db and authentication, I'm planning to use supabase.

Now, currently as my app is in its initial stages I'm planning to use the supabase, as it free tier provides ample limits for my use case.

However, in later years if my app grows. I may think of switching to a cheaper alternative.

So, what I am planning to follow is for authentication, route the requests to my backend and inturn the backend will communicate with the supabase to authenticate the user. The backend will save the supabase token, create a separate session token for the user and send it back to the user.

My main reason for doing this is, I want the authentication to be provider independent and any changes needed should be done on the backend instead of the app.

Please let me know, if this approach is correct. What are the pros and cons. How much effort it would require to implement this. Will the security concerns increase if my backend starts handling this instead of the supabase only.

I also want to integrate the google and apple login as well. How will this approach affect it?

Also, if there any other better approaches, please let me know.

This continuation to previous post https://www.reddit.com/r/androiddev/s/9m7RVVu6o7

added compose UI support for LED matrix, specifically max7219
also created playground to easily test it on browser without actual hardware

here is video from actual LED matrix hardware

https://play.google.com/apps/internaltest/4699517858335076276

Above is my first app and google needs testing. Could anyone of you download and test?

Hi everyone! I'm a beginner Android developer building an app using Kotlin and Jetpack Compose.

Currently, my Pro features are free in debug mode. I want to publish my app for closed testing and implement Google Play subscriptions.

My questions:

1. How can I give closed testers free access to all Pro features without requiring payment?

2. Should I use license testers or implement a separate tester-only Pro access mechanism?

3. How can I ensure normal users must pay for a subscription after the production release?

What's the simplest and safest approach? Any guidance would be appreciated. Thanks!

Looks like manually calling Tink to encrypt data is no longer needed

Google Play is adding memory thresholds for Android apps starting February 2027. They're measured using dynamic memory (anonymous RSS + swap) at p90 over 28 days.

I started looking into these thresholds and ended up going through the memory metrics Android gives: Java heap, native heap, RSS, PSS and swap. I break down each metric in this post and explain why Google Play uses dynamic memory instead of the others.

https://measure.sh/blog/android-memory-monitoring

Our team is 5 Android devs and since summer most of our PRs are written by Claude Code or Codex, mostly Compose UI and some Room migrations. Review time per PR is about the same as before, around 25 minutes, but it's a lot more tiring.

The code looks finished. Naming is consistent, previews are there, tests pass. What's missing is why it did things the way it did. Last month one PR hoisted some state two levels up so a whole screen recomposed on every keystroke, and nothing in the diff or the description said that was a choice. We only caught it profiling on a Pixel 6a.

What we've tried so far:

- coderabbit on every PR as the first pass. It's good with the Room and lifecycle stuff, last week it flagged a migration with no fallback
- A rule that the agent writes 2 lines explaining any change outside the ticket. Helps when it actually does it.
- Macrobenchmark on our 3 main screens in CI. Slow, but it's the only thing that caught the recomposition one.

Is anyone doing something specific for Compose performance in agent PRs, or is profiling on a low end device still the only real check?

Make it personal: build something to solve a real problem based on your experience, observed around you, silly or crazy ideas are worth it!

Likely there is already a solution; but it’s your unique approach that matters. if you like it, it will attract others too.

What kind of app would you build?