E2e developer journey gaps on embedded Android dev [Spike]

Map and study e2e developer journey gaps on embedded Android development. Setting up the environment should be easy and logical, developer needs to be able to 1) build, 2) deploy, 3) debug and repeat 123 in an easy and well documented manner.

As customer put it, "I wish it was as easy and versatile as targeting eLinux".

Question: How does the envisioned Qt workflow with QDS+Creator land here?

Outcome of this study should be more User Stories and Tasks, perhaps few Epics too. The study needs to cover Qt promoted workflow based on Qt tools (Qt Design Studio, Qt Creator) but it may also end up recommending Android tools such as e.g. Android Studio.