App Frameworks

Flutter178.5k★

Flutter builds natively compiled apps for mobile, web, and desktop from one Dart codebase. It ships its own rendering engine instead of native UI components, so the app looks the same on every platform. BSD 3-Clause, free, no paid tier, no premium SDK features. Google funds it as a platform bet rather than a product, which is why there is nothing to buy and why people keep asking how long it lasts. It runs well past phones now: NotebookLM, Zoho, LG webOS, and the 2026 Toyota RAV4 infotainment system. Version 3.44 froze Material and Cupertino in the framework and began moving them into standalone material_ui and cupertino_ui packages, the biggest structural change in years. Agentic Hot Reload lets coding agents attach to a running app and trigger reloads. Solo and small teams: one codebase instead of two is the whole argument. Medium: strongest when nobody writes Swift or Kotlin. Large: check whether platform-specific feel justifies two native codebases. The catch: Dart. Almost nobody learns it for anything else, so the hiring pool is thinner than React Native's. facebook/react-native and expo/expo keep you in JavaScript, tauri-apps/tauri is better when desktop is the real target, and Flutter web still ships heavy bundles.

React Native126.4k★

React Native builds actual native mobile apps with native UI components, not a website wrapped in a phone frame. React Native is the most battle-tested way to do it. Write your app in JavaScript/TypeScript using React components, and it renders native iOS and Android UI. One codebase, two platforms. This is Meta's own framework, used in Facebook, Instagram, and Messenger. That scale proves it works in production. The ecosystem is enormous: navigation libraries, UI kits, native module bridges, and thousands of community packages. The New Architecture (Fabric renderer, TurboModules) has made performance significantly better than the old bridge-based system. Completely free under MIT. No paid tier from Meta. Flutter is the main competitor: Dart instead of JavaScript, pixel-perfect rendering instead of native components. Expo simplifies React Native development significantly by handling the native toolchain for you. If you're starting fresh with React Native, start with Expo, not bare React Native. The catch: "learn once, write anywhere" still means platform-specific work. Complex animations, native APIs, and platform-specific UI patterns require writing native code (Swift/Kotlin) or finding a library that bridges it. Debugging can be painful; you're debugging across JavaScript, native, and the bridge layer. Build times are slow. And the upgrade path between versions has historically been rough, though it's improving.

Electron122.6k★

Electron wraps Chromium and Node.js into desktop applications for Windows, Mac, and Linux, so you build with JavaScript, HTML, and CSS you already know. Slack, VS Code, Discord, Figma's desktop app, Notion, all Electron. You build a web app, Electron makes it a native-feeling desktop app. MIT license, maintained by GitHub (Microsoft). The ecosystem is massive. Frameworks like Electron Forge and electron-builder handle packaging, signing, and auto-updates. If you know React/Vue/Svelte, you can ship a desktop app. Everything is free. No paid tier, no commercial license. The catch: every Electron app ships its own copy of Chromium. That "Hello World" app is 150MB+ and uses 200-300MB of RAM minimum. Users complain about this constantly. If you're building something lightweight, Tauri uses the system's built-in webview instead, resulting in 5-10MB apps that use a fraction of the memory. Electron is the pragmatic choice when you want the largest ecosystem and most battle-tested tooling. Tauri is the better choice when app size and resource usage matter. Choose your trade-off.

Tauri110.3k★

Tauri lets you wrap a web frontend (HTML, CSS, JavaScript) in a native desktop shell. Same idea as Electron (which VS Code uses), but Tauri apps are dramatically smaller because they use the OS's built-in web renderer instead of shipping a copy of Chrome. Apache 2.0 and MIT dual-licensed, Rust backend. A basic Tauri app is 3MB where the Electron equivalent is 150MB+. Backend logic runs in Rust for native performance and system access. Tauri v2 added mobile support (iOS and Android), making it cross-platform for desktop AND mobile. Completely free. CrabNebula (the company behind Tauri) offers paid cloud build and distribution services, but the framework itself costs nothing. Solo: perfect for shipping a desktop app with web tech. Small teams: great for internal tools. Growing teams: evaluate whether Rust is a skill your team has. Large: consider CrabNebula for build infrastructure at scale. The catch: you need Rust for the backend. If your team is pure JavaScript, that's a real barrier. The ecosystem is younger than Electron's: fewer plugins, fewer examples, and debugging the Rust-JS bridge gets tricky. And because each OS uses its own web renderer, you'll hit cross-platform rendering inconsistencies that Electron avoids by shipping its own browser.

