“Reflex Frontends compile down to a React app and Reflex allows developers to wrap their own React Components to use in their apps.”
Frontend FrameworkMaker says so +1 · source ↗
React
JavaScript library for building user interfaces from components, used for web apps and, through React Native, native apps.
Works with AI agents:llms.txtReact is a JavaScript library for building user interfaces out of components: functions that take data (props and state) and return markup. It handles the view layer of an app; routing, data fetching and server rendering come from elsewhere.
You describe what the UI should look like for a given state, and React re-renders the affected components when that state changes. Components are usually written in JSX and can be typed with TypeScript. The React team now recommends starting through a framework such as Next.js or React Router, or Expo for native apps; starting from a bare build tool like Vite, Parcel or Rsbuild is the do-it-yourself route.
Recent React adds Server Components, which run at build time or on the server and send rendered output instead of code, plus Server Functions and a build-time compiler that applies memoization automatically. Server Components need a framework or bundler that implements them. React runs in any modern browser, and React Native extends the same model to iOS and Android.
The main limit for a small team is that React alone is not an app. Without a framework you choose and wire up routing, data loading and rendering yourself, and the React docs say this amounts to building your own framework that you then have to maintain.
Where it fits
How React itself is built
1 tools, from its own code, website and Product Hunt page.
Who uses it
200 makers' products, each linked to the source that shows it, and 1,193 open-source projects that declare it in their code.
“Listed in their tool stack on Starter Story (stack)”
Frontend FrameworkMaker says so · source ↗“Mature ecosystem, hooks, and predictable composition. The SDK’s components stay framework-friendly and portable.”
Frontend FrameworkMaker says so · source ↗“Listed in their tool stack on Starter Story (stack)”
Frontend FrameworkMaker says so · source ↗“Listed in their tool stack on Starter Story (stack)”
Frontend FrameworkMaker says so · source ↗“Listed in their tool stack on Starter Story (stack)”
Frontend FrameworkMaker says so · source ↗“The foundation of our UI. Every tap, swipe, and test you see in QualGent is brought to life with React’s flexibility and elegance.”
Frontend FrameworkMaker says so · source ↗“Primary tech for the apps our solution build”
Frontend FrameworkMaker says so · source ↗“Listed in their tool stack on Starter Story (stack)”
Frontend FrameworkMaker says so · source ↗“Listed in their tool stack on Starter Story (stack)”
Frontend FrameworkMaker says so · source ↗“Listed in their tool stack on Starter Story (stack)”
Frontend FrameworkMaker says so · source ↗“Listed in their tool stack on Starter Story (stack)”
Frontend FrameworkMaker says so · source ↗“The best web app framework.”
Frontend FrameworkMaker says so · source ↗“Latest concurrent features. Server Components cut bundle size dramatically.”
Frontend FrameworkMaker says so · source ↗“React offers a component-based approach that allows for reusable code, making development faster and more maintainable. Compared to alternatives like Angular, React’s flexibility and ease of integration with other technologies make it a preferred choice for building scalable user interfaces.”
Frontend FrameworkMaker says so · source ↗“Listed in their tool stack on Starter Story (stack)”
Frontend FrameworkMaker says so · source ↗“Listed in their tool stack on Starter Story (stack)”
Frontend FrameworkMaker says so · source ↗“The library for web and native user interfaces Legendary framework, nothing to add!”
Frontend FrameworkMaker says so · source ↗“React powers both sides of Pluto Door — the website (via Next.js) and the desktop app (via Tauri). One language, one component model across everything. The ecosystem is huge — xterm.js, React Three Fiber, and Framer Motion cover almost any need. Vue.js, Svelte, and SolidJS are great, but React’s ecosystem makes it the most productive choice when building in small team.”
Frontend FrameworkMaker says so · source ↗“At Rankfender, we actually use both—they complement each other rather than compete. Here's why: Why React? Component reusability. We built a dashboard with complex data tables, real-time AI answer updates, and charting libraries. React's component model keeps this maintainable as we scale. Ecosystem. React Query for data fetching, Recharts for visualizations, React Router for navigation—the ecosystem is unmatched. Developer experience. Fast refresh, hooks, and a massive community mean we ship faster. Why Tailwind CSS? Speed. No jumping between files to write CSS. We style components inline and move on. Consistency. Utility classes enforce design tokens—spacing, colors, typography—across the entire app. Bundle size. PurgeCSS removes unused styles automatically. Our CSS stays lean even as the UI grows. The combo: React handles the heavy lifting (state, logic, API calls). Tailwind makes it look good—fast. For Rankfender, that meant shipping a polished dashboard in weeks, not months.”
Frontend FrameworkMaker says so · source ↗“Accelerated our engineering development immensely.”
Frontend FrameworkMaker says so · source ↗“Component-based UI framework for dynamic web apps.”
Frontend FrameworkMaker says so · source ↗“Listed in their tool stack on Starter Story (stack)”
Frontend FrameworkMaker says so · source ↗Open source: a project that declares React as a dependency in its public code — verifiable, but not necessarily a live product.
What makers say
99 makers on why they use React, in their own words on Product Hunt.
At Rankfender, we actually use both—they complement each other rather than compete. Here's why: Why React? Component reusability. We built a dashboard with complex data tables, real-time AI answer updates, and charting libraries. React's component model keeps this maintainable as we scale. Ecosystem. React Query for data fetching, Recharts for visualizations, React Router for navigation—the ecosystem is unmatched. Developer experience. Fast refresh, hooks, and a massive community mean we ship faster. Why Tailwind CSS? Speed. No jumping between files to write CSS. We style components inline and move on. Consistency. Utility classes enforce design tokens—spacing, colors, typography—across the entire app. Bundle size. PurgeCSS removes unused styles automatically. Our CSS stays lean even as the UI grows. The combo: React handles the heavy lifting (state, logic, API calls). Tailwind makes it look good—fast. For Rankfender, that meant shipping a polished dashboard in weeks, not months.
RankfenderSep 2026 ↗At Rankfender, we actually use both—they complement each other rather than compete. Here's why: Why React? Component reusability. We built a dashboard with complex data tables, real-time AI answer updates, and charting libraries. React's component model keeps this maintainable as we scale. Ecosystem. React Query for data fetching, Recharts for visualizations, React Router for navigation—the ecosystem is unmatched. Developer experience. Fast refresh, hooks, and a massive community mean we ship faster. Why Tailwind CSS? Speed. No jumping between files to write CSS. We style components inline and move on. Consistency. Utility classes enforce design tokens—spacing, colors, typography—across the entire app. Bundle size. PurgeCSS removes unused styles automatically. Our CSS stays lean even as the UI grows. The combo: React handles the heavy lifting (state, logic, API calls). Tailwind makes it look good—fast. For Rankfender, that meant shipping a polished dashboard in weeks, not months.
RankfenderFeb 2026 ↗React’s component-based architecture allows for modular development, making it easier to maintain and scale applications. The large ecosystem of libraries and tools, such as React Router for navigation and Redux for state management, enhances its functionality. The active community provides a wealth of resources, tutorials, and support, which is invaluable for both learning and troubleshooting.
Face IndexSep 2026 ↗React powers both sides of Pluto Door — the website (via Next.js) and the desktop app (via Tauri). One language, one component model across everything. The ecosystem is huge — xterm.js, React Three Fiber, and Framer Motion cover almost any need. Vue.js, Svelte, and SolidJS are great, but React’s ecosystem makes it the most productive choice when building in small team.
Pluto DoorSep 2026 ↗React offers a component-based approach that allows for reusable code, making development faster and more maintainable. Compared to alternatives like Angular, React’s flexibility and ease of integration with other technologies make it a preferred choice for building scalable user interfaces.
TestMu AISep 2026 ↗Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises, with how Product Hunt tags its reviews.
- Its component model breaks complex interfaces into small reusable pieces that are easy to maintain. PHPH 2PH 3PH 4
- The ecosystem of libraries and tools is huge and battle-tested. PHPH 2PH 3PH 4
- The same approach carries over to web and native mobile apps. PHPH 2PH 3
- Makers find it fast to iterate on while the product is still changing. PHPH 2PH 3
Reliability and open issues
- Hooks + multiple instances of React👍 291 · opened Oct 2018 · active Jul 2026
- Formalize top-level ES exports👍 250 · opened Nov 2017 · active May 2026
- createPortal: support option to stop propagation of events in React tree👍 228 · opened Oct 2017 · active May 2026
- [eslint-plugin-react-hooks] allow configuring custom hooks as "static"👍 172 · opened Sep 2019 · active May 2026
- Provide a way to handle browser-autocompleted form values on controlled components👍 160 · opened Feb 2014 · active Jun 2026
Who switches
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general. Open a row to see the pull requests.
Astro → React21 PRs
- Fix Astro example to use React 19edmundhung/conform · 2026-08-22
- Migrate the website from Astro to ReactJMRBDev/ai-directory · 2026-08-19
- Migrate portfolio from Astro to React 19 with TanStack Router and Queryjoaocdfarias/joaocdfarias.github.io · 2026-05-31
- Update index.astro to match React reference UIslopratchet/000.cauldron.it.com · 2026-05-31
- refactor(ui): rewrite astro components to reactmonaboiste/bero · 2026-05-28
- feat: migrate frontend from Astro to React + ViteSebasjp4/Bushipagina · 2026-05-24
- Migrate from Astro to Vite with React RouterSigmaBuilder/Client · 2026-05-08
- refactor(grade): migrate Grade component from Astro to React and centralize grade utilitiesfshowalter/franksmovielog.com · 2026-03-31
- Migrate Astro components to React for interactive featuresjohnpangalos/blog.pangalos.dev · 2026-03-26
- Migrate game UI from inline Astro script to React components (Astro retained)eviltimrogers/guess-the-airline · 2026-02-26
Next.js → React21+ PRs
- Migrate from Next.js web app to Expo React Native mobile app1001pranav/expenseMonster · 2026-10-01
- Convert frontend from Next.js to React + ViteAsheesh7298/customer-churn-detection-project-final · 2026-09-29
- Fix Netlify deploy error by upgrading Next.js to support React 19 stablefireflyyogaretreatbali-svg/jevel-s-by-vinza · 2026-09-26
- [FE-01] Migrate frontend from Next.js to React + Vitesaumyashah0510/Multi-Agent-Research-System-Architecture · 2026-09-26
- chore(frontend): upgrade Next.js 14 to 15 with React 19PaladinKnightMaster/ai-image-edit · 2026-09-22
- refactor: :recycle: Migrate from Next.js to Vite with React Routeralessioforte/beehive · 2026-09-17
- Migrate from Next.js to React Router with Cloudflare Workerszackdotcomputer/my-homepage · 2026-09-12
- refactor: next.js to react+vitemaat-apps/routines · 2026-09-10
- chore: upgrade Next.js 15 to 16.3.4 with React 19.2crispal94/Analyzer-shoes-AI · 2026-09-02
- Refactor: Migrate from Expo+Next.js to single responsive React PWAalonbenitzhak-alt/horse-farm-platform · 2026-08-25
SvelteKit → React8 PRs
- Rewrite Yahtzee scorekeeper from SvelteKit to React with ViteTheRauch1/yahtzee · 2026-08-13
- refactor: migrate web app from SvelteKit to React with new component structure and page routingDev-Card/DevCard · 2026-06-03
- refactor: migrate web app from SvelteKit to React with new component …Dev-Card/DevCard · 2026-06-03
- Migrate frontend from SvelteKit to React + Vite with Framer MotionAlidrix/The_Trend_Scope · 2026-05-04
- feat: migrate from SvelteKit to React 19 + TanStack Starthfrdmnk/morgenblau · 2026-02-25
- Migrate from Tauri/SvelteKit to rngpui React Native + Rust backendundivisible/vuno · 2026-02-14
- Migrate from SvelteKit to React with React RouterDaniel-BD/personal-tracking · 2026-02-10
- Migrate/sveltekit to reactjaem1n207/synchronize-tab-scrolling · 2025-10-17
React → Astro123 PRs
- Migrate from React + Vite to Astro static siteCTJ425/script-docs · 2026-10-02
- Migrate site from React to Astro for performancemini-artemis/Web-Veterinaria · 2026-09-30
- build: migrate from Vite + React to AstroOpen-Sourcery-UMD/umdcoffee · 2026-09-29
- Move the site from React to Astrothedhanawada/me-plus · 2026-09-27
- Remove React, migrate to Astro components, improve a11yFueRobertHer/astro-portfolio · 2026-09-25
- Docs: scope the move from the React SPA to AstroUnderstory-Collaborative/understory-collab · 2026-09-22
- feat: migrate site from React + Vite to Astro with Cloudflare Pages a…Jivaansh-Yadav/icse-resources · 2026-09-19
- Rework: Migrate from React SPA to static Astro siteUser420-bit/Website · 2026-09-14
- Migrate portfolio from React SPA to Astroheidenreich20/Portfolio-2026 · 2026-09-06
- perf: convert presentational React islands back to Astromarco-rossoconsulting/astia-web · 2026-09-04
React → Next.js73+ PRs
- Migrate from Vite + React to Next.js with bilingual catalogsaraitmanar/FlashElectronicsWebsite · 2026-10-02
- Migrate from Create React App to a Next.js static exportFremen1990/react-portfolio-devthomas · 2026-09-30
- Upgrade React.dev to Next.js 15.5.26devjiwonchoi/next-agent-upgrade-dogfood · 2026-09-28
- Migrate React project to Next.jsfiqriachmada/fe-my-indekos · 2026-09-27
- Refactor: Migrate from React Native to Next.js web appRocmaDL/DebtTracker · 2026-09-27
- feat: migrate portfolio from Vite + React Router to Next.js 16CodesofAkash/Personal-Portfolio · 2026-09-27
- Migrate from Vite/React to Next.js with TypeScriptkunospw/deesprofesionalportfolio · 2026-09-26
- Migrate from Vite/React to Next.js and restructure projectvovineb/Queensy-BnB · 2026-09-25
- Migrate from Create React App to Next.js 16edboaden/chessdailypuzzle · 2026-09-23
- Migrate frontend from React to Next.js App Routernaveensnsgroups/Todo_Mern · 2026-09-23
React → Nuxt19 PRs
- Migrate portfolio from React to Nuxt 3 + Vue 3Poyopote/Portfolio · 2026-09-16
- feat: enhance React to Nuxt migration with new translation features a…mohd-ashif/code-migration-tool · 2026-07-13
- feat: add React to Nuxt transformation utilitiesmohd-ashif/code-migration-tool · 2026-07-13
- Migrate from React + Vite to Nuxt 4SeppeVE/MixtapeMaker · 2026-07-03
- Migrate from React to Nuxt 3 with TypeScriptPoyopote/Portfolio · 2026-06-09
- Port React design to Nuxt 4ai-builders-id/rental-mobil-anak · 2026-06-07
- feat: migrate web layer from Next.js/React to Nuxt 3/Vue 3Abi-shai/tolbi-trace · 2026-06-01
- Migrate from React to Nuxt 3 with redesigned portfolio siteAbeldewit/abeldewit.github.io · 2026-03-18
- Convert Gatsby (React) to Nuxt 3 (Vue)aremu-smog/alukobrown · 2026-03-18
- Migrate React control panel frontend to Nuxt 3 SPA (nuxt-new/)borsuczyna/CmdHub · 2026-03-07
React → SvelteKit17 PRs
- Migrate from React to SvelteKit with native CSS and Svelte 5 runescocreating/TheCharlatan · 2026-09-29
- Migrate product UI from Next.js/React to SvelteKit and update build/toolingfozagtx/DriftRecon · 2026-09-07
- Migrate from Next.js/React to SvelteKitjooshua-inglis/pdf-editor · 2026-08-27
- feat: migrate frontend from React to SvelteKit SPArmwahid/full-stack-fastapi-template-but-svelte · 2026-08-27
- Migrate application from React to SvelteKitzmjohnso/photo-voice · 2026-06-13
- feature: migrate from React to SvelteKit 5 + Bits UIPromptPasture/neatmark · 2026-05-25
- Full rewrite of Khmer Dictionary from React to SvelteKitsrghma/khmer · 2026-04-19
- feat: migrate from Next.js/React to SvelteKit 2 + Svelte 5 (runes)ocknamo/split-bill-calculator-on-nostr · 2026-03-28
- Convert codebase from React to SvelteKitawei82/sds-svelte · 2026-02-26
- Migrate website from React to SvelteKit1aurentius/k-stacks-website · 2026-02-19
React → React Router11+ PRs
- Migrate client from Create React App to Vite and React Router 7DC-Cunningham/TheBeautRev · 2026-10-02
- chore: Updated react router dom to react routerlinagora/twake-contacts-frontend · 2026-09-29
- Upgrade dependencies and bring the React and Angular skills up to React Router 8, Vite 8, and Angular 21formio/ai · 2026-09-28
- migration: react router dom to react router with modern syntaxsubrataroy912/Campus-Mind · 2026-09-02
- Upgrade to React 18, migrate to React Router 6, and enhance Auth0 integrationEcommerce-Chilly/PF-Chilly · 2026-08-30
- chore(web): fix react-hooks warnings + opt in to React Router v7 future flagslumoryxr/lumo-task-web · 2026-08-27
- Upgrade apps/web from React Router 7 to React Router 8 (Decision Log #28)Tracymao/soccernity-mvp · 2026-08-22
- Fix Heroku build: upgrade React 18 to 19 for React Router 8andrewmoody96/ciyp · 2026-08-12
- test(react-router): migrate the integration test to React Router 8thelooter/apollo-client-integrations · 2026-08-12
- feat(react-router): widen peer range to include React Router 8apollographql/apollo-client-integrations · 2026-08-03
Alternatives to React
All alternatives by situation →Questions makers ask about React
Do I need a framework to use React?
Not strictly, but the React team recommends one for new apps. You can start from a build tool like Vite instead, at the cost of solving routing, data fetching and server rendering yourself. source ↗
Can a React app run without a server?
Yes. The recommended frameworks all support client-only single-page apps and static generation that deploy to a CDN, and let you add server rendering per route later. source ↗
Can I use Server Components in a plain Vite app?
Not on their own. Server Components need a bundler or framework that implements them, such as the Next.js App Router, and the low-level APIs for building that support can still change between React 19 minor versions. source ↗
Does React work with TypeScript?
Yes. Install the @types/react and @types/react-dom packages and use .tsx files for JSX; all the recommended frameworks support TypeScript out of the box. source ↗
Can I add React to an existing site built with another stack?
Yes. You can serve one section of the site, such as everything under a sub-path, from a React app, or render React components into parts of existing pages without rewriting the rest. source ↗
How often does React make breaking changes?
Stable releases follow semantic versioning and major versions are rare. Upcoming breaking changes show up first as development warnings, codemods are often provided, and security fixes are backported to affected older majors. source ↗
Can I build mobile apps with it?
Yes, through React Native. The React docs point to Expo as the framework for building Android, iOS and web apps from one codebase. source ↗
Is React free?
Yes — it is free, open-source software.
Is React open source or self-hostable?
Open source. source ↗
Can AI coding agents work with React?
It serves an llms.txt docs index.
Who uses React?
200 makers' products we track, each with a source, and 1193 open-source projects declare it in their code. source ↗