Sami Jaber
Senior Software Engineer @ Builder.io
Halifax, Canada
Actions
I am the Software Lead of SDK development at Builder.io and the core maintainer of Mitosis, a compiler for framework-agnostic UI components.
I have spent nearly a decade writing code starting with data engineering, and then as a Web Team Lead at Unsplash, before joining Builder.io.
Links
Area of Expertise
Topics
The web needs an open spec for UI components
The web is very fragmented today: the proliferation of new web frameworks means that the same work is repeated over and over by countless teams and developers.
How many nearly identical autocomplete components exist in our web ecosystem? Hundreds across React, React Native, Svelte, Qwik, Vue, Angular, etc.,
With the arrival of React Server Components, will we have to rewrite the entire React ecosystem with these new constraints?
Web Components promised a solution to this problem but have not lived up to the vision.
We faced this challenge at Builder.io and found a solution: an abstract schema to describe all of our UI components. With this in hand, we were able to create Mitosis, a compiler that lets you build framework-agnostic components.
Mitosis is the engine that powers our SDKs, which work across 6 web frameworks, all from a single codebase. It also powers our top 10 Figma plugin which translates Figma designs to code in every framework!
Today, I want to talk to you about this open spec that drives Mitosis, and help you envision a better future for our web ecosystem, where many of us build on top of it.
Mitosis: an open spec for UI components
In 2023, JavaScript fatigue is more real than ever. There are so many new web frameworks, and the old ones are not shy about releasing major changes in newer versions.
If you’re a Design System maintainer, providing UI components that works across varying environments is really difficult…and forget about supporting multiple web frameworks!
Fortunately, we’ve come up with a solution that we call Mitosis: a compiler that lets you build framework-agnostic components. Mitosis provides you with an interoperability that was previously impossible, while still offering you the DX you'd expect from building a "native" UI component.
Come listen to me talk about what Mitosis is, and how you can use it to solve all your Design System woes.
It's time to de-fragment the Web
Over the past few years, the number of web frameworks available to us has exploded. In some ways, the breadth of choice is a clear win for our ecosystem. However, for many of us, it also comes with harsh drawbacks:
- Have you ever used a popular open-sourced component built for framework A, and wished it existed in framework B? What about a design system library?
- Does your company have frontends built in different frameworks, and your web teams are frustrated about the wasted hours needed to achieve a consistent design system?
- Does your team build SDKs for web frameworks, and must manually re-write them for each framework?
The solution to all 3 of these problems exists today. To fully understand it, we must first examine today’s web frameworks, re-think what a component should look like, and introduce a new Intermediate Representation of our components. This is what we have done at Builder.io when we created Mitosis, and we’re excited to share it with everyone.
Sami Jaber
Senior Software Engineer @ Builder.io
Halifax, Canada
Links
Actions
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top