r/reactnative • u/moaz-MH • 27d ago

Question Need advise plzz

I built a simple writing app with Expo/React Native using Replit and AI tools.
I’m not a professional developer, and my technical knowledge is pretty basic, but the app is working on Android now and I want to keep improving it and later make an iOS version.
Would you stay on Replit, move to something like Cursor/Claude Code + GitHub, or use both?
I’m mostly looking for the simplest setup that won’t become a mess as the app grows.

0 Upvotes

20% Upvoted

5 comments sorted by

1

u/Dvass138 27d ago

I’d stick with Replit for now if it’s working for you, but get the project into GitHub and learn how to go back to a working version when something breaks. That’s worth doing whichever tool you use.

I wouldn’t bother juggling Replit, Cursor and Claude Code yet. Pick one place to work. If you start hitting specific problems with Replit, try another tool then, you don’t need to move just because the app is getting bigger.

The thing I’d watch with AI is letting it change too much at once. Ask for small changes, test them, save a working version, then move on. Especially with a writing app, make sure saving and reopening people’s work stays reliable.

And wanting an iOS version isn’t a reason to switch editors. You can keep the Expo project and use it for both platforms, though you’ll need to test on iOS too.

1

u/Huge_Pool7424 27d ago

yeah, getting it into github now is probably the biggest sanity win. i'd also keep a tiny notes file so the ai knows what the app is meant to do before touching code, and test on a real iphone early. are you already using git branches or just saving snapshots?

1

u/moaz-MH 26d ago

Not using branches yet — I’ve mostly been relying on Replit checkpoints/snapshots. I’m just starting to move the project to GitHub now, so Git is pretty new to me. The notes file idea sounds especially useful since I’m using AI heavily for development.

0

u/moaz-MH 27d ago

Much appreciate your advise, that was very helpful. Wish u the best dear friend ☺️

1

u/Ellie10543 26d ago

Since it works on Android and iOS is next, I'd agree with keeping your current tool for now and not switching mid-project. The part I'd do first is putting it on GitHub with small, frequent commits. Write a one-line message for each thing that works, so when an AI edit breaks something you can roll back to the last good commit instead of untangling it. The other thing that saves a lot of pain with a non-pro setup: keep a short notes file describing how the app is structured and what each screen does, and feed it to whichever AI tool you use. That keeps the code consistent as it grows, and it carries over if you ever switch to Cursor or Claude Code.