Hey everyone,
I’ve been working on Android Dev Monitor, an open-source Windows desktop tool that I originally built because I wanted a simpler way to monitor Android apps without constantly jumping between different ADB commands and tools.
The idea is basically Task Manager, but for Android development.
It connects to physical Android devices or local emulators through ADB and lets you monitor things like:
- App and device CPU usage
- App / device memory usage
- Disk read/write activity
- Network activity
- Frame statistics / performance data
- Battery and thermal information where supported
- Running processes
- Logcat / logs
- Screenshots and screen recordings
- ADB shell
- File explorer
- Monitoring sessions, markers, alerts and exports
One workflow I wanted to make easier was reproducing a performance problem in an app, marking the exact moment something happened, and then being able to look at the metrics and logs from the same session afterward.
It also has a demo mode, so the UI can be explored without connecting an Android device.
The project is currently an early preview, so some metrics depend on the Android version, device manufacturer and available ADB permissions. I’m still improving it and would especially like feedback from people who actually work with Android profiling/debugging.
GitHub:
https://github.com/marko69420/android-dev-monitor
I’d be interested to know:
- Would a tool like this actually be useful in your Android workflow?
- What feature would you expect from something described as a “Task Manager for Android developers”?
- Is there anything in the current UI/workflow that you would approach differently?
Any technical feedback, bug reports or contributions are welcome.
submitted by /u/skrixynine[link] [comments]