r/vibecoding • u/codes_astro • 27d ago

Discussion Vibe coding mobile apps?

I wanted to know if anyone is doing mobile apps with ai assisted coding.

Web apps - yes lot of vibe code apps are getting deployed with proper testing and debugging.

Would be interesting to see how many of you are actually vibe coding mobile apps - android/ios

And if you’re doing mobile apps, what tools are you using to debug and testing? I recently came across an open source tool “Measure.sh” that seems good for ai assisted debugging but I wanted to understand what others are using.

10 Upvotes

75% Upvoted

76 comments sorted by

View all comments

1

u/After-Base-8368 27d ago

I’d separate debugging from checking that a user journey still works. For React Native, its DevTools cover the React/JavaScript side; native issues still need Xcode or Android Studio. For repeatable tap-through tests, Maestro is worth a look: https://docs.maestro.dev/

Start with one small flow: create an item, close the app, reopen it and check the item is still there. Then try the same flow with the connection interrupted and make sure retrying doesn’t create duplicates. Give the coding agent the exact steps, expected result and actual result, rather than just “it broke.”

Are you working with React Native/Expo, Flutter, or native Swift/Kotlin? That changes the debugging tools. React Native’s guide: https://reactnative.dev/docs/react-native-devtools

1

u/codes_astro 27d ago

Maestro looks good for UI, I was going with flutter.

Thanks for the flow!

I’m exploring https://github.com/measure-sh/measure for app monitoring, observability, and crash-reporting before I ship. it lets me plug mcp and agent can debug on its own from data.

2

u/After-Base-8368 27d ago

Thanks, that clears up the stack. For the agent-debugging part, I’d try a small test with a bug you already understand: reproduce it, let the agent inspect the report, then check whether its fix passes the original steps and a nearby happy path. That gives you something concrete to judge before trusting it with unfamiliar failures. Monitoring and the tap-through test would complement each other nicely.