> For the complete documentation index, see [llms.txt](https://www.xrdev.app/mixed-reality-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.xrdev.app/mixed-reality-docs/ai-lessons/fundamental-ai-concepts/project/how-to-create-an-application-with-ai-whiteout-coding/where-to-go-next.md).

# What's next?

Now you have your app's prototype, you can add more features, get feedback and test your app.&#x20;

### Should I keep using my power app or rebuild it?

When your needs change, you can consider refactoring your application to a serverless backend and a custom built UI. If the app is working fine for you and your users, you can continue using and improving overtime using Power Apps.&#x20;

What would be the changes that requires the upgrade? There are two possibilities for the changed requirements for your app:

* Feature
* Budget

### How to create a custom feature for Power Apps?

Ready made tools are always limited to the features the product team decides to include. If you are writing custom code, you can add any feature that you need. Thankfully, for the features that are not implemented yet, it is always possible to author a custom connector that you can use with or without Power Apps.&#x20;

A **connector** is a **proxy** or a **wrapper around an API** that allows the underlying service to talk to Microsoft **Power Automate**, **Microsoft Power Apps,** and **Azure Logic Apps**. It provides a way for users to connect their accounts and leverage a set of pre-built actions and triggers to build their apps and workflows.

Check out the list of [Power Apps Connectors ](https://docs.microsoft.com/connectors/connector-reference/connector-reference-powerapps-connectors?WT.mc_id=aiml-8438-ayyonet)and [how to build a custom connector](https://docs.microsoft.com/connectors/custom-connectors/?WT.mc_id=aiml-8438-ayyonet) yourself.&#x20;

### How to compare costs for Power Apps and Logic Apps?

Once you start using your app, you will have a better idea about the number of users accessing AI capabilities and the number of images that you need to train. You can use [AI Builder Cost Calculator](https://powerapps.microsoft.com/en-us/ai-builder-calculator/?WT.mc_id=aiml-8438-ayyonet) and [Logic App Cost Calculator](https://azure.microsoft.com/pricing/details/logic-apps/?WT.mc_id=aiml-8438-ayyonet) to compare options. You can check any other service price through [Azure Product Cost Calculator](https://azure.microsoft.com/pricing/calculator/?service=logic-apps\&WT.mc_id=aiml-8438-ayyonet).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.xrdev.app/mixed-reality-docs/ai-lessons/fundamental-ai-concepts/project/how-to-create-an-application-with-ai-whiteout-coding/where-to-go-next.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
