Build a full app with Manus

Tools

Manus

Overview

A user built a whole app on Manus with a smooth start, but ran out of credits and got stuck in a billing support loop between Apple and Manus.

Workflow

Suggested implementation: A user attempts to build a full application using Manus. The workflow involves initial development, credit consumption, and subsequent upgrade attempts. The specific technical steps are not detailed in the source, but the process includes interacting with Manus support and Apple/iTunes billing systems when credits run out.

Reported result

The user reported that the product showed promise initially, but encountered a billing block after running out of credits. This issue prevented them from continuing with Manus, leading them to switch to Claude to complete the project. No specific build metrics or success rates were provided.

Human role

Source evidence is unavailable regarding specific human roles or division of labor in the development process.

Limitations

Prerequisites include a Manus subscription and sufficient credits. A significant constraint is the billing integration: if subscribed via Apple, upgrades and billing changes may require processing through Apple, potentially causing delays or support loops. Source reliability is low as the original URL returned a 403 error, and details are based on secondary summaries.

Try it

I want to test the Manus app-building workflow with a low-risk pilot. Please guide me through building a simple, non-critical feature. Inputs: - App Specification: [Insert simple feature description, e.g., a to-do list with local storage] - Target Platform: [e.g., Web/Mobile] - Output Location: [e.g., Local directory or GitHub repo] Steps: 1. Initialize a new project in Manus. 2. Implement the specified feature. 3. Monitor credit usage during the build. 4. If credits run out, attempt to upgrade via the standard interface. 5. Document any billing or support interactions. Deliverables: - Working code for the feature. - A log of credit consumption and any support tickets raised. Quality Check: - Verify code functionality manually. - Confirm billing channel (Apple vs. Direct) before scaling. Safeguards: - Do not spend more than [Insert Budget] credits. - Stop and ask for human confirmation if a billing error occurs. - If the source URL is inaccessible, rely on current Manus documentation for setup steps. Clarification: If the specific app spec is missing, please ask for it before proceeding.

More cases · Software & development

• Update a code base with Copilot chat and agent mode
• Check code against user intent with review agents and tests
• Build a budgeting app from a single prompt
• Build a mental models framework with a multi-agent dev team
• Build a instant-opening markdown viewer for macOS