Rebranding works best when decisions are organized. The process below helps prevent incorrect logos, unclear portal labels, missed device requirements and last-minute changes.
The five project stages
Choose a supported player
Compare device compatibility, login methods, interface style and available customization options.
Send approved assets
Provide the final app name, logos, colors, artwork and authorized portal configuration.
Confirm the scope
We confirm what will change, what will be delivered, the price and expected timeline.
Customization and review
The supported app elements are customized and prepared for your review.
Test and receive
The final details are checked and the completed build is delivered through the agreed channel.
What you need to provide
- Final app name with exact spelling and capitalization.
- A high-resolution transparent logo, preferably with a vector source.
- Primary and accent colors with exact HEX values.
- Approved backgrounds or a clear visual direction.
- The selected app and target device types.
- Authorized portal or Multi DNS details, if supported.
- Any supported contact, support or advertising details included in the scope.
Our branding checklist explains how to prepare each item.
Review and revisions
Review the build against the confirmed scope. Check spelling, logos, colors, backgrounds, portal labels and the main user journey. Send one consolidated list of corrections from the designated approver.
A revision corrects or refines an item already included in the agreed scope. A new player, new theme, major layout request or additional configuration may require a separate quote.
Testing responsibilities
We check the customization and agreed configuration. Clients should also test the delivered build on representative devices and with their own authorized service environment before broad distribution.
- Verify installation and launcher identity.
- Test supported login and portal selection.
- Check TV remote and mobile touch navigation.
- Review text readability and image cropping.
- Confirm support details and approved links.
Delivery and future updates
The delivery format is confirmed before work starts. Keep the delivered build, approved brand assets, app version and configuration together. Future player updates, portal changes or new visual designs may require a new customization order.