It takes about 10-20, sometimes even more attempts to fulfil a request correctly. Even in the smallest tasks. It barely happens on plaforms like base44. Sometimes I think that it set to begginer mode or something. I can spend hours on same generic error fix without results.
1 Like
Yes, Firebase Studio is currently in the “Preview” phase. Therefore, such problems are often encountered. I can give you some advice to minimize them. I hope you find it useful.
- If the file is long in code, there is a high risk of errors. Instead, try separating some of the functions in the file into different files and call them in the main file. (You can also ask the gemini to do this. If your project has grown, it will be a bit of a hassle, but you will be much more comfortable once you have done it.) This way you can get the desired functions updated with fewer bugs.
- Instead of asking for extensive requests all at once, break them down. Take it step by step with smaller task steps and once you are sure that you have done one step correctly, move on to the next step.
- If it didn’t do something right, go back to the old version and tell it what it did wrong. Tell him that you had to revert to the old version because of his mistake and that you will try again. When I tell him that, he is more careful about it.
My experience may make your work easier. I hope that at least until Firebase studio is much improved, you will have fewer bugs.
You can also try these methods for more consistent results:
3 Likes
Thanks for the tips. The problem is more noticable when errors are already created. The AI has hard times with fixing it’s own made errors, although it mention them correctly and knows exactly what’s wrong. It’s like it has restricted codding skills and I find my self using Calude to “help” it.
1 Like
In some cases, the response rate of prototyper, comes down to your connection speed and computer speed. For example if you reload the page after some minutes while the prototyper still shows as running, you will see it completed. It is due to server completing the task but your computer is not able to function fast enough. But This is probably a bug in ui, a fix would be good.
Like @bevren15 said, Divide and Conquer method works. What you do is split up any file that is larger than 500 lines. It becomes so much faster and easier to debug. But you may be introduced with import problems when first doing it.
1 Like
And Also, all AI vibe coding tools lack [claude, openai, cursor, etc]. I find myself using all of it because they each have their strengths and weaknesses. It is fine if you have to use other ai tools. AI is a library that a problem solver uses. Don’t rely on it too much.