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

related-product/gemini_deep_research_prompt.md

@@ -0,0 +1,40 @@
+# Gemini Deep Research Prompt: Lite-Client Platform & Marketplace
+
+Copy and paste the prompt below into Gemini Deep Research (or your preferred research AI) to generate a complete market viability and cost-assessment report.
+
+---
+
+```text
+Please perform a deep, comprehensive research and market viability assessment for a new developer platform and marketplace.
+
+### 1. Product Context
+The product is a generic Server-Driven UI (SDUI) "Lite-Client" platform and marketplace. It consists of:
+- **Stateless Lite-Client Shells**: Lightweight, unified client applications running on Wear OS (smartwatch), watchOS, iOS, Android, and Desktop. These shells contain no business logic; they simply connect to a local/cloud host, fetch a visual JSON layout configuration, and dynamically inflate native UI elements.
+- **Visual Lite-Client Builder**: A drag-and-drop editor allowing creators to design visual dashboards, remote controllers, and notification systems, which are serialized directly into the platform's JSON schemas.
+- **MCP Integration**: Native support for Model Context Protocol (MCP) schemas, allowing the visual builder to automatically translate local tools/endpoints into native UI layouts.
+- **[The Marketplace]**: A public registry where developers publish, share, or monetize their custom UI layouts and configurations (lite-clients) for various scripts, IoT tools, local servers, and dashboards.
+- **First Reference App ("Meatbag")**: The first application built on the platform—a satirical, edgy confirmation-routing tool specifically designed for AI agents requesting human approval via smartwatch haptics.
+
+### 2. Core Research Objectives
+
+Please research and analyze the following areas:
+
+#### Objective A: The Cost of Building Custom Clients
+- Evaluate the standard development, maintenance, and deployment costs (in engineering hours, developer salaries, and App Store lifecycle overhead) for an organization or developer to build dedicated, platform-specific custom client apps (such as a custom Apple Watch dashboard, a dedicated remote-control phone app, or a desktop notification utility) for their internal systems.
+- Compare this against the cost and time savings of using a single, pre-installed "stateless rendering shell" that consumes a server-driven JSON config generated via drag-and-drop.
+
+#### Objective B: Market Viability of a Lite-Client Platform & Marketplace
+- Analyze the current developer tooling and DevOps landscape. Is there a demand for a lightweight, generic, drag-and-drop interface builder for local scripts, APIs, and CLI tools?
+- Evaluate the adoption of MCP (Model Context Protocol). How well does an MCP-native drag-and-drop builder integrate with the current wave of developer interest in AI and local tool execution?
+- Assess the market size and potential transaction volume of a marketplace dedicated to sharing and licensing these stateless layout profiles.
+
+#### Objective C: Customer Profiles & Go-To-Market (GTM)
+- Identify the core customer segments (e.g., IoT hobbyists, DevOps teams, sysadmins, AI application developers) most likely to adopt a generic lite-client platform.
+- Recommend the best monetization models for the marketplace (e.g. flat transactional fees, developer subscription tiers, hosting/syncing fees).
+
+### 3. Deliverables Required in the Output
+1. **Executive Summary**: Market viability rating of a generic, MCP-native lite-client platform and marketplace.
+2. **Quantitative Cost Analysis**: A comparison matrix of traditional native client development vs. the Server-Driven UI shell.
+3. **Market Segment Analysis**: Target audience profiles, use cases, and estimated Willingness to Pay (WTP).
+4. **GTM & Monetization Strategy**: Recommended business model and launch plan.
+```