feat: implement visual UI builder, multi-device Android app, Ktor routing sync, and product roadmaps

related-product/ecosystem_platform_assessment.md

@@ -0,0 +1,40 @@
+# Platform Assessment: iOS, Smart TVs, and Smart Home Systems
+
+This document analyzes the viability of using Kotlin Multiplatform (KMP) and Compose Multiplatform (CMP) to target iOS, Smart TVs, and Smart Home systems (IoT) for stateless lite-client rendering.
+
+---
+
+## 1. Platform Viability Matrix
+
+| Platform Group | Operating System | Primary Language | Kotlin / CMP Support | Notes |
+| :--- | :--- | :--- | :--- | :--- |
+| **Phones / Wearables** | iOS / watchOS | Swift / Objective-C | **Excellent** | Compiles to native iOS frameworks using Skia rendering. |
+| **Smart TVs** | Android TV / Fire TV | Kotlin / Java | **Excellent** (Native) | Standard Android build targets work out of the box. |
+| **Smart TVs** | Samsung Tizen / LG webOS | HTML5 / JS | **Medium** (via Web/Wasm) | Web-based OS. Standard JS/HTML is lighter here. |
+| **Apple TV** | tvOS | Swift / Objective-C | **Experimental** | Supported by Kotlin/Native compiler. |
+| **Smart Home Hubs** | Home Assistant | Python | **Custom integration** | Extensible via Python scripts or custom Web UI cards. |
+| **Microcontrollers** | ESP32 / Arduino / IoT | C / C++ | **No Support** | Require low-level C/C++ or MicroPython. |
+
+---
+
+## 2. Platform Breakdown
+
+### 1. iOS and Apple Watch (watchOS)
+* **How Kotlin works on iOS**: Kotlin Multiplatform compiles your shared Kotlin code into a native Objective-C/Swift framework, and Compose Multiplatform renders directly via **Skia/Canvas** (high-performance graphics engine). This means you get a native-looking, high-performance UI on iOS without duplicating code.
+* **Apple Watch (watchOS)**: Kotlin/Native natively supports watchOS compilation targets, making it easy to share the database, networking, and state logic with an Apple Watch app.
+
+### 2. Smart TVs (Android TV vs. WebOS/Tizen)
+* **Android TV (Sony, Fire TV, Nvidia Shield)**: Android TV is 100% Android. Since Kotlin is the official language of Android, your KMP lite-client APK can run natively on Android TVs with no extra porting required.
+* **Web-Based TVs (Samsung Tizen, LG webOS)**: These TVs do **not** run Java/Kotlin. They are lightweight web browsers that run **HTML5/JavaScript** applications. To render on these TVs, you either compile your Kotlin app to WebAssembly (Kotlin/Wasm) or write a small HTML/JS shell that communicates with the Ktor server.
+
+### 3. Smart Home Systems & JVM Hubs
+* **JVM-Based Hubs (openHAB, legacy SmartThings)**:
+  * You are absolutely correct: many major home automation hubs run on the **JVM**.
+  * **openHAB** (the leading Java-based open-source smart home automation platform) runs entirely on a Java OSGi framework.
+  * **SmartThings** (Samsung) originally built its entire local device handler and smart-app ecosystem on **Groovy** (a JVM language).
+  * Because of this, a local **Ktor (Kotlin/JVM) server** is an ideal candidate to act as a custom smart-home hub. It can run continuously on a Raspberry Pi or home server, interface directly with existing Java libraries, and orchestrate signals.
+* **Google Home / Nest Hubs**: Many smart displays run on Android (Java/Kotlin native) or Android-based wrappers, making them native deployment targets for our client shells.
+* **Connected Devices (ESP32 / Zigbee / Thread)**:
+  * The actual endpoints (switches, bulbs, sensors) run C/C++ or lightweight micro-firmware.
+  * These devices do not run business logic; they simply broadcast signals (MQTT, Zigbee, or Matter) to the **local JVM hub (our Ktor server)**.
+  * The Ktor server processes these signals, matches them to rules, and uses our Server-Driven UI schema to push a control interface to your smartwatch or phone on demand.