Roadmap

This is a tentative roadmap of the high-level enhancements we're working on or planning for Relay. Note that we're using the issues page to track bugs and as a venue for discussing these enhancements with the community. If you're curious about one of the tasks below and we haven't already created an issue, feel free to file one!

In progress:

• Support persisting data for offline use: @yuzhi.
• Support deferred queries: #288 by @wincent.
• Field-level cache eviction and query tracking: #537 by @joesavona.
• Real-time updates via an event-based Subscription API: #541 by @skevy (contributor).
• Support arbitrary root fields (avoids the need for a viewer wrapper field): #112 by @steveluscher.
• Support extracting queries at build time: @yungsters.
• Create Relay dev tools: @kassens.
• Make OSS Relay & React Native work together: #26 by @zpao, @spicyj, and others.
• Support multiple Relay contexts in the same JS environment (for server rendering): #558. by @devknoll (contributor).

Future enhancements:

Smaller enhancements are tagged with 'enhancement' and are a great place to start if you're interested in contributing. The following are some larger-scale changes that we plan to address:

• Simplify the mutations API: #538.
• Gracefully handle the lack of a network connection.
• Support client/local state
  • API for resolving fields locally: #531.
  • Support querying & compiling client-only fields by extending the server schema, and a means for writing data for these fields into the cache: #114.
• Draw a clear distinction between Relay core (imperative APIs for data-fetching) and the React/Relay integration (declarative APIs such as RelayRootContainer and RelayContainer). This would allow experimentation and iteration within each layer. #559.