SDK Sample Applications

Realtek Connect+ customer evaluations should start with runnable reference samples before product teams commit to a branded app, production firmware, or a private deployment plan. The detailed source of truth stays in the rtk_cloud_client repository, especially docs/SAMPLE_APPLICATIONS.md and the sample-specific README files.

Sample families

Customer evaluation path

1. Run the Linux simulator first to validate light, AC, and camera command handling without physical hardware.
2. Use the WebApp Ops Lab sample to exercise cloud-side onboarding, device registry exploration, MQTT payload inspection, simulated controls, camera helper flows, and debug report generation.
3. Run the Android and iOS Home Automation samples to verify native mobile flows, setup profiles, device control, camera monitor boundaries, and redacted debug evidence.
4. Connect the PRO2 camera device demo when hardware is available to validate device-bound token flow, owner transport, snapshot upload, camera status/log/event reporting, and WebRTC Video over TURN answerer behavior.

Boundaries

• These samples are SDK usage references, not production app-store apps, white-label release packages, or customer release artifacts.
• The WebApp sample demonstrates browser-side cloud flows and does not implement BLE or SoftAP onboarding.
• The sample command schema for light and AC controls is a sample-local reference, not a formal cloud wire contract.
• Video streaming copy is WebRTC Video over TURN only; TURN and coturn are described only as WebRTC ICE infrastructure, not as standalone relay products.
• Product teams still own production UX, app signing, app-store publishing, household sharing, push delivery, scenes, schedules, automation, and market-specific release policy.

Source documents

Next step

Use the samples to decide which app and device path matches your product evaluation, then contact the Realtek Connect+ team to discuss SDK scope, device class, and deployment assumptions.