JSONForms VS single-spa

I'm currently working on an Android app that requires dynamic form creation based on JSON schema. I came across the website jsonforms.io and was impressed by their framework for generating forms from JSON schema.

We use JsonForms and for multiple forms and its quite powerful & consistant

There's this cool tool called JSON Forms. Basically you specify a schema and a rudimentary form is generated based on that schema with a framework of your choosing (vue, react, angular) with no additional configuration! Sounded cool so I cloned it. Now it looks like a real time saver, but i'm concerned about how I am using an 'imported template' that will probably restrict any customization on my end.

Json Forms: https://jsonforms.io/

Yes, exactly. I did some searching after I posed the question and found this so far https://jsonforms.io/

The best way I found to build form intensive apps is using: https://jsonforms.io/ It's super declarative with JSON Schema and can be easily extended by writing custom widgets. Also it provides good balance between being "battery charged" and freedom of state management.

I agree. RJSF examples work fine but it doesn't scale well to large forms. For a similar approach but better implementation, take a look at https://jsonforms.io/ which also supports multiple frameworks.

Of course in js there's a Library for that: https://jsonforms.io/

At JupiterOne, we've made a significant transition from a monolithic frontend to a distributed frontend architecture using microfrontends, powered by (single-spa-react)[https://single-spa.js.org/]. This architectural shift has brought many benefits, such as lazy loading sections of the app and accelerating our development cycle. However, like any significant change, it has also come with its set of challenges.

Single-SPA Framework - One of the most popular choices. It has a large community behind it and offers robust routing and lifecycle management for microapps. Ref - https://single-spa.js.org/

Joel Denning is the visionary behind single-spa, boasting profound insights into the true mechanics of the web and is, in my view, a pioneer in micro frontend architecture. I highly recommend checking the single-spa website and his YouTube channel. While the videos might appear dated at first glance, rest assured, Joel is ahead of his time, and the content remains incredibly relevant today.

You got me curious and I found that single spa is something new to me - if I read https://github.com/single-spa/single-spa then I reckon you can use Svelte(Kit) in such framework - like you can use angular etc

I’ve actually done that “web components as the interoperability layer”!

It was this old angular 1.8 app with new features being written in angular-hybrid-ized angular 8. Ripping out angular-hybrid and separating the angular 1.8 routes from the modern angular routes was difficult, but now they were totally separate.

The only thing linking them together was an object with some RXJS streams in it for state, and a little in-house wrapper “app” who just loaded one component or another depending on the URL and a hash of routes for config. (I’d probably use SingleSPA [1] now. Same thing really.)

We could deploy them separately since the build just ends up being another JS file somewhere that just gets included with a script tag at runtime. No version bumping! No big mega build!

We started replacing the remaining “old” routes 1 by 1 with a “new” counter part. That was the easiest part, and went at a pace devs were comfortable with (fast enough) and business folk could tolerate. (modular enough to not HAVE to be done all at once)

Last I checked, the angular 1.8 stuff is gone years ago. :)

[1] https://single-spa.js.org/

Module Federation is not the unique solution, for example single-spa

You may want to look into using single-spa to run Vue 2 and Vue 3 side by side while you're migrating. Once your app is fully converted, you can stop using single-spa

Single-SPA and module federation are potent tools for building scalable micro-frontends. Single-spa provides a framework for building a modular front-end application. It allows lazy loading of micro-frontends, which helps improve the application's performance. In contrast, module federation enables communication and dependency sharing between different micro-frontends. It reduces code duplication, which can help with scaling an application.