---
# System prepended metadata

title: 'Fluent UI Repo, Package, & Scopes Guidance'

---

# Fluent UI Repo, Package, & Scopes Guidance

## Our product family name is: Fluent UI
In text (documentation, logotype, emails, decks, etc., teams channels): **Fluent UI**
For example:
“The Fluent UI libraries provide a set of UI components… ”
“Here’s what you’ll be getting in the Fluent UI React release this month…”
“Add that to the Fluent UI > General channel”

In repos, package names, filenames, urls, social media handles: **fluentui**
For example:
Repos: microsoft/fluentui, microsoft/fluentui-react-native, microsoft/fluentui-android, etc.
Packages: @fluentui/utilities, @fluentui/styling, @fluentui/icons

## UI Library Product Names
The pattern is that you prepend "Fluent UI" to the technology or platform that the product leverages/targets so that it is clear to developer customers what the product targets or uses. This should provide teams with a pattern to follow when we welcome new technology solutions into the Fluent UI product family. For example if we decided to expand in the web space, we could use the following: Fluent UI Web Components, Fluent UI Vue. Also if we collaborate with other technologies: Fluent UI Adaptive Cards - this would be the specific Adaptive Cards render that uses Fluent UI components. 

The following are the list of engineering products our collective teams all contribute to:
 - Fluent UI React
 - Fluent UI React Native
 - Fluent UI iOS & Mac
 - Fluent UI Android

Open issues:
- [ ] 1.	Fluent UI iOS & Mac - It is unclear if Apple has a collective name for all their OSes: iOS, macOS, iPadOS, watchOS, tvOS. We could use names like Fluent UI AppleOS, Fluent UI Apple, Fluent UI Cupertino, etc. However, I don’t know from a Product naming 
- [ ] 2.	WinUI and Xamarin. These products already have established brand names. It's possible to keep them intact and prepend Fluent UI WinUI, but that feels odd. Fluent UI Xamarin doesn't feel too weird. 
- [ ] 3.	It's unclear if we can official take two names and concatenate them together. We need to run this by the naming team and we officially need to name them to something like "Fluent UI for React," "Fluent UI for React Native" and then we can just refer to it as Fluent UI React after.
- [ ] 4.	Fabric Core Icons - Holistically we should roll iconography into the Fluent product family. We need to determine the resourcing, ownership, and product vision for a product akin to Fluent UI Icons. For Fluent UI libraries that use font based iconography, they should take a dependency on. Adaptive Cards specifically is looking for a Microsoft solution for iconography
- [ ] 5.	Design Toolkits. Need to follow up to ensure they are 1:1 to Products and where they are hosted. For example, is there a Fluent UI React Design Toolkit and a Fluent UI React Native Design Toolkit… or are they essentially the same? Do we call it the Fluent UI Android Design Toolkit? 



