--- title: "Building Your App" slug: "building-your-app" updated: 2026-07-27T17:03:29Z published: 2026-07-27T17:03:29Z canonical: "docs.developer.comcast.com/building-your-app" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.developer.comcast.com/llms.txt > Use this file to discover all available pages before exploring further. # Building Your App Building your app involves understanding and implementing baseline functionality and features according to platform requirements. Once done, your app must be tested and certified before release. **Before you begin** Review the platform design guidelines in our [Design & Plan](/v2-0/docs/design-overview) section. Keeping these guidelines in mind while developing your app will enable you to have a more streamlined certification and release process once development is complete. > [!NOTE] > **Need to learn about Firebolt**® **before building your app?** > > Check out our [Baseline Firebolt APIs](/docs/baseline-firebolt-api-implementations) and our [Getting Started](/docs/getting-started) guide to learn details about our technology stack and how to build a Hello World app. --- ## Implement baseline functionality To start developing your app, you will need to implement core functionality that enables baseline platform functionality and features. **While developing, you should ensure your app functions as expected on less powerful devices before porting it to higher-end devices.** Refer to the [Device Specs](/v2-0/docs/device-specs) for information on specific devices. > [!WARNING] > **Transitioning from legacy** > > This implementation guidance is designed specifically to help with building Firebolt apps. If you are transitioning your app from our legacy badger APIs, refer to the guidance for [Transitioning from Legacy](/docs/transitioning-from-legacy). ### Lifecycle and navigation **All apps are required to have basic Firebolt Lifecycle support to run properly on our platform.** At a high level, lifecycle functionality on our platform is robust in the fact that your app must support more states than just `closed` or `open`. Instead, your app must support `inactive`, `suspended`, `closed`, `background`, and `foreground` states that enable quick startup and better app performance. 1. [Lifecycle Management](/docs/lifecycle-management) lets you manage the various states of your app on the device. 2. [Listening for Events](/docs/listening-for-events) lets your app to respond to asynchronous notifications from users and the platform. 3. [Listening for Property Changes](/docs/listening-for-property-changes) lets you adjust your app’s functionality in response to hardware and system properties (e.g., audio, accessibility settings). 4. [Deep Linking](/docs/deep-linking) lets users to directly navigate to content in your App from the home screen. **Associated requirements for lifecycle and navigation include:** - [Sign in and authentication requirements](/v2-0/docs/baseline-feature-requirements#signin-and-authentication-requirements-ar) - [Deep linking requirements](/v2-0/docs/baseline-feature-requirements#deep-linking-requirements-dl) - [Dismiss button requirements](/v2-0/docs/baseline-feature-requirements#dismiss-button-requirements-db) - [Quick start requirements](/v2-0/docs/baseline-feature-requirements#quick-start-feature-requirements-qs) ### Media playback [Media playback](https://docs.developer.comcast.com/docs/video-playback) works in tandem with lifecycle and navigation functionality to let users interact with your app’s content. It can be triggered by specific events, intents, and deep links. **Common triggers for media playback include the following intents:** - [PlayEntityIntent](https://docs.developer.comcast.com/docs/150-core-intents-schemas#playentityintent) is the standard for beginning playback of your content. It also offers extra configuration options to targeting specific entities for playback (e.g., playing a specific song in an album). - [PlayQueryIntent](https://docs.developer.comcast.com/docs/150-core-intents-schemas#playqueryintent) leads to media playback from a search or abstract query, where a specific entity is not defined. - [TuneIntent](https://docs.developer.comcast.com/docs/150-core-intents-schemas#tuneintent) is used specifically for “tuning” to linear media, such as a broadcast channel/network or a live streaming event. **Associated requirements for media playback include:** - [Audio/video quality requirements](/v2-0/docs/baseline-functionality-requirements#audio-video-quality-requirements-av) - [Playback requirements](/v2-0/docs/baseline-feature-requirements#playback-requirements-pb) - [Trickplay requirements](/v2-0/docs/baseline-feature-requirements#trickplay-behavior-requirements-tp) ### App metrics **To track the quality of your App’s experience, our platform needs to know metrics for when specific events are initiated.** The Firebolt [Metrics module](https://docs.developer.comcast.com/latest/core-metrics) helps with reporting and analytics regarding your App’s functionality and usage. **For step-by-step instruction on implementing metrics** in your app, check out the [Implementing Firebolt Metrics](/v2-0/docs/implementing-firebolt-metrics) guide. ### App operations and experience Your app must fulfill established operational and experience requirements to ensure a high-quality user experience. **Associated requirements for operations and experience include:** - [Operational requirements](/v2-0/docs/baseline-functionality-requirements#operational-requirements-or) - [Reporting requirements](/v2-0/docs/baseline-functionality-requirements#reporting-requirements-rr) - [Functional requirements](/v2-0/docs/baseline-functionality-requirements#functional-requirements-fr) - [Accessibility requirements](/v2-0/docs/baseline-functionality-requirements#accessibility-requirements-ac) - [Localization requirements](/v2-0/docs/baseline-functionality-requirements#localization-requirements-lc) - [Parental safety requirements](/v2-0/docs/baseline-functionality-requirements#parental-safety-requirements-ps) - [Legal requirements](/v2-0/docs/baseline-functionality-requirements#legal-requirements-lr) --- ## Test and debug Thorough testing can accelerate app release and create a more reliable app experience. Once you’ve implemented baseline functionality for your app, you can **verify your app works as expected on test devices through the following resources:** - [Developer Tools](https://docs.developer.comcast.com/docs/developer-tools) - [Firebolt Implementation Testing Suite](/docs/test-suite-implementations) --- ## Implement additional integrations > [!WARNING] > **Platform integrations must be discussed before adoption** > > The integrations available for your app may depend on your specific distribution terms. **Contact your delivery manager if you are interested in additional integrations.** Once your baseline app is working as expected, you can connect to our [Metadata](https://docs.developer.comcast.com/docs/metadata-overview) systems to enable additional feature integrations if applicable to your app. **Additional integrations include:** - **Continue Watching:** Let users pick up and resume content where they last left off. - **Advertising:** Integrate advertising into your app experience to increase monetization. - **Marketplace:** Let users purchase content directly from their device. - **Whole-Home Sign-In:** Let users login with the same credentials across all devices connected to their account. - **Partner Page:** Show users the best content you have to offer via a fully automated merchandising experience. - **Kids Section:** Offer dedicated areas for kids content. Check out our [Platform Integration Requirements](/docs/platform-integration-requirements) to see what’s needed for each integration. As you add integrations, be sure to test each one to ensure the app behaves as expected according to the requirements. --- ## Certify and release Once you have determined your app is working as expected, you can submit it for certification testing. After your app has passed certification, you can then coordinate with your delivery manager on the final release. ### Certification 1. **Before submitting for certification, ensure your app meets key requirement thresholds.** The [App Performance & Reliability Thresholds](/v2-0/docs/app-performance-reliability-thresholds) contain a list of key requirements and their associated thresholds. 2. **Submit your app for certification via the developer portal certification form.** This form is accessible from the portal’s [app dashboard](https://developer.comcast.com/dashboard). 3. **The app certification team receives your certification request and determines a testing plan.** Considerations that help determine the specific testing plan include: - Specific features and integrations that you have implemented in your app. - Territories and devices to which you plan to distribute your app. 4. **The app certification team tests the app according to the finalized test plan.** Upon testing completion, the team will inform you whether your app has passed or failed certification. - If the app has **passed** certification, you can now coordinate the final release with your assigned delivery manager. - If the app has **failed** certification, you must remove any identified defects and issues before resubmitting your app for another round of certification testing. ### Release Once your app has passed certification, it is ready for release! At a high level, the release process is as follows: 1. You and your delivery manager plan a go-live date. 2. The delivery manager and operations teams prepare the app for release. 3. On the go-live date, you work with your delivery manager and the operations team to release the app to customer devices. **Once your app has been released, our operations team will closely monitor it to ensure it works smoothly in for first few weeks that it is live.** From here, you can coordinate any updates needed for your app as you make improvements throughout its time on our platform.