Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
104 changes: 63 additions & 41 deletions content/en/docs/developerportal/maia-plan.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,100 +7,122 @@ weight: 3

## Introduction

You can use Maia Plan to plan and generate an app. This page describes how to provide project context, review and refine the generated project scope, and approve the solution proposal to initiate app development.
Maia Plan helps you plan and generate an app. This page describes how to provide project context, review and refine the generated project scope, and approve the solution proposal to start app development.

{{< figure src="/attachments/developerportal/maia/maia-create-app.png" alt="Plan and build with Maia" max-width=50% >}}
{{< figure src="/attachments/developerportal/maia/maia-create-app.png" alt="Plan and build with Maia entry point" max-width=50% >}}

## Creating an App with Maia Plan

Go through the steps in the following sections to have Maia Plan create an app for you.
Follow the steps in the following sections to create an app with Maia Plan.

### Adding Project Details
### Adding Project Context

Providing context is the foundation for Maia to build your project plan. Give Maia clear goals, user details, and requirements to generate an accurate app plan.

1. In **Apps**, click **Create App** in the upper right corner.

2. Select **Plan & Build with Maia**.
2. Select **Plan & Build**. The **Plan & Build with Maia** window is displayed.

3. In the **Project Context** text box, enter as much detail as possible about your future app. Include the following information to help Maia generate an accurate app plan:
3. In the **Project Context** text box, enter as much detail as possible about your app. Include the following information to help Maia generate an accurate app plan:

* Describe your goals.
* Describe your targeted users.
* List out success criteria.
* Describe your target users.
* List success criteria.
* Add requirements.
* Attach documents, sketches, images.
* Attach documents, sketches, and images.

4. Click **Generate Plan**.

### Defining the Scope

### Generating the Project Scope
Work with Maia to refine and detail the project scope, including the goal, success criteria, target users, and requirements.

1. Once you have added all the preliminary details, click **Generate Plan**. The **Project Scope** window is displayed, and Maia starts populating it with the proposed project scope.
The app plan becomes available on the **Apps** page as soon as you click **Generate Plan** at the beginning of the workflow. As such, you can go back to the plan at any time after you leave it, and you can already add team members to the app.
1. After you click **Generate Plan**, the **Define Scope** window appears, and Maia starts populating it with the proposed project scope.
The app plan becomes available on the **Apps** page as soon as you click **Generate Plan** at the beginning of the workflow. You can return to the plan at any time after you leave it, and you can add team members to the app.

Once the **Project Scope** window is populated, you can see the following information generated by Maia:
After the **Define Scope** window is populated, you can see the following information generated by Maia:

* **Goal** – A description of what you want to achieve through the app.
* **Goal** – A description of what you want to achieve with the app.
You can edit this description.

* **Success Criteria** – A list of criteria by which to measure the success of the app. You can perform the following actions:
* **Success Criteria** – A list of criteria to measure the success of the app. You can perform the following actions:

* In-line edit criteria.
* Edit criteria inline.
* Remove criteria by hovering over them, then clicking the trash can icon.
* Add new criteria by clicking **+Add New Success Criteria**.

* **Target Users** – Cards corresponding to the app's target users, along with each user's goal. You can perform the following actions:
* **Target Users** – Cards for the app's target users and each user's goal. You can perform the following actions:

* In-line edit user details.
* Edit user details inline.
* Remove users or their goals by hovering over them, then clicking the trash can icon.
* Add users by clicking **+Add New User**.
* Add user goals by clicking **+Add New User Goal**.

* **Requirements** – The features that the app must have. You can perform the following actions:

* In-line edit requirements.
* Edit requirements inline.
* Remove features by hovering over them, then clicking the trash can icon.
* Add new features by clicking **+Add New Requirement**.

You can use the pane on the right to chat with Maia about your requirements for the new app.

2. Once you review the project scope and make any changes you deem necessary, click **Approve Project Scope** in the top right of the page. The status of the project scope changes from **Draft** to **Approved**.
2. After you review the project scope and make any necessary changes, click **Approve to Generate**.
You can also click **Save and Exit** to save all the changes and leave the flow.

### Generating the Solution Proposal
### Generating the Plan

If you agree with the project scope, click **Generate Solution** in the top right of the page. The **Solution Proposal** window is displayed, and Maia starts populating it with the proposed project scope.
While the solution proposal is being generated, as well as after it's displayed, the **Project Scope** is locked. If you want to make changes to it, you can click the lock icon to unlock it.
Once the **Solution Proposal** window is populated, you can see the following information generated by Maia:
Maia translates your defined scope into a concrete plan, which includes a series of epics and stories.

