We're out with 1.0 release of ReactiveSearch for Vue. It provides scaffolding to build complex Search UIs in record time by taking care of querying, managing search state and updating your UI. It also comes with over 10 built-in components that help you get started in minutes. Direct Github link: https://github.com/appbaseio/reactivesearch.
We always get the question about why someone should use it, and we also think about this a lot.
- ReactiveSearch provides declarative props for the most common search scenarios: e.g. how to use auto-suggestions, how to handle search typos, how to tune weights, apply relevance. Instead of specifying how to achieve these outcomes, a user just specifies the desired outcome. This makes building search UIs accessible to all developers v/s just search engine users. It also makes it inherently safer and easier to change these.
- Combined with the ability of specifying props, ReactiveSearch components come with built-in components that have presets on how to render the search box, facets, results.
- ReactiveSearch doesn’t get in the way when you want to specify how to achieve a certain search scenario — you can write your own Query DSL for it. You can also bring in your own UI components and design systems.
- Above all, ReactiveSearch is Apache 2.0 licensed, actively maintained and is relied on by hundreds of projects for their production search use-cases. Aside from Vue.JS, ReactiveSearch also comes in React and React Native flavors.
- If you are an appbase.io user, ReactiveSearch can additionally record search and click analytics out-of-the-box (it requires an opt-in). You can use Appbase.io with any ElasticSearch cluster.
Since this is the very first time we're putting this out there, would love to hear feedback from the community.
If you're looking to just get started with it, see the quickstart guide here: https://docs.appbase.io/docs/reactivesearch/vue/overview/quickstart/.
Top comments (0)