Build a route app in tiny testable pieces

A Manus user burned through 8,100 credits and over 8 hours without finishing a working navigation app.

Done with Manusยท Advanced

What they did
On their first day with Manus, a commenter tried to make an app for directions, map viewing, lane guidance, and audio turn-by-turn help. Manus kept revising the project across five APK outputs, including fixes for Expo Go crashes, EAS CLI build instructions, API key handling changes, a switch from live mapping to a static map, and a later WebView-based attempt. The user handled the testing and repeated build cycle.
How it went
Search eventually became functional, but navigation still caused crashes. One interim version showed only a static map with written directions. The effort used a full monthly 8,100-credit allowance and went on past 2:41 AM without producing a working app.
Tips
For app projects, ask the agent to prove one core function before layering on extras. Set a checkpoint before any paid build, submission, or other irreversible step.

Try it yourself with Manus

I want to create a [platform] app for [route task] using [map service]. Start with the smallest version that can confirm the main flow, and after each milestone, stop and ask me whether to continue. Before you add live maps, voice, lane guidance, or anything that requires a paid build, deployment, or submission, show me what changed and wait for my approval.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on reddit.com โ†—

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.