---
# System prepended metadata

title: Web framework choices

---

---
robots: nofollow, noindex
---

# Web framework choices

Goal: outline

> Excellent question, Fluent UI team is working together FAST on aligned plan, and, as a first step, FAST is already part of the Fluent UI repo. As you say web components are important part of the future, but we are not looking at them as replacement to React and the plan for Fluent UI libraries is to continue to use it.
> 
> @Markus and @Justin who run PM and Engineering for Fluent UI respectively are working with the FAST folks to make sure that we have a short white paper describing strategy here and that all public facing materials reflect this.


- Balancing the requirements around teams and guidance
- Focus on the positives

1. Initial point - Choice matters - Pick the right thing for your project and team
1. We aren't going to spell everything out, this document will give a high level way you can think about these two frameworks
2. Time (cutting edge), and browser support aspect
3. High level 
    3. Web components: lighter weight, faster, highly interoperable
    4. React: Ecosystem, established, both inside and outside of Microsoft?
5. Closing encourage folks to do their own research