Microsoft Fast Design vs Web Components

Overview

Web Components

Stacks82

Followers60

Votes0

Microsoft Fast Design

Stacks4

Followers52

Votes0

GitHub Stars9.6K

Forks609

Microsoft Fast Design vs Web Components: What are the differences?

## Introduction
In this comparison, we will explore the key differences between Microsoft Fast Design and Web Components.

1. **Architecture:** Microsoft Fast Design is based on a modular design system created by Microsoft, focusing on consistency and scalability across products. Web Components, on the other hand, are a set of web platform APIs that allow creating and using custom elements that encapsulate styling, structure, and behavior.
  
2. **Browser Support:** While Web Components are supported by all the major browsers including Chrome, Firefox, Safari, and Edge, Microsoft Fast Design is specifically tailored for Microsoft products and may not be as widely supported across different browsers.
  
3. **Customization:** Microsoft Fast Design provides a more structured and predefined set of design guidelines and components, making it easier for developers to create consistent user interfaces. Web Components offer more flexibility in customization since they allow developers to define their own reusable components.
  
4. **Components Libraries:** Microsoft Fast Design comes with a curated set of components and design patterns for building Microsoft experiences. Web Components, being a web standard, can be used with any library or framework, allowing for a broader ecosystem of components to choose from.
  
5. **Tooling:** Microsoft Fast Design is integrated with tools like Visual Studio, making it seamless to work with Microsoft's development environment. Web Components, being a web standard, can be developed using any code editor or IDE without the need for specific tooling.
  
6. **Community and Support:** Web Components have a larger community and support from major tech companies, fostering innovation and sharing of best practices. Microsoft Fast Design, being more limited to Microsoft ecosystem, may have a smaller community and resources available for developers.

In Summary, Microsoft Fast Design and Web Components differ in architecture, browser support, customization, components libraries, tooling, and community support.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Web Components, Microsoft Fast Design

Gericke

Jul 27, 2020

Needs adviceon

.NET Core

JavaScript

React

Hi,

I am looking into solutions for reusable components for an existing #MVC project which is build on .NET Core. Currently some functionality is being reuses via JavaScript. I have React experience so I know I can create React components and then reference it on the MVC app. The only problem is I do not know the full extent of it as the current app uses a lot of 3rd party libraries, not sure how that will effect React components. I am currently looking into WebComponents which is also another way for creating reusable components and it is compatible with any JavaScript library based on what I have seen on the website. Also to take in consideration that it should cause a re-write of the system.

So my question is, to future-proof reusable components, which will be best React or Web Components? And which will be more reliable to use with 3rd party libraries?

49.1k views49.1k

Comments

Detailed Comparison

Web Components	Microsoft Fast Design
Web components are a set of web platform APIs that allow you to create new custom, reusable, encapsulated HTML tags to use in web pages and web apps.	It is a collection of JavaScript packages centered around web standards, designed to help you efficiently tackle some of the most common challenges in website and application design and development.
-	Unopinionated; UI development and style guide tools; Bring your design system
Statistics
GitHub Stars -	GitHub Stars 9.6K
GitHub Forks -	GitHub Forks 609
Stacks 82	Stacks 4
Followers 60	Followers 52
Votes 0	Votes 0
Integrations
No integrations available	React Vue.js AngularJS ASP.NET Blazor Aurelia

What are some alternatives to Web Components, Microsoft Fast Design?

Bootstrap

Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web.

Foundation

Foundation is the most advanced responsive front-end framework in the world. You can quickly prototype and build sites or apps that work on any kind of device with Foundation, which includes layout constructs (like a fully responsive grid), elements and best practices.

Semantic UI

Semantic empowers designers and developers by creating a shared vocabulary for UI.

Materialize

A CSS Framework based on material design.

Material Design for Angular

Material Design is a specification for a unified system of visual, motion, and interaction design that adapts across different devices. Our goal is to deliver a lean, lightweight set of AngularJS-native UI elements that implement the material design system for use in Angular SPAs.

Material-UI

Material UI is a library of React UI components that implements Google's Material Design.

Blazor

Blazor is a .NET web framework that runs in any browser. You author Blazor apps using C#/Razor and HTML.

Quasar Framework

Build responsive Single Page Apps, SSR Apps, PWAs, Hybrid Mobile Apps and Electron Apps, all using the same codebase!, powered with Vue.

Nuxt.js

Nuxt.js presets all the configuration needed to make your development of a Vue.js application enjoyable. You can use Nuxt.js for SSR, SPA, Static Generated, PWA and more.

UIkIt

UIkit gives you a comprehensive collection of HTML, CSS, and JS components which is simple to use, easy to customize and extendable.

Related Comparisons

Microsoft Fast Design vs Web Components: What are the differences?

## Introduction
In this comparison, we will explore the key differences between Microsoft Fast Design and Web Components.

1. **Architecture:** Microsoft Fast Design is based on a modular design system created by Microsoft, focusing on consistency and scalability across products. Web Components, on the other hand, are a set of web platform APIs that allow creating and using custom elements that encapsulate styling, structure, and behavior.
  
2. **Browser Support:** While Web Components are supported by all the major browsers including Chrome, Firefox, Safari, and Edge, Microsoft Fast Design is specifically tailored for Microsoft products and may not be as widely supported across different browsers.
  
3. **Customization:** Microsoft Fast Design provides a more structured and predefined set of design guidelines and components, making it easier for developers to create consistent user interfaces. Web Components offer more flexibility in customization since they allow developers to define their own reusable components.
  
4. **Components Libraries:** Microsoft Fast Design comes with a curated set of components and design patterns for building Microsoft experiences. Web Components, being a web standard, can be used with any library or framework, allowing for a broader ecosystem of components to choose from.
  
5. **Tooling:** Microsoft Fast Design is integrated with tools like Visual Studio, making it seamless to work with Microsoft's development environment. Web Components, being a web standard, can be developed using any code editor or IDE without the need for specific tooling.
  
6. **Community and Support:** Web Components have a larger community and support from major tech companies, fostering innovation and sharing of best practices. Microsoft Fast Design, being more limited to Microsoft ecosystem, may have a smaller community and resources available for developers.

In Summary, Microsoft Fast Design and Web Components differ in architecture, browser support, customization, components libraries, tooling, and community support.

Microsoft Fast Design vs Web Components

Overview