Replit Agent gave you a web app when you wanted mobile, or code that looks right but breaks on device. Here is how to redirect the Agent and clean up its output for an iOS-bound project.
Replit Agent is strong, but it is a probabilistic tool that fills gaps with assumptions. Many wrong-output problems trace back to an ambiguous prompt.
Its default gravity tends toward web. If you do not explicitly steer it to React Native and Expo, it may produce a web app, which is the wrong target for an iOS-bound project.
It also optimizes for a working preview, not necessarily for clean, secure, or device-ready code. Output can look correct yet hide issues that only appear on real hardware.
Understanding these two tendencies, a web default and a preview-first bias, is the key to both preventing and fixing wrong output.
Symptom: you wanted an iOS app but got HTML/CSS or a web React app with no path to a phone.
Cause: the prompt did not pin the framework, so the Agent chose its web default.
Fix: state the target explicitly. Re-prompt with something like "this must be a React Native app using Expo, targeting iOS," and ask it to migrate or regenerate accordingly.
If the project is small, regenerating with a precise prompt is often faster than converting web code by hand. For larger projects, ask the Agent to introduce Expo/React Native incrementally and verify each step in Expo Go.
Symptom: everything looks fine in Replit's browser preview, then layout, navigation, or networking breaks on a real iPhone.
Cause: the browser preview is not iOS. Differences in safe areas, touch handling, storage, and networking surface only on device.
Fix: test in Expo Go early and feed the real symptoms back to the Agent. Describe exactly what is wrong on device, for example "the header is hidden behind the notch," so it can apply the correct fix.
For networking, watch for hardcoded localhost or HTTP URLs, which work in preview but fail on device. Point the app at a deployed HTTPS endpoint instead.
Symptom: the app mostly works but has intermittent bugs, stale data, or state that does not update correctly.
Cause: AI-generated state management can be subtly wrong, mixing up effect dependencies, mutation, or async ordering.
Fix: isolate the bug and give the Agent a precise reproduction. "When I add an item then delete it, the count is off by one" is far more fixable than "the list is buggy."
Review the state logic yourself. These bugs often live in a few lines of effect or reducer code, and a human read frequently spots what the Agent missed.
Symptom: on review, you find hardcoded keys, missing input validation, or auth that trusts the client.
Cause: the Agent optimizes for a working demo, and secure-by-default is not guaranteed, especially around auth, secrets, and data access.
Fix: treat every auth, payment, and data path as requiring a manual security pass. Move secrets to Replit's secrets manager and out of any client bundle.
Ask the Agent specifically to add server-side validation and to stop trusting client-supplied permissions. Then verify it actually did, rather than assuming the change landed correctly.
Symptom: you fix something, ask for another change, and the original issue comes back.
Cause: the Agent may not retain full context of your constraints across a long session, so it reverts to its defaults.
Fix: restate critical constraints in the prompt that triggers the change. Reminding it "keep using Expo, keep secrets server-side" each time reduces regressions.
Use version control checkpoints aggressively. When the Agent undoes good work, a committed checkpoint lets you recover the correct state instead of re-fixing from scratch.
There is a point where another round of prompting costs more than just editing the code. Learn to recognize it.
If you have re-prompted the same fix two or three times without success, open the file and make the change directly. You often understand the bug better than the Agent does by that point.
Use the Agent for scaffolding and broad strokes, and your own hands for precise, load-bearing logic. That division of labor plays to each side's strengths.
Remember the bigger picture: this is React Native bound for iOS through EAS, not native Swift. Some problems are best solved by understanding the Expo and React Native model directly rather than asking the Agent to guess again.
Symptom: the app feels fine in the browser preview but stutters, lags, or drains battery on a real iPhone.
Cause: the Agent optimizes for something that works, not something that is efficient. Heavy re-renders, large lists rendered all at once, or oversized images can be invisible on a fast desktop preview yet obvious on a phone.
Fix: profile on a real device and feed concrete symptoms back to the Agent, such as "scrolling the list is janky on an iPhone." Ask it to use list virtualization for long lists and to avoid unnecessary re-renders.
Review how data and images are loaded. Pulling everything at once or shipping full-size images is a frequent cause of sluggishness, and it is usually a small, targeted fix once you know where to look.
Symptom: a feature the Agent added throws errors on device or simply does nothing, even though it looked fine in preview.
Cause: the Agent reached for a web-oriented package or a browser API that has no place in React Native. It can run in the browser-based preview but has no equivalent on a real device.
Fix: identify the offending dependency and ask the Agent for a React Native or Expo-compatible alternative explicitly. Many web libraries have direct mobile counterparts.
When in doubt, prefer libraries from the Expo and React Native ecosystem. Pinning the Agent to that ecosystem in your prompt prevents it from drifting back to web-only packages in the first place.
Front-load your constraints. Name the framework, the target platform, the data shape, and any security rules in your first prompt.
Work in small, reviewable increments. One change per message makes wrong output obvious and easy to roll back.
Test on a real device early and often through Expo Go, so the Agent's preview-first bias does not hide device-only bugs until late.
And always review before you trust. AI-generated code is a fast first draft, not a finished product; the human review pass is what turns Agent output into something you can responsibly ship to the App Store.
Because the prompt did not pin the framework and the Agent defaulted to web. Re-prompt explicitly: state that it must be a React Native app using Expo, targeting iOS. For small projects, regenerating with a precise prompt is often faster than converting web code by hand.
The browser preview is not iOS, so safe areas, touch handling, storage, and networking can differ. Test in Expo Go early and feed the exact on-device symptom back to the Agent. Watch especially for hardcoded localhost or HTTP URLs, which fail on real devices.
Not without review. The Agent optimizes for a working demo, not secure-by-default. Treat every auth, payment, and data path as needing a manual security pass: move secrets server-side, add server-side validation, and never trust client-supplied permissions.
It may be losing track of your constraints over a long session. Restate critical constraints in each prompt, and use version control checkpoints so you can recover a good state. After two or three failed attempts, it is usually faster to edit the code yourself.