// the find
flexn-io/renative
🚀🚀🚀 Unified Development Platform for iOS, tvOS, Android, Android TV, Android Wear, Web, Tizen TV, Tizen Watch, Tizen Mobile, LG webOS, macOS/OSX, Windows, KaiOS, FirefoxOS Firefox TV platforms
ReNative is a CLI-driven build system that wraps React Native, Next.js, and Electron to target 15+ platforms from one codebase. It sits between your code and each platform's native toolchain, managing configs, builds, and deployments via a unified `rnv` command. The target user is a React developer who needs to ship to iOS, Android, TV platforms, and webOS/Tizen without maintaining separate build pipelines.
The platform abstraction is genuinely useful — platform-specific file extensions (`.ios.tsx`, `.web.tsx`, `.lng.ts`) let you share business logic while swapping rendering layers without conditional spaghetti. The monorepo is well-structured with clear package boundaries: core, CLI, adapters, and per-platform SDKs are separate packages rather than one giant blob. E2E workflows exist for every major target (iOS, Android, tvOS, macOS, web) in CI, which is unusual for a project this broad. The JSON schema for `renative.json` is versioned and in-tree, so config validation is at least possible rather than an afterthought.
Supporting 15+ platforms simultaneously means every platform SDK dependency is a liability — Tizen and webOS toolchains are notoriously fragile, and when Samsung or LG breaks their SDK the entire chain stalls. The plugin override system (JSON patches applied to native files) is clever but opaque; when a plugin override conflicts with an upstream native dependency change you're debugging diffed JSON against Gradle or Podfile output with no good error story. At ~2000 stars the community is thin, which matters because the debugging surface is enormous — most issues you hit will have no Stack Overflow answer. Documentation lives on a separate repo and frequently lags the main package versions, so you'll find yourself reading source to understand what the docs claim.