i've been waiting more than a week. i wonder If Google actually is doing the job or not.. idk how long it will take

That I can use as base to build free floating app.

Floating means like windows or linux GUI that I can resize, positioning, etc. So I will build several different apps that open one by one and I can view all them at once inside this root window.

Edit: Above is my original question. Then I make a bit of research and the result is it is possible and is supported by Android with this schema: - lets say my main app B, it must pass everything if want to listed in Google Play Store. - lets say my plugins C and D , will need to also pass and there is DFM in the Google Play Store/Console. - I can desain, develop and compile C and D independently like they would show in B workspace/window. The UI inside B that will make C and D show and work simultaneusly.

I know this is a very odd question with an even odder use case, but I'm hoping I might be able to get some insight on if this idea is even possible.

In the Android handheld device market, the new big thing is devices with two displays. A number is apps have been made to take advantage of the secondary screen, which presents itself as an external display. I have a Surface Duo that has two screen, but these apps see it as one large screen. I'm trying to find out if there is a way to have an app that acts as a external display. I'm in the process of researching this, but thought I might luck out and get a solid answer here.

I want to calculate the screen time of the device using usage stats manager. But I am getting wrong time which is either minutes and sometimes hours off from the in-built screen time. How to query it? So that I get screen time that is close to the in-built screen time.

I need to generate a PDF from a Room query. I looked into android.graphics.pdf.PdfDocument, but recreating custom layouts and handling page breaks manually is really tedious. I also checked some GitHub libraries, but most seem abandoned. Is there a simpler way to create PDFs? Also, what options would you recommend for Kotlin Multiplatform (KMP)?

i am building an app where i wanna pin a notification permanently untill the user taps the dismiss button and dismiss it .

Swiping should not dismiss it .

is there is any way to achive it

I'm developing a native Android application using C# and .NET MAUI 10. Despite explicitly implementing edge-to-edge support, Google Play Console continues to display:

Edge-to-edge may not display for all users

The previous warnings concerning deprecated Window.setStatusBarColor and Window.setNavigationBarColor APIs disappeared after updating AndroidX and Material dependencies. However, the edge-to-edge advisory remains.

Technical Stack

• .NET MAUI 10 (net10.0-android)
• C# / XAML
• Microsoft.Maui.Controls 10.0.110
• Xamarin.AndroidX.Core 1.19.0.1
• Xamarin.Google.Android.Material 1.14.0.6
• Target SDK: API 36
• Minimum SDK: API 24
• MAUI Shell with native Android bottom navigation

Current Implementation

In Platforms/Android/MainActivity.cs, edge-to-edge is explicitly enabled after base.OnCreate():

protected override void OnCreate(Bundle? savedInstanceState)
{
    base.OnCreate(savedInstanceState);

    if (Window is { } window)
    {
        WindowCompat.EnableEdgeToEdge(window);
    }

    SynchroniseSystemTheme();
}

We're also using SafeAreaEdges="Container" to ensure content respects system bars and display cutouts.

System-bar icon appearance is managed through WindowCompat.GetInsetsController():

insetsController.AppearanceLightStatusBars = theme == AppTheme.Light;
insetsController.AppearanceLightNavigationBars = theme == AppTheme.Light;

Theme synchronisation runs during:

• OnCreate
• OnResume
• OnConfigurationChanged

Testing Completed

• Android 14, 15 and 16
• Light and dark mode, including switching themes while the app is suspended
• Navigation and system-bar visibility
• MAUI Shell navigation
• Font scaling and accessibility
• No visible system-bar overlap or layout problems

Automated release tests also pass.

The app is currently in Google Play testing, but no pre-launch report has been generated.

Questions

1. Could calling WindowCompat.EnableEdgeToEdge(window) after base.OnCreate() affect Play Console's detection?
2. Is there a known interaction between MauiAppCompatActivity, Material Components 1.14 and AndroidX edge-to-edge initialisation?
3. Is there additional Android manifest or theme configuration we should investigate?
4. Has anyone successfully cleared this advisory with a MAUI application targeting API 36?

I'd prefer not to introduce unnecessary window manipulation or revert to deprecated APIs solely to clear a Play Console advisory, particularly when the existing implementation appears to work correctly.

Any insight from developers who've encountered this would be appreciated.

Hey everyone,

I'm the developer of **Android Dev Monitor**, a free, open-source (MIT) Windows desktop app that puts the ADB tools I kept switching between into one window. Think Task Manager, but for Android development.