* Cards corresponding to each epic which contributes to building the app.
You can remove epics by hovering over them, then clicking the trash can icon.
Click the card itself to:
1. After you click **Approve to Generate**, the **Generate Plan** window appears, and Maia starts populating it with the proposed plan based on the project scope.
After the **Generate Plan** window is populated, you can see the following information generated by Maia:

* See the entire list of stories for an epic in the right side panel.
* Edit the description or details of the epic.
* Cards for each epic that contributes to building the app.
You can remove epics by hovering over them, then clicking the trash can icon.
Click the card to:

* See the list of stories for an epic in the right side panel.
* Edit the description or details of the epic.

You can perform the following actions on each story:
You can perform the following actions on each story:

* To see the full details of a story or edit it, click the three-dot menu, then select **Edit**.
* To remove a story, click the three-dot menu, then select **Delete**.

* To see the full details of a story or to edit it, click the three-dot menu, then select **Edit**.
* To remove a story, click the three-dot menu, then select **Delete**.
2. While the project plan is being generated, you have these options:

* **Previous** – Click this button to return to the **Define Scope** window. Any changes you have made are saved.
* **Save and Exit** – Save all the changes and leave the flow.

After the project plan is fully generated and you have made any necessary changes, click **Start Building**.

#### Recommended Marketplace Components {#recommender}

{{% alert color="warning" %}} This feature is in Public Beta. For more information, refer to Release Status. {{% /alert %}}
{{% alert color="warning" %}}
This feature is in Public Beta. For more information, refer to [Release Status](/releasenotes/release-status/).
{{% /alert %}}

If Mendix identifies Marketplace components that can be used to implement a specific story, they are displayed in the following places:
Maia identifies approved Marketplace components that can accelerate your development. If Maia finds components that can help you implement a specific story, they are displayed in the following places:

* At the epic level, as a number. Example: *1 Resource*.
* At the user story level, in the side panel. From here, you can perform the following actions:

* If you want more details about the component, click it to access its page in the Marketplace.
* If you do not want a component to be used, delete it by clicking the trash can icon.

If your company has company-approved components, Maia only returns company-approved components from the Public and the Private Marketplace.
If your company has company-approved components, Maia only returns company-approved components from the Public and Private Marketplace.
If your company does not have company-approved components, Maia returns the following types of components:

* platform-supported components
* all Private Marketplace components
* Platform-supported components
* All Private Marketplace components

### Opening the App
### Starting the Development

Once you are happy with Maia's suggested project plan, click **Open in Studio Pro** in the top right of the page. This opens Studio Pro, where you can continue working on the new app. Note that, at the moment, Studio Pro does not take into account [recommended components](#recommender).
For details, refer to [Maia Make](/refguide/maia-make/) in the Studio Pro documentation.
After you click **Start Building**, the **Start Development** window is displayed, showing the following options:

You can also click **Open in Planning** to open the **Planning** window of the new app, which includes all the project's stories. Note that, if you click **Open in Planning** before Maia is done [finding recommendations](#recommender), recommended components are not displayed in the **Planning** window.
* **Prioritize in Planning Board** – Click this button to open the **Planning** window of the new app, which includes all stories organized in sprints. You can reorganize the sprints as needed.
Only the stories in the active sprint are taken into Studio Pro.

If you click **Prioritize in Planning Board** before Maia is done [finding recommendations](#recommender), recommended components are not displayed in the **Planning** window.
* **Open in Studio Pro** – Click this button to open Studio Pro, where you can continue working on the new app. Studio Pro does not currently take into account [recommended components](#recommender).

For details, refer to [Maia Make](/refguide/maia-make/) in the Studio Pro documentation.
13 changes: 13 additions & 0 deletions content/en/docs/releasenotes/developer-portal/2026.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,19 @@ weight: 1

## April 2026

### April 23, 2026

#### Improvements

* In an effort to provide a seamless app creation experience, we have updated the [Maia Plan](/developerportal/maia-plan/) project creation flow. Everything works the same, but the step layout and progression are now aligned to the general Mendix Portal experience that you might already be used to.

#### Fixes

* We are now displaying explanatory error messages in the following scenarios:

* If any action takes too long.
* If large requirements documents do not process correctly.

### April 2, 2026

#### New Features
Expand Down
2 changes: 1 addition & 1 deletion layouts/partials/landingpage/latest-releases.html
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ <h4 class="lp-panel-title">Latest Releases</h4>
</li>
<li class="lp-panel-list">
<a href="/releasenotes/developer-portal/">Apps</a>
<p class="rn-date">April 2, 2026</p>
<p class="rn-date">April 23, 2026</p>
</li>
<li class="lp-panel-list">
<a href="/releasenotes/developer-portal/deployment/">Deployment</a>
Expand Down