Organize firmware, cloud, and app workstreams around one delivery plan.

Development

Development outlines how engineering teams move from proof-of-concept into execution. It explains the expected workstreams, the handoffs between firmware and cloud teams, and the checkpoints needed before release and deployment readiness reviews.

Coverage

What this section explains

  • Suggested phase plan from prototype to production
  • Shared responsibilities across firmware, mobile, cloud, and QA
  • Integration checkpoints for provisioning, OTA, and operations

Expected outputs

What teams should be able to leave with

  • Environment bootstrap checklists
  • Cross-team implementation milestones
  • Validation gates before field pilots

Primary audience

Who should start here

  • Engineering managers planning delivery
  • Firmware and app leads coordinating dependencies
  • QA teams defining release readiness

Related docs

Continue with adjacent developer topics.

Product Overview

Platform architecture, capability map, and commercial packaging guidance for Realtek Connect+ evaluations.

View section

APIs

REST, MQTT over TLS, webhook, and service contract documentation entry points for external systems.

View section

SDKs

Mobile SDK, firmware SDK, reusable client components, and reference samples for branded product delivery.

View section

Firmware

Provisioning, identity, telemetry, OTA agent, and diagnostics expectations for device firmware teams.

View section

CLI

Command-line entry points for local testing, release preparation, fleet actions, and support diagnostics.

View section

Deployment

Production deployment profile, persistent SQLite storage, reverse proxy TLS, health checks, backup/restore, and rollback notes.

View section

Release Notes

Versioned change logs, upgrade notes, compatibility statements, and rollout communication patterns.

View section