metaUI can reduce code duplication by generating your UI at runtime. This leads to an overall reduction in maintenance cost and a lower occurrence of UI based bugs. Use of metaUI can streamline your development workflow and focus on what’s really important, delivering great experiences and business value to your users.
metaUI is heavily inspired by CCS due to it being highly flexible and composable. Developer has ability to rewrite any rule, that results in powerful customization and allows generating wide variety of UI shapes and forms.
metaUI takes your data model
Reads metadata describing this model (OSS Rules) just like CSS rules
It creates stack of assigments: Object is Invoice, Operation is Edit
Run this against the meta rule set to compute the effective key/value property map
Dynamically derive the whole UI for you on the fly without templates, rather than letting you layout your fields manually for every use case
Don't repeat yourself principle. Reducing repetition of software patterns, replacing it with abstractions or using data normalization to avoid redundancy.
Let you extend and fully customize existing applications to apply to different business use cases.
metaUI Rule engine is independent of its UI layer to give you the ability to plug-in your own library. It was built to allow to use 3rd party "component" without wrapping
For all of these metaUI gives you a way to derive specific UI for each of them.
metaUI can use object introspection to register some implicit rules (such as type, field name, class name, current values)