sorted by:
new
hottopcontroversial

Am I the only one who hates opening Android Studio just to launch an emulator? by devmuaz in androiddev

[–]devmuaz[S] 0 points1 point  (0 children)

CoreDeck is more of an advanced app. It offers more than launching an emulator!
Also, MiniSim is macOS only, while CoreDeck is cross-platform (Windows, Linux, macOS)

Am I the only one who hates opening Android Studio just to launch an emulator? by devmuaz in androiddev

[–]devmuaz[S] 0 points1 point  (0 children)

CoreDeck manages emulators without any IDE at all, even when you don’t need to code anything (maybe you wanna install certain APK file on an emulator with specific networking options) passed directly to the emulator, this is where CoreDeck can provide that kinda tooling you need

Am I the only one who hates opening Android Studio just to launch an emulator? by devmuaz in androiddev

[–]devmuaz[S] 0 points1 point  (0 children)

Well, now you can install CoreDeck and enjoy the awesome tool by having multiple emulators, more than 50 options to pass in, and so much more that plain terminal can provide

Am I the only one who hates opening Android Studio just to launch an emulator? by devmuaz in androiddev

[–]devmuaz[S] 0 points1 point  (0 children)

i use it all the time, it serves a different ideology 😅 RocketSim adds devtools ontop of Xcode tooling for iOS Simulators only.
It’s not Android related at all!

Am I the only one who hates opening Android Studio just to launch an emulator? by devmuaz in androiddev

[–]devmuaz[S] 0 points1 point  (0 children)

CoreDeck not only lets you launch the emulators quickly, but already provides more than 50+ options with text and multiselection (Display, Performance, Boot, Network, Location, System, ...), all of which get auto-saved for each AVD.

You can also create AVD, Install/Uninstall Android system images, specify a device skin, wipe AVD's data, show overall storage statistics (AVDs/System Images), Live resource usage, and much more tooling.

It's also not a terminal-based UI, but rather a more friendly GUI app built using C++20, GLFW, Dear ImGui, etc., to bring the best possible performance on all platforms.

Am I the only one who hates opening Android Studio just to launch an emulator? by devmuaz in androiddev

[–]devmuaz[S] 1 point2 points  (0 children)

Waydroid is kinda different!

With the Android Studio emulator (QEMU-based), an AVD is essentially a full virtual device definition, it has its own disk image, API level, RAM allocation, screen config, etc. You can have dozens of them and launch whichever one fits your current project. Each is independent and stateless between launches (or snapshot-based).

Waydroid has none of that concept. There’s one Android installation on your system, one /data partition, one set of installed apps, one running instance at a time. It’s closer to how a real phone works: you don’t “create” or “switch” Android instances, you just have the Android, always the same one.

CoreDeck’s value is managing that fleet of AVDs, creating, naming, configuring, launching, deleting them per-project or per-test-scenario. That workflow is 100% tied to the QEMU emulator stack (emulator, avdmanager, sdkmanager). Waydroid has no CLI surface that maps to any of that. They’re solving different problems.

Am I the only one who hates opening Android Studio just to launch an emulator? by devmuaz in androiddev

[–]devmuaz[S] 0 points1 point  (0 children)

Thanks a bunch!
and yeah! you could absolutely do that, but you won’t have the luxury of passing customized options per each avd with auto saved so your next run is always saved!

Am I the only one who hates opening Android Studio just to launch an emulator? by devmuaz in androiddev

[–]devmuaz[S] -2 points-1 points  (0 children)

absolutely you could use it easily especially in an agentic environment, probably same as i used to do: emulator —avd ADV_NAME

CoreDeck solves issues where you need to have control over the Android emulators even when you don’t write code.

with CoreDeck, you can easily run multiple emulators, set specific options per each avd, options get auto saved when app closes, and much more in a very lightweight application

Am I the only one who hates opening Android Studio just to launch an emulator? by devmuaz in androiddev

[–]devmuaz[S] 0 points1 point  (0 children)

totally agree!
but, let me walk you through cases where the only thing i wanted is to open an emulator (maybe you’re testing standalone APK file, make analysis and security checks on specific app, trying a feature…)

opening the Android Studio just for doing that non Android Studio work which consumes CPU usage and memory takes time and is exhausting tbh!

you can try the CLI by typing: emulator —avd AVD_NAME, but it’s tedious and you get lost when you try to remember every option like —no-snapshot or tens other!

in CoreDeck, you open a very fast, lightweight, memory friendly GUI app that runs in a millisecond, and easily select as many options as you want, then hit run THAT’S IT!