Skip to main content
Supported Regions:上海

Requirement Description

The requirement description is the first and most critical step in the AI Builder development flow. An accurate and clear requirement description directly affects the quality and correctness of the AI-generated application.

Overview​

During the requirement description phase, you should describe in natural language the application you want AI Builder to create. The AI Builder's intelligent engine will analyze your description, understand the application's functional requirements, UI layout, data structures, etc., and generate corresponding front-end pages, back-end logic, and database schemas.

Tip

In this phase, focus on the application's functional requirements and UI style. After generating the basic layout and structure, add backend services and generate data models.

How to write an effective requirement description​

1. Specify the application type​

First, clarify the type of application you want to build:

  • Web application: desktop web app
  • Mobile H5: mobile web app
  • Admin panel: data management and operations backend
  • Presentation page: product showcases, company introduction and other static pages

Example:

I want to create a mobile task management application

2. Describe core features​

Detail the main functional modules of the application:

Example:

The app should include the following features:
- Users can create, edit, and delete tasks
- Tasks can have priorities (High, Medium, Low)
- Tasks can have due dates
- Users can mark tasks as completed
- Support task categorization
- Provide task statistics and progress displays

3. Describe UI style​

Explain the expected UI style and user experience:

Example:

UI style requirements:
- Clean and modern design
- Primary color in blue tones
- Mobile-friendly interactions, support swipe gestures
- Clear visual hierarchy

Requirement description template​

Basic template​

[Application Type]: [Web/Mobile H5/Mini Program/Admin]

[Application Name]: [Your app name]

[Core Features]:
1. [Feature 1 description]
2. [Feature 2 description]
3. [Feature 3 description]
...

[UI Requirements]:
- [Design style requirements]
- [Color palette requirements]
- [Interaction requirements]

[Special Requirements]:
- [Other special requirements]

Full example​

[Application Type]: Mobile H5

[Application Name]: Smart Task Manager

[Core Features]:
1. Task management: create, edit, delete, complete tasks
2. Category management: support custom categories with different colors
3. Priority setting: support High, Medium, Low
4. Date management: support due dates and highlight overdue tasks
5. Search: search by title and content
6. Statistics: show completion rate and category breakdown
7. User system: support registration, login, and profile management

[UI Requirements]:
- Modern minimalist design
- Primary color using gradient blue (#4A90E2 to #357ABD)
- Support dark mode toggle
- Smooth animations
- Responsive for various mobile screens

[Special Requirements]:
- Support offline use with local storage
- Task reminders (browser notifications)
- Drag-and-drop task reordering
- Cloud sync for data

Best practices​

✅ Recommended​

  1. Be specific: avoid vague descriptions like "build a website"; provide concrete details
  2. Keep structure clear: use bullet points and sections
  3. Use examples: for complex features provide usage scenarios
  4. Consider UX: describe flows from the user's perspective
  5. Iterate: describe core features first, then expand gradually

❌ Avoid​

  1. Too vague: "build a website" lacks details
  2. Too many features at once: split into phases
  3. Overuse of technical jargon: focus on business needs
  4. Conflicting descriptions: keep consistency across sections
  5. No priorities: highlight core features and main flows

FAQ​

Q: I don't know how to describe technical details. What should I do?​

A: You don't need to describe technical details. Focus on features and user experience. AI will choose suitable technical implementations.

Q: Can I modify the requirement description later?​

A: Yes. You can refine and improve the description during the detail-editing phase.

Q: Should I describe all features at once or in phases?​

A: It's recommended to describe core features first and add advanced features later after generating the baseline version.

Q: How to ensure AI understands my requirements?​

A: Use a clear structure and concrete descriptions, and review the generated output to confirm it matches expectations.

Next step​

After completing the requirement description, AI Builder will generate an initial application structure based on your description. Next you can:

🎯 Go to detail editing →

In the detail editing phase you can further refine UI layout, tweak interactions, and optimize user experience.