From 7ece1ec5cef7fec57295534150a1d1b661965b2e Mon Sep 17 00:00:00 2001 From: nicoletacoman Date: Mon, 13 Apr 2026 17:26:06 +0200 Subject: [PATCH 1/6] Maia Plan release --- content/en/docs/developerportal/maia-plan.md | 57 +++++++++++-------- .../releasenotes/developer-portal/2026.md | 13 +++++ .../partials/landingpage/latest-releases.html | 2 +- 3 files changed, 48 insertions(+), 24 deletions(-) diff --git a/content/en/docs/developerportal/maia-plan.md b/content/en/docs/developerportal/maia-plan.md index 7d3d6346ec8..eeb93d94f3d 100755 --- a/content/en/docs/developerportal/maia-plan.md +++ b/content/en/docs/developerportal/maia-plan.md @@ -9,17 +9,17 @@ weight: 3 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. -{{< figure src="/attachments/developerportal/maia/maia-create-app.png" alt="Plan and build with Maia" 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. -### Adding Project Details +### Adding Project Context 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: @@ -29,12 +29,14 @@ Go through the steps in the following sections to have Maia Plan create an app f * Add requirements. * Attach documents, sketches, images. -### Generating the Project Scope +4. Click **Generate Plan**. -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. +### Defining the Scope + +1. After clicking **Generate Plan**, the **Define 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. - Once the **Project Scope** window is populated, you can see the following information generated by Maia: + Once 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. You can edit this description. @@ -60,25 +62,32 @@ Go through the steps in the following sections to have Maia Plan create an app f 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. Once you review the project scope and make any changes you deem necessary, click **Approve to Generate**. + You can also click **Save and Exit** to save all the changes you have made so far 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: +1. After clicking **Approve to Generate**, the **Generate Plan** window is displayed, and Maia starts populating it with the proposed plan based on the project scope. + Once the **Generate Plan** window is populated, you can see the following information generated by Maia: -* 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: + * 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: - * See the entire list of stories for an epic in the right side panel. - * Edit the description or details of the epic. + * See the entire 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 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 go back to the **Define Scope** window. Any changes you have made are saved. + * **Save and Exit** – Save all the changes you have made so far and leave the flow. - * 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**. + Once the project plan is fully generated and you have made any necessary changes to it, click **Start Building**. #### Recommended Marketplace Components {#recommender} @@ -98,9 +107,11 @@ If your company does not have company-approved components, Maia returns the foll * 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 clicking **Start Building**, the **Start Development** window is displayed. This provides you with 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 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. +* **Open in Studio Pro** - Click this button to open 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. diff --git a/content/en/docs/releasenotes/developer-portal/2026.md b/content/en/docs/releasenotes/developer-portal/2026.md index 1da3c8006b8..f20e607bd25 100644 --- a/content/en/docs/releasenotes/developer-portal/2026.md +++ b/content/en/docs/releasenotes/developer-portal/2026.md @@ -8,6 +8,19 @@ weight: 1 ## April 2026 +### April 16, 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 generating epics takes too long. + * If large requirements documents do not process correctly. + ### April 2, 2026 #### New Features diff --git a/layouts/partials/landingpage/latest-releases.html b/layouts/partials/landingpage/latest-releases.html index d6485a41f0e..8fcc265e98c 100644 --- a/layouts/partials/landingpage/latest-releases.html +++ b/layouts/partials/landingpage/latest-releases.html @@ -10,7 +10,7 @@

Latest Releases

  • Apps -

    April 2, 2026

    +

    April 16, 2026

  • Deployment From c44659c53c6819019bc96f3d1179b4de8a35a6b4 Mon Sep 17 00:00:00 2001 From: nicoletacoman Date: Tue, 14 Apr 2026 10:40:52 +0200 Subject: [PATCH 2/6] Changed release date --- content/en/docs/releasenotes/developer-portal/2026.md | 2 +- layouts/partials/landingpage/latest-releases.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/releasenotes/developer-portal/2026.md b/content/en/docs/releasenotes/developer-portal/2026.md index f20e607bd25..fa553f7ad71 100644 --- a/content/en/docs/releasenotes/developer-portal/2026.md +++ b/content/en/docs/releasenotes/developer-portal/2026.md @@ -8,7 +8,7 @@ weight: 1 ## April 2026 -### April 16, 2026 +### April 23, 2026 #### Improvements diff --git a/layouts/partials/landingpage/latest-releases.html b/layouts/partials/landingpage/latest-releases.html index 8fcc265e98c..5e4af6a6480 100644 --- a/layouts/partials/landingpage/latest-releases.html +++ b/layouts/partials/landingpage/latest-releases.html @@ -10,7 +10,7 @@

    Latest Releases

  • Apps -

    April 16, 2026

    +

    April 23, 2026

  • Deployment From bd6da0aa32abc03680cc545ffa2a3fbd4072cdec Mon Sep 17 00:00:00 2001 From: nicoletacoman Date: Fri, 17 Apr 2026 09:05:31 +0200 Subject: [PATCH 3/6] Minor changes --- content/en/docs/developerportal/maia-plan.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/content/en/docs/developerportal/maia-plan.md b/content/en/docs/developerportal/maia-plan.md index eeb93d94f3d..7dbdee346fe 100755 --- a/content/en/docs/developerportal/maia-plan.md +++ b/content/en/docs/developerportal/maia-plan.md @@ -9,7 +9,7 @@ weight: 3 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. - +{{< 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 @@ -91,7 +91,9 @@ Go through the steps in the following sections to have Maia Plan create an app f #### 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: @@ -111,7 +113,9 @@ If your company does not have company-approved components, Maia returns the foll After clicking **Start Building**, the **Start Development** window is displayed. This provides you with the following options: -* **Prioritize in Planning Board** – Click this button to open the **Planning** window of the new app, which includes all the project's stories. +* **Prioritize in Planning Board** – Click this button 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. -* **Open in Studio Pro** - Click this button to open 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). +* **Open in Studio Pro** – Click this button to open 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. From c7a35b1ca88fd8c43534bfe8cafffecf7020e9f6 Mon Sep 17 00:00:00 2001 From: nicoletacoman Date: Mon, 20 Apr 2026 15:07:36 +0200 Subject: [PATCH 4/6] Implemented feedback --- content/en/docs/developerportal/maia-plan.md | 12 +++++++++--- .../en/docs/releasenotes/developer-portal/2026.md | 2 +- 2 files changed, 10 insertions(+), 4 deletions(-) diff --git a/content/en/docs/developerportal/maia-plan.md b/content/en/docs/developerportal/maia-plan.md index 7dbdee346fe..27a0ec3558f 100755 --- a/content/en/docs/developerportal/maia-plan.md +++ b/content/en/docs/developerportal/maia-plan.md @@ -17,6 +17,8 @@ Go through the steps in the following sections to have Maia Plan create an app f ### Adding Project Context +Providing context is the foundation on which Maia builds the project plan. This first step gives Maia the direction and the details it needs to get started. + 1. In **Apps**, click **Create App** in the upper right corner. 2. Select **Plan & Build**. The **Plan & Build with Maia** window is displayed. @@ -33,6 +35,8 @@ Go through the steps in the following sections to have Maia Plan create an app f ### Defining the Scope +During this step, you work with Maia on refining and detailing the boundaries of the plan. You can review and edit Maia's proposed project scope, including the goal, the success criteria, the target users, and the requirements. + 1. After clicking **Generate Plan**, the **Define 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. @@ -67,6 +71,8 @@ Go through the steps in the following sections to have Maia Plan create an app f ### Generating the Plan +Maia translates the boundaries you have created during the previous step into a concrete plan, which includes a series of epics and stories. + 1. After clicking **Approve to Generate**, the **Generate Plan** window is displayed, and Maia starts populating it with the proposed plan based on the project scope. Once the **Generate Plan** window is populated, you can see the following information generated by Maia: @@ -95,7 +101,7 @@ Go through the steps in the following sections to have Maia Plan create an app f 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 helps you plan your project more efficiently using Marketplace components that are already approved by your company, and that make your development faster. As such, if Maia identifies Marketplace components that can be used to 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: @@ -113,9 +119,9 @@ If your company does not have company-approved components, Maia returns the foll After clicking **Start Building**, the **Start Development** window is displayed. This provides you with the following options: -* **Prioritize in Planning Board** – Click this button to open the **Planning** window of the new app, which includes all the project's stories. +* **Prioritize in Planning Board** – Click this button to open the **Planning** window of the new app, which includes the contents of the first active sprint. The stories included in the first active sprint are selected by Maia, and you can change them. These are also the stories that make up the scope of the work when you open the project in Studio Pro. - Note that, if you click **Open in Planning** before Maia is done [finding recommendations](#recommender), recommended components are not displayed in the **Planning** window. + Note that, 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. 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. diff --git a/content/en/docs/releasenotes/developer-portal/2026.md b/content/en/docs/releasenotes/developer-portal/2026.md index fa553f7ad71..fda2eed027f 100644 --- a/content/en/docs/releasenotes/developer-portal/2026.md +++ b/content/en/docs/releasenotes/developer-portal/2026.md @@ -18,7 +18,7 @@ weight: 1 * We are now displaying explanatory error messages in the following scenarios: - * If generating epics takes too long. + * If any action takes too long. * If large requirements documents do not process correctly. ### April 2, 2026 From 8bdb99d3bb169488a8e42595f5a9fd08d8007701 Mon Sep 17 00:00:00 2001 From: nicoletacoman Date: Tue, 21 Apr 2026 08:23:40 +0200 Subject: [PATCH 5/6] Added one-line section introduction --- content/en/docs/developerportal/maia-plan.md | 74 ++++++++++---------- 1 file changed, 37 insertions(+), 37 deletions(-) diff --git a/content/en/docs/developerportal/maia-plan.md b/content/en/docs/developerportal/maia-plan.md index 27a0ec3558f..c944371ce25 100755 --- a/content/en/docs/developerportal/maia-plan.md +++ b/content/en/docs/developerportal/maia-plan.md @@ -7,93 +7,93 @@ 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 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 Context -Providing context is the foundation on which Maia builds the project plan. This first step gives Maia the direction and the details it needs to get started. +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**. 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 -During this step, you work with Maia on refining and detailing the boundaries of the plan. You can review and edit Maia's proposed project scope, including the goal, the success criteria, the target users, and the requirements. +Work with Maia to refine and detail the project scope, including the goal, success criteria, target users, and requirements. -1. After clicking **Generate Plan**, the **Define 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 **Define 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 to Generate**. - You can also click **Save and Exit** to save all the changes you have made so far and leave the flow. +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 Plan -Maia translates the boundaries you have created during the previous step into a concrete plan, which includes a series of epics and stories. +Maia translates your defined scope into a concrete plan, which includes a series of epics and stories. -1. After clicking **Approve to Generate**, the **Generate Plan** window is displayed, and Maia starts populating it with the proposed plan based on the project scope. - Once the **Generate Plan** window is populated, you can see the following information generated by Maia: +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: - * Cards corresponding to each epic which contributes to building the app. + * 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 itself to: + Click the card to: - * See the entire list of stories for an epic in the right side panel. + * 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: - * To see the full details of a story or to edit it, click the three-dot menu, then select **Edit**. + * 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**. 2. While the project plan is being generated, you have these options: - * **Previous** – Click this button to go back to the **Define Scope** window. Any changes you have made are saved. - * **Save and Exit** – Save all the changes you have made so far and leave the flow. + * **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. - Once the project plan is fully generated and you have made any necessary changes to it, click **Start Building**. + After the project plan is fully generated and you have made any necessary changes, click **Start Building**. #### Recommended Marketplace Components {#recommender} @@ -101,7 +101,7 @@ Maia translates the boundaries you have created during the previous step into a This feature is in Public Beta. For more information, refer to [Release Status](/releasenotes/release-status/). {{% /alert %}} -Maia helps you plan your project more efficiently using Marketplace components that are already approved by your company, and that make your development faster. As such, if Maia 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: @@ -109,19 +109,19 @@ Maia helps you plan your project more efficiently using Marketplace components t * 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 ### Starting the Development -After clicking **Start Building**, the **Start Development** window is displayed. This provides you with the following options: +After you click **Start Building**, the **Start Development** window is displayed, showing the following options: -* **Prioritize in Planning Board** – Click this button to open the **Planning** window of the new app, which includes the contents of the first active sprint. The stories included in the first active sprint are selected by Maia, and you can change them. These are also the stories that make up the scope of the work when you open the project in Studio Pro. +* **Prioritize in Planning Board** – Click this button to open the **Planning** window of the new app, which includes the contents of the first active sprint. The stories included in the first active sprint are selected by Maia, and you can change them. These stories also make up the scope of the work when you open the project in Studio Pro. - Note that, 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. Note that, at the moment, Studio Pro does not take into account [recommended components](#recommender). + 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. From b61bf737bec7b9ad813cfadc47e468ef2531311a Mon Sep 17 00:00:00 2001 From: nicoletacoman Date: Wed, 22 Apr 2026 11:19:28 +0200 Subject: [PATCH 6/6] Applied feedback --- content/en/docs/developerportal/maia-plan.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/developerportal/maia-plan.md b/content/en/docs/developerportal/maia-plan.md index c944371ce25..f02dd1eb16e 100755 --- a/content/en/docs/developerportal/maia-plan.md +++ b/content/en/docs/developerportal/maia-plan.md @@ -119,7 +119,8 @@ If your company does not have company-approved components, Maia returns the foll After you click **Start Building**, the **Start Development** window is displayed, showing the following options: -* **Prioritize in Planning Board** – Click this button to open the **Planning** window of the new app, which includes the contents of the first active sprint. The stories included in the first active sprint are selected by Maia, and you can change them. These stories also make up the scope of the work when you open the project in Studio Pro. +* **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).