> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/channels/push/apps.md). # Apps Register and manage your mobile apps in UbiQuity before sending push notifications. In UbiQuity, an app corresponds to a mobile app you have developed that is installed on your users' devices. Before you can send push notifications, your app needs to be registered in UbiQuity. You can register multiple apps against a single UbiQuity account. Each notification you send is associated with a specific app, and only devices registered for that app will be available to target when you set up your filter. *** ### Registering an app Registering an app in UbiQuity requires setup by the UbiQuity team. Contact UbiQuity to get your app registered. Once your app is registered, you will be able to: * Send notifications to users who have the app installed * View registered devices for that app * Link app users to database contacts for segmentation and personalisation *** ### Managing apps Once an app is registered, it will appear in your UbiQuity account and can be selected when creating a notification. > **Note:** If you delete an app, all notifications associated with that app will also be deleted. For information on how to integrate your app with UbiQuity from a development perspective, see Connecting Your App. --- # 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://docs.ubiquity.co.nz/documentation/channels/push/apps.md?ask=&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.