Business take on

uniforms

What are/is uniforms?

Wait, there's more than one?

What about our competition?

Fast facts

1. Are multi-page forms or wizards supported?
   • Yes, but it's just a normal form (docs).
2. Are translations handled out of the box?
   • Yes, either on a schema or UI level (docs).
   • Errors are a different story (more here).
3. Are there TypeScript type declarations?
   • Yes, uniforms are 100% TypeScript code.
4. Can I create custom fields? Of course!
5. Can I create custom themes? Of course!
6. Can I create custom bridges? Of course!

There are limits, right?

1. No built-in focus management.
   • Requires custom components.
2. No built-in conditional logic.
   • Requires custom components.
3. No built-in server-side logic.
   • This includes populating a dropdown with data from an API.
4. No "manual" (schema-less) version.

It makes sense if...

• You have a lot of forms.
• You have user-defined forms.
• You need automatically built forms.
• You want a strict separation of UI and logic.
• You want the forms to be ready soon.

• You have only a few forms.
• You have forms that won't change.
• You have no need for using schemas at all.

Levels of integration

1. Start with an official theme.
2. Add custom components.
   • It's far easier now (docs).
3. Create a fully customized theme.
   • It's easy as well (docs).
4. Customize the bridge.

$$$

1. Yes, it's "almost free" to prepare a PoC, where all of the forms are automatically generated.
   • With an assumption that schemas are already there.
   • Without them, it may be faster not to use any form package at all.
2. Yes, it's possible to replace them with customized ones later.
3. Yes, components and themes can be reused in other forms and applications.

Key takeway

Questions?