Developers who are familiar with JavaScript Front-end frameworks know how to build reusable components and utilize them for lesser code repetition and clean architecture. We write markup and logic for every new requirement or enhancement that comes up. Also, most of the time we have to do a lot of conditional rendering. Whatever we do, we eventually write static code in our project. It is fine because that is how we all do it.

But what if I say we can eliminate the hustle of writing code for every new requirement or enhancement in existing work. We do not write the code yet new requirements get implemented themselves on the compile-time and changes reflect on the browser. Sounds crazy right? Well, we can achieve this phenomenal mechanism by generating UI on compile-time via a data model (which we also called metadata).
This metadata is nothing but a smart contract between Front-end and Back-end developers in the form of JSON (can be other formats) that tells our Front- end implementation what to render on the Browser. Hence, we remove the dependency of modifying Front-end implementation to incorporate new changes.

This mechanism is derived from the Data-Driven Programming approach and is being called "Data-Driven User Interface".

In this talk, I want to show how we can achieve this approach in our new or existing codebase. Also, what are the pros and cons of adopting it and when we should or should not adopt this approach.

- This talk is more like a workshop so I would prefer the timeslot for the session should at least be of 45-60 minutes.
- The targeted audience is intermediate JavaScript developers who know how to work with at least one of its frameworks.