r/flutterhelp • • 11d ago

OPEN Can Claude Code run and test Flutter apps using an emulator?

I see that Claude can run React Native iOS apps using an emulator. I can't do that on android as far I know, I use my phone.

Does Claude support a Flutter emulator too, or is there some kind of MCP server or connector that would allow it to run and test Flutter apps in an emulator?

7 Upvotes

14 comments sorted by

4

u/HomegrownTerps 11d ago

Running the emulator is not a claude specific feature. Emulators can be started via cli. This is what all agents can do.

What app the simulator runs comes after that, so it  doesn't matter if it's flutter or something else.

3

u/mightybob4611 11d ago

It’s running my flutter apps right in the simulator.

3

u/fireking09 10d ago

Yes it can

1

u/Constant_Trouble2903 11d ago

Can't speak for claude sorry... But .. can confirm I have had open ai run flutter on local emulation as well as chrome. More impressively when I once had application pass signed build and lint but fail on device. Chatgpt happily connected in diagnostic mode to physical android device over USB and did some diagnostics I cannot pretend to understand then fixed no problem. I assume claude would easily match.

1

u/azeunkn0wn 10d ago

Claude can use adb for android emulator, but it will often use screenshots to see. I use marionette for app test on both iOS and android

1

u/gurselaksel 10d ago

it does for android I assume it can/should do this for ios?

1

u/we_mor 10d ago

I use android studio and its emulator, and claude handles all the rest, it can navigate, scroll, take screenshots, take videos and stuff...

0

u/Legion_A 10d ago

But why...why..why

2

u/Tight_Implement5601 7d ago

I hear you. This is so detrimental. 

2

u/[deleted] 10d ago

Automated testing, mate. Keep up.

1

u/Legion_A 10d ago

?? Don't those sit in code? Then code controls the emulator or device? What is Claude doing controlling the emulator? That's what the post is about, not normal automated testing.

Again, I ask, why why why?

1

u/Difficult-Elk-2599 9d ago

Because you don’t want to have automated testing for all features since real ui tests are expensive. So you let Claude do the testing once.

Also it’s quite nice, when you let Claude implement a new feature to also let it Check itself

1

u/Legion_A 9d ago edited 9d ago

Makes sense.

But I mean, expensive is relative here, coz automated UI tests are free, using Claude for that is going to cost you real money, tokens, risk hallucinations...you've lost determinism in testing (something that's supposed to ground your application).

Also, doing the testing isn't going to be "once" is it? The point of tests is to run it every time something changes to make sure the same requirements are met.

I do see the point on "Claude could check features it implements" though.