Platform-specific app behavior, branding, layout, and feature visibility for connected TV and mobile clients.

App Config

Location: MediaBlaster → App Config → App Settings tab

Configure how connected apps (starting with the MediaBlaster Roku app) behave, look, and navigate. Settings are stored in WordPress and served publicly to clients via the REST config endpoint.

This is not API discovery — the app must already know your WordPress site URL to request config. Do not store apiBaseUrl, apiOrigin, secrets, or private credentials here.

Platform tabs

Tab	Status
App Settings (`platform=roku`)	Available
Mobile, Google TV, Fire TV, Apple TV	Planned — same page will gain additional tabs

Sections (App Settings tab)

Section	Purpose
General	App name, debug mode
Content Availability	VOD, movies, series, categories, search, continue watching
Branding	Colors, fallback images, card/poster aspect ratios
Links	Support and privacy URLs
Sidebar	Sidebar visibility and widths
Navigation Features	Which destinations appear in app navigation (`features` object)
Labels	Custom UI labels (`labels` object)
Homepage Layout	Home screen layout toggles (`layout` object)
Home Tag Rows	Tag-based home row settings (`homeTagRows` object)
Boot	Startup behavior (`boot` object)
REST Endpoint	Read-only display of the public config URL

Each field includes inline help text under its label. Section titles include a short description.

REST endpoint

GET /wp-json/mediablaster/v3/config?platform=roku

Public, read-only (no authentication required)
Default platform query value: roku
Unsupported platform → 400 mediablaster_invalid_platform

See REST API — App Config for the response shape.

Not the same as GET /app/config — that route returns subscription/Stripe client configuration when the subscriptions module and REST API are enabled. See Subscriptions and Apps API.

Defaults and saving

If nothing has been saved, the endpoint returns built-in Roku defaults immediately.
homeRows is always [] in v1 (no admin UI yet).