---
title: "Choosing the right extension point"
slug: "choosing-the-right-extension-point"
abstract: "Considerations for choosing the right extension points for a Marketplace app."
---
# Choosing the right extension point

As the app developer, you decide which section of your app appears in which extension point. This is useful because most apps offer a variety of functionalities, some of which are more suitable to display in one user interface than in another.

For example, a SitecoreAI translation plugin could include an authentication section and a feature for adding pages to a translation project. You could choose the *full screen* extension point for the authentication section while the page-specific translation feature is best to display in the *Page builder context panel*.

You first choose extension points when you configure your [custom](https://doc.sitecore.com/mp/en/developers/marketplace/configure-and-activate-a-custom-app.html "Configure and activate a custom app") or [public](https://doc.sitecore.com/mp/en/developers/marketplace/configure-a-public-app.html "Configure a public app") app in the Cloud Portal. Although extension points and API access are not dependent on each other, you usually need to choose certain APIs for certain extension points.

You can [update your app's extension points](https://doc.sitecore.com/mp/en/developers/marketplace/finish-configuration.html "Finish configuration") any time as your app requirements change. Certain changes to the extension points of an *installed* [custom](https://doc.sitecore.com/mp/en/developers/marketplace/custom-marketplace-apps.html#configuration-changes-to-installed-apps) or [public](https://doc.sitecore.com/mp/en/developers/marketplace/public-marketplace-apps.html#configuration-changes-to-installed-apps) app require manually updating the app.