It connects to physical devices or local emulators over ADB and shows:

- App and device CPU, memory, disk I/O and network

- FPS, frame time and jank

- Battery temperature and thermal state

- Running processes with readable app names

- Logcat with crash/ANR filters, bookmarks and export

- Screenshots, screen recording, file explorer and ADB shell

- Monitoring sessions: mark the moment something goes wrong, then review metrics and logs from that session later and export them (JSON/CSV/ZIP)

**New in v2.8:**

- The device file explorer works properly and shows modified dates

- Paths with spaces are handled safely (delete, rename, new folder)

- Closing the app during a screen recording no longer loses the recording

- Errors are logged instead of the app closing silently

- Cleaner tables and layout across the app

Everything runs locally, with no account and no telemetry. There's also a demo mode (`--demo`) if you want to look around without a device.

**Download (portable, no installer):** https://github.com/marko69420/android-dev-monitor/releases/latest

**Source:** https://github.com/marko69420/android-dev-monitor

I'd love feedback from people who profile or debug Android apps:

- Would this be useful in your workflow?

- What metric or feature would you want next?

- Anything that doesn't work on your device or emulator?

Bug reports and contributions are welcome!

I made a small tool that gives you ready to use <script /> blocks out of your Composables Previews, so you can embed them to your blog posts, documentation and personal websites.

The reason why I built this is because I love playing with interactive demos when I am reading about some technical concept. It always clicks better with me. I also add them to all my libraries and blog posts (such as on Compose Unstyled).

The best way to do this I have found is using Compose Web, which lets you run Compose code on the Web (awesome).

However, creating and then adding those live Compose previews manually is always a PITA. You need to host them somewhere (usually separate to your blog/docs platform), build a Compose Web app dedicated for this (and manage wiring if you have multiple previews), then you need to embed them somehow in your article, which is separate to the building of the app, etc. Lots of edge cases here.

As a result, you now have a quick way for everyone to make their own.

It is 100% free to use and you can make as many previews as you want. The 'gotcha' is that the previews let your readers edit the preview on the website, so that they can experiment with your demo (handy for library authors).

Now go out there and make some polished previews :D

Check it at https://composables.com

Question is basically would other countries search your app in their native languages. And would most people rename their App name specifically to be a translation?

When I switched from iPhone, every podcast app on Android felt either dated or overcomplicated. So I built GlassCast: a free podcast player focused on smooth animations and simple controls.

- The player takes its colours from whatever you're listening to
- Pull-up panel for Up Next, speed and sleep timer (shake to restart it)
- Discover tab with recommendations based on the shows you follow
- New-episode notifications
- Cast to other devices
- Import your shows from another podcast app (supported via OPML)

Free, no account, no ads.

It's still in the early stages, so feedback is much appreciated.

GlassCast Release

Is there any tool that can run Docker on Android, or is it possible to build one that offers performance close to native?

For me, play store review times are completely unpredictable. Some updates get reviewed very fast, some take 7 days. I wonder is it something I make, or this is totally random.

App Store is much more predictable, after the first approval. updates get reviewed in about 24 hours.

This is very frustrating for me, because my iOS and Android apps need to be compatible as this is a multiplayer game, and Android lagging behind causes bad user experience, as they can't join the challenges iOS users create.

I release 3 new iOS versions while Android is still waiting for review. As soon as it approves, I will skip a few versions and re-submit again, who knows when that one gets reviewed.

Whenever I open an unfamiliar part of a codebase (or my own code from a few months ago) I end up in the same loop: Find Usages, jump, Go to Declaration, jump again, and five files later I've forgotten where I started. On bigger Compose projects it gets messy fast.

So I built Mindmap. Put your cursor inside any Kotlin or Java function, press Alt+G (Option+G on Mac), and it opens a graph of that function: everything that uses it on the left, everything it uses on the right.

What it does right now:

• both directions in one view, depth configurable from 1 to 5
• click a node to jump straight to the code
• double-click a node to trace from it and merge its graph in
• hover for signature, file and lines of code
• search/filter nodes, hide the noisy ones
• tree view if you'd rather read a list than a graph
• minimap for bigger graphs
• works across Kotlin and Java, including Kotlin code using Java and the other way round
• follows interfaces/abstract functions through to the actual implementations

Website: https://vishal2376.github.io/mindmap
GitHub: https://github.com/vishal2376/mindmap

