React Native Material Design vs Semantic UI: What are the differences?
React Native Material Design: React Native UI Components for Material Design. An open source project which aims to bring Material Design to Android through React Native by Facebook. The library is made up of many components, which can be found in the sidebar; Semantic UI: A UI Component library implemented using a set of specifications designed around natural language. Semantic empowers designers and developers by creating a shared vocabulary for UI.
React Native Material Design belongs to "Mobile UI Frameworks" category of the tech stack, while Semantic UI can be primarily classified under "Front-End Frameworks".
"Unmaintained" is the primary reason why developers consider React Native Material Design over the competitors, whereas "Easy to use and looks elegant" was stated as the key factor in picking Semantic UI.
React Native Material Design and Semantic UI are both open source tools. Semantic UI with 45.7K GitHub stars and 4.83K forks on GitHub appears to be more popular than React Native Material Design with 3.12K GitHub stars and 398 GitHub forks.
What is React Native Material Design?
What is Semantic UI?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using React Native Material Design?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
ReactQL is written in TypeScript to provide full types/Intellisense, and pick up hard-to-diagnose goofs that might later show up at runtime. React makes heavy use of Webpack 4 to handle transforming your code to an optimised client-side bundle, and in throws back just enough code needed for the initial render, while seamlessly handling
import statements asynchronously as needed, making the payload your user downloads ultimately much smaller than trying to do it by hand.
React Helmet was chosen to handle
<head> content, because it works universally, making it easy to throw back the correct
<title> and other tags on the initial render, as well as inject new tags for subsequent client-side views.
<style> tags when using #StyledComponents.
React Router handles routing, because it works both on the server and in the client. ReactQL customises it further by capturing non-200 responses on the server, redirecting or throwing back custom 404 pages as needed.
Koa is the web server that handles all incoming HTTP requests, because it's fast (TTFB < 5ms, even after fully rendering React), and its natively #async, making it easy to async/await inside routes and middleware.
We use Semantic UI for our frotend. A heavily customised version of it, but still Semantic UI under the hood.
Used Semantic UI + Angular2 together with Spring or Node/Express for full stack web application development.