Over the past few days, I’ve frequently seen posts about a new tool — Firebase Studio. It positions itself as an AI tool for faster prototyping. As usual, you write the prompt and get a result that you can publish and share with colleagues and friends. What caught my attention was the support for Android Studio, so I decided to try it.
I was surprised to see how it loads a virtual Android Studio and mirrors the regular interface in the browser. Just running this setup virtually takes around 30 second, and the result is an Android Studio instance with the Gemini plugin preinstalled and configured for the project. It’s not bad, especially if you want to quickly develop something on a slow machine — but it’s not the kind of setup that gives you the vibe or speed for fast iteration. The Problem isn’t with this tool — the issue lies in Android development itself, which requires a lot of resources, time, and addition tools that slow down the process.
It seems that building a mobile application solely through prompts and then improving it through prompting is not in the nearest future. Because it isn’t possible to achieve this without improving and simplifying regular mobile development. We can only speed up specific parts of development, for example, routine tasks, mocking specific screens, or solving particular business problems. This is a good article with examples of that point.
You can find me in X, GitHub, medium or LinkedIn. Thanks for your time and see you in next post.
