Reflex Roadmap #2727

This issue is the public, living copy of the Reflex Framework Roadmap. It describes the major initiatives for Reflex 0.10.0, v1.0, and beyond. Each section links its tracking issue and the individual issues behind it. Last updated: October 2026.

Feel free to comment to leave feedback or upvote any issues you'd like to see prioritized, and we welcome outside contributions for any issues.

Why This Roadmap

Reflex exists so that Python developers can build production web apps without learning JavaScript. That promise only holds if the framework is stable enough to bet a product on, simple enough that you spend your time on ideas rather than plumbing, and fast enough that users never notice there's a Python backend behind the UI.

Every initiative below serves one of those three goals. If the team executes on these items, Reflex becomes the best Python web framework for human developers and AI agents alike — a framework where a single rx.event handler is simultaneously a reactive UI binding, an HTTP endpoint, and an MCP tool, all without extra code.

Key Focus Areas

Stability — As we approach 1.0, we're making the core API stable and limiting breaking changes so Reflex can be a solid foundation for long-term projects.

Simplicity — Improve the out-of-the-box experience so developers can focus on their ideas. This means a growing third-party component ecosystem, simpler APIs for core components, and fewer required dependencies.

Speed — Reflex apps should be fast for end users and developers alike. We're investing in compile-time performance, hot-reload times, and runtime efficiency so apps stay fast as they grow.

Event System

Tracking issue: #6236

• EventHandler awaitable semantics — EventHandler redesign: awaitable semantics #6223
• Thread pool executor for sync events — Explicit thread pool executor for sync event handlers #6225
• Event lifecycle hooks
  • on_connect hook — on_connect lifecycle hook for @rx.event #6229
• Background task exit on disconnect — Make it easier to exit a background task when the socket disconnects #5049
• EventHandler return values — EventHandler return values: stream yielded/returned values to the frontend #7608
  • Frontend queues an event and may use for await ... syntax to process each yielded/returned value - crucially uses async iterator style for all events as it is the superset of supported python syntaxes
  • Each request will require an id to allow multiple in-flight requests to identify their results

State Refactor

Tracking issue: #7612

• Var tracking mixin — Var tracking mixin: dirty/accessed field tracking independent of rx.State #6228
• Field setters — rx.Field setter decorators with frontend compilation support #6230
• Field change observers — rx.Field change observers (@field_name.on_change decorator) #6231
• Move BaseState and friends into reflex-base — ENG-10096: Make Field, ComputedVar and EventHandler state descriptors #7312 (merged), Move the core state machinery into reflex_base.state #7314
• Separate distributed lock manager from state manager — Replace StateProxy with state locks held by the EventContext #7313, Check out states in the EventContext, make StateManager a key-value store #7338
• Simplify StateManager API (to make downstream implementations possible) — Check out states in the EventContext, make StateManager a key-value store #7338

Frontend

Tracking issue: #7613

• Ship static frontend javascript as an installable JS package — Ship the frontend runtime JavaScript as an installable npm package #7609
• Include JS tests for frontend functionality using standard tooling — Unit-test the shipped frontend JavaScript with standard JS tooling (vitest) #7611
• Minify user JS in rx.script tags — Minify js code in rx.script tags #3034
  • Do as part of secure script eval, outputting the script to a standalone file and letting vite minify
• ClientStateVar refactor — Refactor ClientStateVar: scoped client state via a useClientState hook (rx.client_state) #7610
• Frontend-only hot reload — reflex run --frontend-only should support hot reload #2294

Components

• Reflex-native component library — Reflex-native component library built on base HTML elements #6247
• Immutable Components — Single-pass compiler: Make Component effectively immutable #6214 (under the Single Pass Compiler tracking issue Single Pass Compiler: Tracking Issue #6235)
• Remove interim Tag in Component render pipeline — Remove interim Tag in Component render pipeline #7618
  • Component.render returns a Var representing the jsx function call instead of a Tag or render dict. The Var carries the hooks, imports, and app wraps the component requires. (breaking)

Backend

• Consolidate endpoints under /_reflex/ — Consolidate all internal endpoints under /_reflex/ prefix #6226

Security

• Safe frontend eval environment — Safer script evaluation #6208
  • Use request IDs so the backend can eval a function and wait for the result to come back
• Token Protected Endpoints — JWT-based authenticated event processing #6232. Phase 0 (signed session cookies for event transport) is in progress: Keep request credentials out of frontend router data #7360, Add signed browser sessions and bound client tokens #7361, Authorize browser state through session-aware transports #7362, Persist browser sessions without delaying hydration #7363, Validate enforced sessions and document migration #7364

Developer Experience

• Event loop blocking detection — Implement event loop blocking detection #7619
• Move entire integration test suite to playwright (WiP) — Move the integration test suite to Playwright #7617
• Organize test suites by subpackage (reduce number of tests need to validate changes in subpackage)
• Unified exception handler API — Unify generic frontend/backend exception handler API #5168
• Remove Pydantic v1 hacks — Remove unsupported hacks to use Pydantic v1 #6241
• Reduce install footprint — Reduce External Dependencies #4921
• Config via pyproject.toml — Config via pyproject.toml with app profiles #6240
• ASGI interoperability — ASGI Interoperability — mountable Reflex sub-app #6239 (also addresses Embedding Reflex in other apps #46, the oldest open issue)

Database & ORM

Make the database layer less opinionated. Remove custom ORM abstractions that get in the way while keeping an easy-to-use experience built on standard SQLAlchemy and Alembic. If you know SQLAlchemy, you should feel at home. If you don't, rx.session and reflex db still give you a gentle on-ramp.

rx.Model will be deprecated in favor of bring-your-own model base. reflex-orm becomes a separately installable package — useful for convenience, never required.

Tracking issue: #6238

• Extract reflex-orm package — Extract reflex-orm package #6243
• Remove rx.Model — Remove rx.Model #6244
• Simplify rx.session + reflex db — Simplify rx.session and reflex db CLI #6245

Internationalization & Localization

Highly requested by the community. I18N/L10N framework support will let developers build apps that serve global audiences without rolling their own translation infrastructure.

• I18N/L10N framework support — Internationalization (I18N) and localization (L10N) (Feature Request)  #2339 (top voted feature request)

v1.0 Release Gate

• Remove v1.0-promised deprecated functionality. Once every pre-1.0 breaking change above has landed, remove the deprecations promised for 1.0 and cut the release.

Please leave comments on what you think about this tentative plan.