reactivesearch VS react-motion

The SearchBox component is part of the ReactiveSearch UI kit: https://github.com/appbaseio/reactivesearch and works with Elasticsearch, OpenSearch, Solr, and MongoDB Atlas Search as search engine backends. Support for OpenAI is coming soon - star or watch the repo to be in the loop for this one.

reactivesearch has the most stars from what I can find on GH. I've never used one either, maybe someone else will have a better suggestion.

This is a follow-along post (takes a couple of hours to build this end-to-end) showing how to build a consumer grade search UI using React and Elasticsearch. It makes use of the https://github.com/appbaseio/reactivesearch library (Apache 2.0 licensed) that's being used by over 1,000 projects for building their search UI.

It kinda depends what you have and what you want out of it, for https://demo.rapidez.io/women/tops-women we use Reactivesearch (Vue variant): https://opensource.appbase.io/reactivesearch/

🤩 Reactive Search- UI components for building data-driven search experiences.

ReactiveSearch - UI components library for Elasticsearch

Github repo : https://github.com/chenglou/react-motion

React-Motion is an animation toolkit that makes building and implementing realistic animations much easier. However, React-Motion can be hard to grasp for beginners. But it has good documentation with rich examples to help developers.

React Motion is an animation library for React applications that makes realistic animations easier to build and implement.

Here's a comparison showing how the transition-hook bundle size compares to other React animation libraries: react-spring, framer-motion, react-motion, and react-move:

Framer Motion is a production ready animation library for React. I felt the need to add some "cool" animations to my portfolio so that it looks more alive and interactive. One can argue between choosing React Spring or React Motion but that depends on the use-case and since I've already worked with Framer motion before so I went with this.

Ah I found it. "On the Spectrum of Abstraction" by Cheng Lou (author of React-Motion)

https://github.com/chenglou/react-motion

React Motion

Thanks. Let me write some information concerning our ClojureScript frontend. We wanted to use physics-based animations using springs since only these animations make sense. Sadly the browser decided to only support silly animations which are described in terms of curves and durations. Spring animations are used on both MacOS and iOS and they look much better, since they have the natural feeling. Originally, we were using React Motion for them which would be fine for a small project. But running a lot of animations at the same time is very taxing since every frame of the animation has to go through React and all these layers. Therefore, I spent about 4 months completely rewriting most of our frontend code related to rendering and UI interactions within OrgPage. Unlike React Motion and probably any other spring-based animation library, we do not simulate these springs but instead analytically solve their differential equations. (Luckily I have a strong background in math.) I created the OrgPage https://orgpad.com/s/yRyR-GOU0Pm which summarizes math and my approach. Our animations code consists of about 5k lines of code where maybe 1k is the physics itself and computation of animation maps. The remaining 4k lines are low level controls where particular OrgPage elements are animated using requestAnimationFrame. We always calculate their new positions/sizes/etc. and apply DOM mutations, completely bypassing React, Reagent and Re-frame. There are a lot of clever optimizations to get the current speed. In upcoming months, I plan to investigate WebGL rendering which we could use to render larger parts of the documents, hopefully making everything even faster.

react-motion - A spring that solves your animation problems

Motion/transitions, powered by react-motion