Apps Technical Control
Platform/app authority. Core Publish handles content only; this page handles packages, platform profiles, OTT Core, certification and QA.
VIDAA / Hisense
Smart TV
Store/certification priority.
Current packages are technical contracts, not final signed store binaries.
Must behave as platform-native, not generic web view.
Shared service/product contract consumed by all 17 apps.
Single account, profiles, device sessions and profile restrictions.
Plans, subscription state, rental/purchase rights and playback authorization.
Home rails, title metadata, collections and artwork hierarchy.
Search suggestions, filters, title links and campaign links.
ABR playback, DRM-ready architecture, subtitles, resume and telemetry.
Continue watching, resume points, history, My List and recommendations.
Captions, readable type, audio language, RTL and localized metadata.
Browse, search, playback, buffering, crashes and telemetry.
Color, typography, artwork ratios, spacing and motion language.
All right-sidebar complexity collapsed into actionable requirement tiles.
App UI must match platform density and screen model.
No unreachable controls. TV apps must be D-pad/remote safe.
Focus/back behavior must be verified before store submission.
Playback is the hard gate before UI polish.
Treat every platform as a certification program.
Shared OTT Core stays common; platform shell changes per device.
Existing downloads preserved. No duplicate Core Publish Technical page.
Minimum actionable controls only. Explanations stay in backend/API contracts.
Trendest-owned organization account required.
Package/bundle/channel ID, app name, icon and store profile.
Privacy policy, terms, account deletion and store disclosures.
Screenshots, icons, descriptions, rating declarations and support URLs.
Review account, content access and region notes required.
No platform moves to ready until playback, login, privacy, assets and QA are green.
Same evidence-board style as QC: requirement tile, owner, evidence, status.