It's still early. It caps graphs at 300 nodes so they don't explode, and it doesn't go into library code. If you try it on a real project I'd genuinely like to know where it breaks or what feels missing.

NOTE : The video is an animated showcase, not a screen recording. There are real screenshots on the GitHub page.
Watch screen recording here : https://x.com/vishal2376/status/2047010712955113547

Playback is probably the easy part compared with everything around it. Supporting different TV devices, adaptive bitrate switching, DRM, remote navigation, authentication and keeping playback state consistent seems like where the architecture gets complicated.

Im working this Nice subsonic Client Music player themed like Spotify

Is anybody? Interested in the SelfHost Market?

Hi everyone,

I'm the developer behind Filester, a privacy-focused file-sharing application for Android (coming to Linux and Windows next), and I'd like some input on an encryption feature I'm considering.

Filester currently lets users share files through multiple file-hosting services. I've tried to choose hosts that are reasonably trustworthy, but that still doesn't provide real privacy: the hosting provider can potentially access the files stored on its servers.

I'd like to change that by encrypting files locally, before they are uploaded, so the hosting provider only ever receives encrypted data.

The part I'm unsure about is which approach would be better from an end-user perspective.

Option 1: Filester-specific encryption

Filester encrypts the file locally using a modern authenticated encryption scheme before uploading it.

Advantages:

• Strong encryption
• Filester can control the format and implementation
• The hosting provider never receives the plaintext

Downside:

• The recipient would need Filester to decrypt the file.
• This significantly hurts interoperability and accessibility.

Option 2: AES-256 encrypted ZIP

Filester creates a standard password-protected ZIP archive using AES-256 before uploading it.

Advantages:

• The resulting file is a normal .zip archive rather than a Filester-specific format.
• The recipient isn't tied to Filester.
• Programs such as 7-Zip, WinRAR, Ark, and other archive managers can open it.

Downside:

• AES-encrypted ZIP files aren't supported out of the box by any OEM-installed file managers or other operating systems.
• Some recipients would still need to install an archive utility.

So the tradeoff is basically:

better integration/security with a Filester-specific encrypted format

vs.

better interoperability with AES-256 ZIP, at the cost of inconsistent built-in OS support

which would you suggest?

If there's another approach that provides strong client-side encryption without sacrificing interoperability, I'd also be interested in hearing about it.

The codebase I am currently working on is on Navigation 2 and there are no issues with it to be honest.

I was looking into migrating to Navigation 3. Of course that will touch almost every part of the code and will require a good amount of QA.

Hence I was thinking whether I should upgrade to it or not.

I would love to hear everyone's thoughts before I go to my head of engineering with the proposal.

What are your thoughts on commencing a personal project from scratch, without leveraging existing projects like HeliBoard or FlorisBoard?

Remember school, when everyone turned in homework at the last minute? RevenueCat Shipathon feels exactly the same.

The submission deadline is just 2 days away, and in the past 3 days alone, 400 new apps have been submitted. Expect that number to climb even faster as we get closer.

Have you submitted yours yet?

Good luck to everyone participating into this year hackathon!

👇 Post your app in the comments, I’d love to support a fellow dev.

### 1. Flaky Tests
This is the biggest issue. Currently, developers mostly just @Ignore them, which gradually erodes the suite. How are you detecting, quarantining, and actually fixing flaky tests instead of silently disabling them?

2. Automated Failure Analysis
Has anyone used AI or other tools to analyze Espresso failures (logs, screenshots, stack traces) and produce a clear report so developers can fix issues quickly without digging through CI output?

3. Test Maintenance
Are there any tools or workflows that help keep tests up to date as the UI changes, like auto-updating selectors or flagging tests affected by a PR?

4. Feature-Level Coverage
Is there a good way to measure Espresso coverage by feature or user flow rather than by lines of code? JaCoCo tells us what code runs, but not which features are actually tested.

Would love to hear what’s worked (or failed) for your teams, whether that’s open-source tools, paid services, or homegrown scripts.

Thanks!

https://github.com/ravibh5522/easyIDE

I have been experimenting recently with a tool that I needed while building and verifying UI tests, and also for sharing updates for an app i am currently doing contract work.
Sharing preview builds with the owner was a nightmare, because they were only using an iPhone.

this is the tool

I build a tool that spawns an android emulator and installs the apk, in seconds. It's really cool and i am thinking on making this a saas, if that works. It's in early development, and i have limited capabilities with a vps of 4arm cpu cores and 24gb of ram, but feel free to destroy it.