Radosław Miernik
Jul 23, 2017 · 2 min read

Instead of passing the desired component as a string using this component directly is preferred. Although it is possible, even with <AutoForm />, because you can adjust <AutoField /> to render anything, depending on the props.

There’s no plan to support React Native out-of-box (yet?), but it shouldn’t be hard to do it directly in your project: most of the projects I know have their own theme (either a fully custom one or a variation of an existing one) so creating a React Native theme is a normal thing. Core logic — integration with schemas, data flow, context and other APIs — will behave in the same way.

How do I compare uniforms to redux-form? Well, few important points:

  • different idea: uniforms are designed to automatically generate a fully-working form from your schema; customising the whole form (or even only a part of it) was a secondary goal
  • unopinionated: there’s no good way to use any form; you can either use it as a drop-in form: just pass it a schema and onSubmit or use it as a field, where model is its value and onChange is… onChange, so you can use anywhere, even with Redux
  • UI agnostic: there are 6 built-in themes at the moment, but who said a field has to be an input? your field can be basically anything: a button, a label or even an icon — it’s simple: if something accepts value and/or call onChange it might be a field

It’s worth mentioning that redux-form is almost a year longer in here. Also, I’m not that good at marketing.

    Radosław Miernik

    Written by

    Open source? Embrace, understand, develop.