---
# System prepended metadata

title: When to use what

---

---
robots: noindex, nofollow
---

# When to use what

# outline
- Intro around philosophy of Fluent UI choice
  - Technologies move and change, this is always in flux, you should make the decision that makes sense for your team
  - Our goal is to give you the right technologies for you to build your project
- Give broad examples Bing/Edge WC, Office/Teams React. Orgs bet on React/WC. 
- Enumerate what is in common between the two. What are the benefits both bring
- While each technologies shares most of the same benefits. Here are a few cases where you may choose one or the other
- For example if you are doing this, you may want to consider this (keep it soft)
  - If .NET -> WC, If multi platforms -> WC
  - If part of React ecosystem -> React
- Conclusion

---
- What are your requirements
- For instance
  - bing edge -> WC
  - Office teams -> React
- However it's difficult
  - for instance, if you need to support blazor you want to use WC
  - 



---
Scratch 
# React
- When you need ie11 or old edge support
- If you have an existing React app
- React has a fixed cost in terms of budle size and performance
- Benefits
  - React programming model
  - Existing investments in React
  - Community support

# Web components
- Lower barrier to entry, it's just HTML

- Dimensions
  - expertise of team
  - app ecosystem

---
- Presenting the technology
  - IE11 and spartan
  - Don't compare
  - Let teams choose





