Good. I have some questions though: 1.
AndroidDeveloperLB
1

1. Why can’t the IDE handle SVG by just having the file inside, and converting it to what’s needed behind the scenes?

What if the conversion fails? I’d prefer the conversion to be explicit so that it can report errors to you

2. Why do we have to import the SVG files one after another, and without the ability to tell which density it was used with (meaning we have to calculate the correct size)?

We hear the demand for batch convert. You can already use the CLI version to do this. Not sure what you mean about density? You shouldn’t have to manually calculate anything, it should use the SVG’s size.

3. For SVG, we can see the files on the file manager of the OS …

We also hear the feedback on wanting to view multiple assets… nothing to announce as yet.

4. Since VectorDrawable is so restricted, why not create a professional tool for designers, that is directly creating those, instead of the need to convert from SVG, which is sometimes not so optimized ? It’s best to start now with it, while it’s still simple compared to SVG…

This would be a major undertaking and have significant opportunity cost. I’m not sure that’s how we could best deploy our resources nor if this is something that designers would want.