« HELP CENTER

Component Development Guide > Certification

Certification Review Process

Once you submit your component for certification, it enters Flite Hub’s certification queue.

Typically, you can expect your component to complete the certification process in less than one month. However, this can vary greatly depending on how many problems we find with the component, and the length of the current certification queue.

The certification process involves three steps: UX Review, QA Review, and Documentation Review.

UX Review

Flite’s User Experience (UX) team will review your component to make sure its design – including usability, layout, appearance, workflow, and parameters – is consistent with Flite standards and best practices. If you have not yet created a demo ad, we will work with you to do so in this step. The following items are tested in this step:

  • Default component design & usability: We make sure the default component looks good, is easy to use, and functions as expected.
  • Demo ad design & usability: We make sure the demo ad looks good and showcases the component well.
  • Parameter set: We review the set of parameters offered by your component, and determine if it is the right set of parameters for your component. This part of the review will often result in recommendations to add or remove certain parameters. UX can block certification pending this addition/removal.
  • Parameter design: We make sure all parameters are well-designed, logically grouped, and easy to understand. We may recommend parameter design changes, or simply make those changes ourselves.

QA review

Flite’s Quality Assurance team will test your components to make sure they are bug-free, and function as intended. This includes making sure that the component’s event tracking is consistent with Flite Metrics requirements. Note that this step cannot begin until UX review is complete.

  • Component functionality: We make sure the component works as intended.
  • Parameter functionality: We make sure all configuration parameters work as intended.
  • Event tracking: We check that events are tracked as outlined in the events spreadsheet you provide. We also check that all events dictated by Flite's events requirements are being tracked.

Documentation review

Flite’s Product team will go through your component documentation, and make sure it is adequate. We will also work with you to produce a one-page component summary sheet for marketing use.