r/androiddev • • 12h ago

Anyone have any idea why my Android Studio emulator isn't refreshing the layout automatically when I save?

2 Upvotes

Literally just started using it.

EDIT:

For anyone else having this problem you have to click on the checkmark / cycle icon in the preview panel and select refresh automatically


r/androiddev • • 3h ago

I built WebView Inspector to inspect WebView URLs and navigation right inside Android apps

1 Upvotes

Hi everyone,

I built WebView Inspector, an Android library that adds a floating inspector to your app so you can see what your WebViews are loading.

It lets you:

  • Highlight a WebView in a card, banner, or full-screen page, inspect its query parameters, and copy its exact URL.
  • Review observed navigation history and revisit saved records after leaving the screen using Live / Recent.
  • Inspect the URL and headers your app supplied through an optional loadUrl helper.

My usual workflow was to search Logcat for the URL, copy it, and open it in Chrome to see what had loaded. That gets tedious when reproducing an issue, especially with multiple WebViews on the same screen. I wanted to check the URL and retrace navigation directly inside the app.

Basic inspection needs one installation in your Application. The optional load helper adds capture of app-supplied URLs and headers. Setup and usage

I see it fitting into the debugging workflow alongside these tools:

  • Chucker shows the Android app’s OkHttp requests and responses. Chucker
  • WebView Inspector shows which URL a particular WebView loaded and where it navigated.
  • Chrome DevTools shows requests made inside the web page, including fetch/XHR calls and their responses. WebView remote debugging

Navigation capture covers observed top-level URLs. Older WebView providers use sampling, which can miss fast redirects. Captured headers are the inputs your app supplied, and records stay in process memory. Capture details

Version 0.5.0 supports Android API 24+ and is available on Maven Central, with a matching no-op artifact for production builds. Release details

The repository includes the source code, integration instructions, and a sample app. Explore WebView Inspector on GitHub

I’d be interested to hear how others handle WebView URL debugging and which cases you find hardest to inspect.


r/androiddev • • 17h ago

Question What tools do you guys use to design professional high-end Android app UIs?

1 Upvotes

Hey everyone, I'm new to Android app development and looking for some advice. I've been using Android Studio, but honestly, its UI designer feels more like making a PowerPoint slide, not the high-end quality UIs that i see in other apps.

What tools do you guys use to create app UIs? And are there any good tutorials or guides you'd recommend for someone just starting out?


r/androiddev • • 20h ago

Open Source I'm experimenting with an open-source Android flight recorder for diagnosing user-journey failures

1 Upvotes

Hey everyone!

I've been working on an open-source project called Argus - SystemSleuth.

The idea started with a problem I've encountered while thinking about application debugging:

When a user reports that something didn't work, a stack trace or API error often tells us where something failed, but not necessarily whag happened across the enire user journey.

For example:

A user selects a PDF, attaches it to an email and taps Send. The upload times out.

A conventional log might tell us that an HTTP request failed. But understanding the sequence of user actions, screen transitions and network events leading up to that failure can be equally important.

I'm exploring whether a structured runtime trace can make this kind of debugging easier.

What Argus currently explores:

● An in-memory, bounded flight recorder for capturing session events.

● Android Activity/Fragment lifecycle and user-interaction tracking.

● Network-event instrumentation through OkHttp.

● Session-level diagnostic analysis using AI providers, with a heuristic fallback.

● A sample Android app that reproduces an attachment-upload timeout and demonstrates the diagnostic flow.

A little context about it's current state:

This is still an early-stage experiment, not a production-ready observability SDK. The expected-workflow-versus-observed-execution comparison is also still a work in progress, rather than a fully integrated Android feature.

Privacy and sensitive-data handling need further work too, so I'd currently treat it as something to experiment with using test data rather than real user sessions.

Github: https://github.com/Deven264/Argus-SystemSleuth

It's liscensed under Apache 2.0.

I'd particularly appreciate feedback from people working on Android, debugging tools, observability or developer infrastructure.

  1. Do structured user-journey traces provide meaningful value beyond conventional logs and crash reports?
  2. Which events would you consider essential to capture when diagnosing application failures?
  3. What privacy safeguards would you expect before using a tool like this in a real application?

I'm sharing this to get honest technical feedback and improve the project. Criticism and suggestions are welcome!

Disclosure: I'm the developer of Argus.