FormEngine Integrations for React Frameworks
FormEngine works best when it fits naturally into the stack you already use. This section shows how to render JSON-driven forms inside real apps built with modern React frameworks, UI libraries, and workflow tools.Popular integration paths
Next.js
Render dynamic forms in server-rendered and app-router based React apps.
Remix
Use FormEngine in nested routes and data-driven Remix applications.
Material UI
Connect FormEngine to MUI components and design systems.
Formik
See when FormEngine complements Formik and when it replaces manual form wiring.
When to use integration pages
- you need framework-specific setup
- you want a UI-library-specific example
- you are evaluating FormEngine against your current stack
- you need to reduce custom form wiring in an existing app
FAQ
Which integration page should I open first?
Which integration page should I open first?
Start with the framework or UI library that matches your production app, such as Next.js or Material UI.
Do integrations change the JSON-driven workflow?
Do integrations change the JSON-driven workflow?
The core model stays the same. Integrations mostly affect rendering setup, UI components, and app-specific constraints.
Can I switch UI libraries later?
Can I switch UI libraries later?
Often yes. One advantage of a schema-driven approach is that the form definition is more portable than hand-coded field trees.
Next steps
Start with installation
Install the core packages and choose a component library.
Learn rendering basics
Understand the JSON-to-React rendering model first.
See product overview
Review the product positioning and use cases.