> ## Documentation Index
> Fetch the complete documentation index at: https://docs.titanos.tv/llms.txt
> Use this file to discover all available pages before exploring further.

# Get your app on Titan OS

## App launch process

If you have an **HTML5** or **HbbTV** app and would like to launch it on Titan OS, please follow the steps below to submit your app for review and prepare it for release.

<Steps>
  <Step title="Compatibility check">
    Ensure your app is fully compatible with [Titan OS
    specifications.](/media-specifications). Confirm that the app adheres to the
    platform's technical and content requirements.
  </Step>

  <Step title="Create a Titan OS Partner Portal Account">
    If you haven’t already, create an account on the **Titan OS Partner Portal**
    here: [Titan OS Partner Portal](https://partners.titanos.tv/).
  </Step>

  <Step title="Submit App for Quality Assurance (QA)">
    In the Partner Portal, navigate to the **'Add new app'** section to submit your app for evaluation. You will need to provide the following:

    * A **test URL** for the Titan OS team to evaluate.
    * Required information for testing, such as credentials, DRM details etc.
    * Necessary assets for publishing, including the app icon and description.

    For more information on asset specifications, see **[Asset Requirements](/app-assets-specifications)**.
  </Step>

  <Step title="Whitelist IPs and Provide Credentials">
    If your app is restricted behind a **paywall** or **geoblocking**, whitelist the IPs provided in the QA Information section of the Partner Portal. Ensure you provide the necessary credentials for the QA team to access your content.
  </Step>

  <Step title="QA Process">
    Once your submission is received, the **Titan OS QA team** will perform an **Intake Test**. This initial test focuses on critical aspects such as:

    * **Playback functionality**
    * **Key handling**

    This stage ensures that your app’s basic functionality works as expected.

    If any issues are identified during the intake test that would block the app from progressing to full QA, an **Intake Report** will be provided. This report will include:

    * Steps to reproduce the issues
    * Suggestions on how to resolve them
    * Supporting visuals (videos or images) to clarify the problem

    Once the basic functionality is approved, the team will move forward with a **full QA** to ensure that the app is stable and meets Titan OS standards for release. If any issues are found during this phase, you will receive a detailed **QA Report** similar to the Intake Report, outlining the steps to reproduce, suggestions for fixing, and visuals to explain the issue.
  </Step>

  <Step title="Resolve Any Issues Identified">
    Address and resolve any issues highlighted in the **QA Report** to ensure your app functions smoothly on Titan OS devices. The **Titan OS QA team** is available to provide support and guidance throughout the process.
  </Step>

  <Step title="Full QA on Production URL">
    If applicable, submit your **production URL** for the final round of quality assurance. The Titan OS team will conduct a final sanity check to ensure your app is fully **release-ready**.
  </Step>

  <Step title="Release and Publishing">
    Once your app has passed the full QA process, it will be ready for publishing on Titan OS. Make sure that all **terms and conditions** with the **Titan OS Business Development** team have been finalized. For any final steps, contact the [business development team](mailto:bd@titanos.tv)
  </Step>
</Steps>

***

## When to submit updates for QA re-certification?

Major updates that significantly affect app functionality, user experience, or compliance with Titan OS guidelines should always be resubmitted for a quick review. This includes changes to key features such as playback, DRM, or navigation behavior. To ensure compatibility and stability, submit the updated version through the Partner Portal for a quick sanity check.

For smaller updates that do not affect core functionalities, you can push these changes directly to the production URL without resubmission. Examples include minor UI tweaks or bug fixes that don’t impact the core logic of the app.

If you're unsure whether your update requires re-certification, it's always best to check with the Titan OS QA team.