Topolo Device Platform

What It Is

Topolo Device Platform is a family of Topolo-owned surfaces for feed delivery, feed media assets, feed analytics, Android playback, TopoloMDM-owned Android provisioning, and device-side consumption of Developers-owned app catalog metadata.

Architecture

The product family spans several first-class PlatformApplications roots rather than one unified application. TopoloFeed owns feed delivery, feed media assets, feed operator UI, Android playback, and feed analytics under PlatformApplications/TopoloFeed. TopoloMDM owns device management and Android provisioning. Topolo Developers owns the Android and iOS app-catalog metadata that device install flows consume. The retained Nodo-origin mobile surfaces now appear as Topolo-owned mobile apps in the Developers workspace: Topolo Feed, Topolo Provision, and Topolo MDM Mobile.

Runtime Surfaces

Use /systems/topolo-device-platform for the current inventory of workers, UIs, and Android surfaces.

API Reference

The active contracts are curated in the docs platform and include TopoloFeed’s https://topolo-feed-api.topolo.app feed worker, https://topolo-feed-assets.topolo.app media asset host, https://topolo-feed-analytics-api.topolo.app telemetry worker, Developers-owned /api/apps mobile artifact listings, and the Android consumers that depend on them.

Auth and Permissions

Auth expectations vary by surface. Some workers are lightweight delivery or analytics endpoints, while admin and provisioning flows should align with broader platform standards.

Data Ownership

Device-platform surfaces own feed configuration, feed analytics, playback state, and provisioning-related artifacts depending on the subcomponent. Feed-specific delivery belongs inside TopoloFeed; mobile app listing and distribution metadata belongs inside Topolo Developers.

Deployments

Treat Topolo Device Platform as a retained product family with several separately deployable surfaces rather than a single product runtime. The callable platform service registry exposes feed delivery as feed; feed analytics remains a device telemetry surface, and feed media assets are served from TopoloFeed’s topolo-feed-assets R2 bucket.

Failure Modes

• the product family is documented as if it were one coherent app
• provisioning, feed delivery, and analytics responsibilities are conflated
• lifecycle maturity is overstated for the provisioning branch
• mobile app catalog ownership is reintroduced as a separate device-platform API instead of staying in Developers

Debugging

Start with /systems/topolo-device-platform, then identify the exact sub-surface before debugging or documenting behavior.

Change Log / Verification

• Moved TopoloFeed media delivery onto the Topolo-named topolo-feed-assets R2 bucket on 2026-04-23.
• Added the TopoloFeed asset host and clarified TopoloFeed/TopoloMDM ownership boundaries on 2026-04-23.
• Re-established the TopoloFeed production hosts and callable feed service registry entry on 2026-04-23.
• Registered retained mobile surfaces as first-party Topolo app records in Developers on 2026-04-23.
• Moved mobile app catalog ownership from the standalone AppLibrary API into Topolo Developers on 2026-04-22.
• Folded the feed API and operator UI into PlatformApplications/TopoloFeed on 2026-04-22
• Promoted the retained app-library, feed API, and feed runtime repos to first-class PlatformApplications/* roots on 2026-04-22
• Renamed the feed runtime container to TopoloFeed on 2026-04-22
• Added canonical device-platform coverage and retired repo-local cluster docs on 2026-03-30