@gogola Caught in the middle of swapping out a new website design, everything should work now. Will be adding a lot of stuff over the day iteratively now. https://github.com/appbaseio/rea... is a good place to read into the details.

@davethackeray the data is stored in appbase.io, a realtime DB service built on Elasticsearch. A major design consideration with ReactiveSearch has been that users don't need to learn / write complex DSL based queries needed for complex search scenarios. This is done by. 1. High Level components: For instance, DataSearch component provides an out of the box search UI with toggle-able highlighting, autocompletion props. It only asks the user to specify the field(s) on which to search on. At the same time, the user can write a custom query to bypass the component's default query -- but this shouldn't be needed 95% of the times. 2. Composing Complex Queries: Result views (internally referred as actuators) can specify which components' (aka sensors) should be combined and queried against, via a single user-specified prop. 3. Good UI defaults: Besides handling the data parts, provide good UI defaults (close to vanilla) that can be easily customized. Since the components can be put inside any grid layout (Bootstrap, Materialize, Your Own), the possibilities are endless. 1. and 2. are possible precisely because of the tight coupling with the DB service. :-)

@andrea_kalmans ReactiveSearch - which uses appbase.io as the data backend) enables building great search focused UIs for the web. Reactive Maps, also launched here https://www.producthunt.com/post... enables building realtime map UIs. Both libraries are fully open-source, actively maintained and we have already seen weeks of time saved in market launch when using them. More UIs and native mobile support to come soon!