Good morning everyone, I’ve been building out a no-code solution called CodeFlow, a full-stack TypeScript app using React 18 + Vite on the frontend, Node.js + Express on the backend, PostgreSQL via Neon for data, LLMs for AI generation and the CanvasEight.io API for the Figma code conversion and the semantic structured code generation. The architecture is IR-first and we’re using TanStack Query for state, Drizzle ORM for type-safe DB ops and shadcn/ui + Tailwind for the component system. I’m exploring whether to integrate Flutter as a modular emitter for mobile app generation. The idea is to extend the IR pipeline to support Dart/Flutter output, but I’m wondering if this ends up being a second major implementation or even a separate product. Curious to hear from anyone who’s tackled multi-framework emitters or mobile-first extensions. What are the key architectural or DX pitfalls I should watch out for especially around layout fidelity, previewing and sandboxing Dart in a TypeScript-native stack? My product's functioning prototype: https://code-flow-marcello888.replit.app/
Thank you Marcello
