Creating a page to communicate agreed-upon FURN principles
This commit is contained in:
danielkko 2021-05-21 16:47:39 -07:00 коммит произвёл GitHub
Родитель 1700c9e4c3
Коммит bd1b8ae73a
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 15 добавлений и 0 удалений

15
PRINCIPLES.MD Normal file
Просмотреть файл

@ -0,0 +1,15 @@
> THIS DOCUMENT IS A DRAFT
# Operating Principles of Fluent UI React Native (FURN)
- FURN is multi modal – give customers what they want
- Some controls are JS
- Some are wrapped-native
- Some offer both implementations
- Cross-platform consistency is an important appeal, but exceptions should be made to account for uniqueness in native platforms – let the platform shines
- Align on names and props whenever appropriate, but don't be dogmatic
- Use Fluent UI Web as inspiration, but don't be blocked if full alignment is yet achievable
- Make local per-platform decisions when appropriate
- Some platforms are more similar than the others, and we should set expectations accordingly – drive higher consistency within a class than across classes
- Desktop OSes belong to a class
- Mobile OSes belong to another class
- Web is yet another class