# supermedium/aframe-react

:atom: Build virtual reality experiences with A-Frame and React.

Repository: https://github.com/supermedium/aframe-react
Canonical: https://ross.abutalabs.com/products/aframe-react
Homepage: https://ngokevin.github.io/aframe-react-boilerplate/
Language: JavaScript
License: MIT
License Family: permissive
Topics: react, vr, aframe, virtual-reality, webvr
Last push: 2024-06-19T15:56:27+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 3913, "days_push": 805, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1432, forks 149 (observed 2026-08-28T04:04:43.167705+00:00)

## What it is
aframe-react is a thin React binding layer for A-Frame that exposes Scene and Entity components so developers can declaratively build virtual reality (WebVR) experiences in JavaScript. The maintainer now recommends vanilla A-Frame instead, warning that React's render overhead conflicts with real-time 3D frame budgets.

## Use cases
- build VR scenes with React components
- create WebVR experiences in the browser
- compose A-Frame entities declaratively in JSX
- build 360-degree virtual tours on the web
- prototype VR apps in JavaScript with React
- render interactive 3D scenes using React state

## When to choose
- Your team is React-first and building a simple, mostly-static VR scene or 360 tour
- You want declarative JSX composition of A-Frame entities without managing the DOM manually
- You are prototyping lightweight VR experiences where per-frame performance is not critical

## When to avoid
- Performance-critical real-time 3D/VR applications - the maintainer explicitly recommends vanilla A-Frame with aframe-state-component instead
- Projects that would place 3D or tick-based logic in the React layer, causing re-renders and memory garbage
- Applications that need to strictly follow A-Frame's entity-component-system pattern without a React abstraction

## Facets
- artifact type: library
- maturity: maintenance
- function: ui-components, frontend-framework, graphics
- domain: web-development, frontend, graphics
- platform: browser, cross-platform
- tags: react, aframe, vr, virtual-reality, webvr, webxr, 3d, react-bindings, ecs, threejs, declarative-scene-graph, game-development, nodejs

## Member repositories
- supermedium/aframe-react (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:43.167705+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T04:37:03.471519+00:00, confidence not recorded.
  - readme: https://github.com/supermedium/aframe-react (fetched 2026-08-28T04:04:43.167705+00:00, sha 0f8342c8bb9e)
  - homepage: https://ngokevin.github.io/aframe-react-boilerplate/ (fetched 2026-08-29T11:48:41.533203+00:00, sha a3a800ea19bb)
- Data as of 2026-08-30T08:39:29.467469+00:00.