UI Inspirations for React

A collection of UI concepts packed into set of small react projects. The idea behind is to leverage the latest community practices to provide useful patterns for your real-world project. By presenting specific UI elements you will learn basic and advanced solutions covering: animations & transitions, microinteractions, responsiveness, navigation, data fetching, state manipulation.

Building web application requires solving many UI problems. There are a ton of libraries that help to solve a prticular case but very often you would come up with your own solution. In that case this repository allows you to discover useful patterns for typical challenges while working on user interfaces. As you probably have noticed, project is written in react. I just feel comfortable using it. However, I think that the solutions presented here can be successfully used in other component based frameworks.

• 🎯 Direct - Embraces explicit and co-located code which is easy to delete and move from one place to another. This is an optimization for change as the change is the thing which will eventually happen. The code is direct and specific which makes it easy to copy and adapt for your needs.
• 🍏 Simple - The only way to achieve flexibility is to make things as simple and easy to change as you can. Following The Rise of "Worse is Better"

  The design must be simple, both in implementation and interface. It is more important for the interface to be simple than the implementation.

• 🍆 No classes - Only functional components.
• ❣️ Hooks - Uses hooks all the way (available as of react 16.7.0-alpha).
• 🖖 Code splitting - Uses React.lazy along with import() and let the webpack do the job.
• ⏱️ Suspense - React suspense for code splitting.
• 💅 CSS-in-JS - It's based on styled components for the look and feel.
• 📦 Promote defaults - As little configuration as possible. Uses defaults wherever it can.

• Just copy & paste whatever you need.
• Be inspired. Find UI solution you like and adapt it to your environment.

It's important to note that some low level tasks still need a libraries to allow focusing on more important aspects. All dependencies in this project were picked very carefully considering the principles mentioned earlier.

• Reach Router Because it's straighforward, composable and does directly what it should. Nothing more.
• Styled Components Simply CSS in JS with great documentation. Why not emotion? I don't know. If there is a reason I should know about, let me know!
• React Spring As the modern UI is often built upon meaningful animations, everything that encourages using them is great. The library lately offers a nice hooks API which plays directly with the DOM for better performance.

MIT License Copyright © 2019-present, Mike Skowronek