Wails35.9k★

Wails builds desktop apps using Go and web tech, but uses the OS native webview instead of bundling Chromium. The result: small binaries (5-10MB vs Electron's 150MB+), low memory usage, and native OS integration. MIT license. Build for Windows, macOS, and Linux from one codebase. The frontend can use any framework: React, Vue, Svelte, plain HTML. Go handles the backend logic, exposed to the frontend via auto-generated TypeScript bindings. Hot reload during development, native menus, dialogs, and system tray support. Fully free. No paid tier, no hosted version. It's a framework you develop with. Solo developers: Wails is excellent if you know Go and want desktop apps without learning a native GUI toolkit. Small teams: the Go + web stack means most web developers can contribute to the frontend. Works at any team size. The catch: native webview means your app renders differently on each OS. Windows uses WebView2 (Chromium-based), macOS uses WebKit, Linux uses WebKitGTK. Cross-platform consistency is harder than Electron where everyone gets the same Chromium. Wails v3 is in development with breaking changes from v2. And the ecosystem of plugins and community packages is much smaller than Electron's. If you need absolute cross-platform pixel-perfect consistency, Electron or Tauri (Rust-based, same webview approach) are safer bets.

shell11.5k★

This is a full desktop shell built in QML for Hyprland (a Wayland compositor). No waybar, no polybar, no cobbling together five different tools. One unified shell that handles everything, with a This thing is exploding. GPL-3.0. The shell replaces your entire desktop interface: panel/bar, notification center, app launcher, lock screen, wallpaper engine, and system controls. Built in QML (Qt's declarative UI language) for buttery animations. Fully free. The creator has a Ko-fi for donations but there's no paid tier or premium features. The catch: this only works on Hyprland (a specific Wayland compositor on Linux). If you're on GNOME, KDE, Sway, or anything else, let alone macOS or Windows, this isn't for you. It's also a dotfiles project, meaning you're adopting someone else's configuration. Customizing it means understanding QML. And the 'no waybar' philosophy means you lose access to waybar's extensive module ecosystem.

orleans10.8k★

Orleans is Microsoft's framework for building distributed systems in C# without doing the distributed-systems homework. Write ordinary classes with async methods (grains), and the runtime spreads them across a cluster, handles placement, recovers from failures, and scales. It invented the virtual actor model: grains always logically exist, so a server crash never invalidates a reference. This is the tech behind Halo and Xbox services. MIT licensed, free. Running it means hosting your own silo cluster: pick a clustering provider (SQL, Redis, Azure Tables, Consul, Cassandra) and storage providers for grain state, then deploy to Kubernetes, Azure, or your own VMs. Version 10 added a built-in dashboard for watching the cluster live, and distributed ACID transactions across grains with no central coordinator remain a feature almost nothing else in the category offers. Use it if you're a .NET shop building stateful, real-time, or high-concurrency backends: game services, IoT, financial systems. Akka.NET is the classic-actor alternative, Dapr is the answer for polyglot teams, and Temporal covers the durable-workflow overlap. The catch: .NET-only, a real learning curve on the actor model, and major versions have broken things before (v7 replaced the entire serialization system). Its popularity metrics badly understate adoption. Judge it by the production list, not the popularity contest.

zero-native7.5k★

Zero-native is Vercel Labs building genuinely native desktop apps with no browser inside them. You write views in a `.native` markup file and your logic in TypeScript or Zig, and it compiles to a native binary that ships no WebView, no Chromium, and no JavaScript runtime. That is the whole departure from Electron: native rendering (Metal on macOS) instead of a web page in a window. Apache-2.0, free. Under the hood it is mostly Zig, built on an explicit model, message, and update loop so state changes stay inspectable and easy to reason about. macOS has the deepest support; Linux runs through a software renderer, Windows through Win32, and iOS and Android are experimental. It is pre-1.0, around v0.5, with APIs still moving. One useful trick: AI agents can drive a running app through built-in automation servers for accessibility snapshots and deterministic testing. For solo developers and small teams who want real native performance and will trade the web stack to get it, this is an interesting early bet. Large teams shipping commercial desktop software should wait; Tauri and Electron have the mature plugin ecosystems and tooling depth today. The catch is that this asks you to leave the web-UI world entirely. No HTML, no CSS, no npm UI ecosystem, just a Zig-flavored markup and a message loop you have to learn. The payoff is a small, fast, truly native app. The cost is being an early adopter of an unfinished and unfamiliar stack.