Creation of Android emulators

[baltpeter]

Now that we're using andromatic, the user doesn't have the SDK binaries in their PATH anymore. This doesn't really matter for most of them, but it is a problem for emulators. The appstraction README currently instructs you to create an emulator like this:

https://github.com/tweaselORG/appstraction/blob/83418768e64c26ac135d4a1d53644cff1f7ea3a1/README.md#L78

This won't work anymore. How do we want to proceed?

• Do we recommend people create the emulator in Android Studio (quite annoying, takes a while)?
• Pr do we implement a quick emulator creator (in appstraction? in CA? in CLI directly?)?

[zner0L]

I think we basically already kinda implemented a emulator creation function in CA. I should be easy to abstract that out and then expose it in CLI also. appstraction seems like the wrong place for it. And I think we could still mention that you can also create the emulators in Android Studio as well.

[baltpeter]

I think we basically already kinda implemented a emulator creation function in CA.

Um, we have a way to start emulators in CA, but we can't create them yet.

[zner0L]

Ah, yes. Of course. Well, I still think CA is the right place for it.

[baltpeter]

I'm really not sure whether I see this as fitting CA. What does this have to do with traffic analysis? But I'm not quite sure where else to put it either:

• appstraction sort of fits in that it is an abstraction around an Android feature, but also not really because this will never be available for iOS (certainly not with the same interface), and it would also be separate from the platform APIs.
• Having it in CLI only would be annoying for everyone who wants to write scripts instead of using a CLI.
• Maybe andromatic would fit best? After all, this would again also have to deal with annoying names of packages you have to install (e.g. I wouldn't want users to have to figure out system-images;android-30;google_apis;x86_64 themselves. I'd want to build some sort of abstraction around that).