[jen_h]

[Full disclosure, work @ Firebase]

But try this:

Open up a blank Flutter template in Studio: https://studio.firebase.google.com/new/flutter

After everything initializes and your Android and web previews set up, open chat by clicking the little Gemini spark at the bottom of the workspace and then add your prompt.

YMMV, but I got a very basic, but working chess clock in one shot with "Can you replace this sample Flutter project with a fully-functional chess clock that works on Android and on the web?"

[tymscar]

That's how I've done it when it did not work. I did, however, go easier, one by one. I first made a simple countdown. Then I made it count down from 10 minutes to 0. Then I created 2 of them. Then I put them side by side. Then I did the logic, one counterstarting each other. Every step of the way, it was filled with loads of errors and loops out of which the ai couldnt get out, to the point where I would need to go there and fix it myself. Errors ranged from logical, to super simple syntax issues, such as missing colons, or brackets.

[tymscar]

I have tried again step by step with what you said here, copy pasted the prompt even and after a couple changes here and there it loses the plot and gets stuck and seemingly no amount of prompting can get it out.

To make sure I tried 3 times in a row. Same result.

I feel like in the emperors new clothes story.

[jen_h]

Well, not conpletely Emperor’s New Clothes: after I got my basic chess clock, I asked for skeuomorphic changes…I got a fantastic “next steps” summary in return…but when I said “Go on ahead, your choice,” it created an incompatible dependency nest trying to add clicky sounds.

Gemini actually dug me out of it, though, with additional prompting (this kind of surprised me; I assumed I’d have to eventually really step in). After all that distraction, though, I had to reset the convo to get it to focus on the files again.

Totally understand that you might be too annoyed at this point, but if you do have a few minutes, it’d be amazing to file a case @ https://firebase.google.com/support/troubleshooter/studio for the team to dig into.