Choose the Right Approach to Build Your Search UI

Coveo provides a variety of ways to build a search interface. Which approach is the best for you depends on your business needs.

Here’s a summary of the pros and cons of each approach for building a Coveo-powered search UI:

Hosted Search Pages

If you want to quickly build a demo or proof of concept, we recommend that you use hosted search pages. These are interfaces that reside in, and are served through, a Coveo organization. You can modify them with the Interface Editor.

Pros Cons

No need to worry about the deployment infrastructure.

Cannot customize the search page URL.

No need to worry about implementing authentication.

Users must be members of the Coveo organization that hosts the search page.

In-Product Experiences (IPX)

To quickly integrate a lightweight search UI within any web-based application, consider using an IPX. You can modify it with the Interface Editor.

Pros Cons

Easy to deploy in any web site or application.

Not easy to do advanced customization.

Requires minimal programming skills.

Only works with browsers that support web components.

Interface Editor

You can use the Interface Editor, which is a WYSIWYG editor based on the JavaScript Search Framework, to edit both IPX and hosted search pages, as well as search pages in some integrations.

Pros Cons

Requires little to no developer skills.

Not flexible.

Useful for experimenting, prototyping, and building basic search pages.

Only usable to edit hosted search pages, In-Product Experiences (IPX), and search pages in certain product integrations (e.g., Coveo for Salesforce).

JavaScript Search Framework

The JavaScript Search Framework is a collection of components that you can use to assemble feature-rich search interfaces. It’s both customizable and extendable to suit your individual use cases.

Pros Cons

Customizable through styling.

Only suitable for building web-based search UIs.

Extendable through custom components.

Strong coupling between UI and logic layers.

Headless Library

The Headless library is a Redux-based toolset for developing your own search UI component libraries. It provides the functionality of the JavaScript Search Framework without tying that functionality to a specific UI implementation.

Pros Cons

Usable in any environment that can run JavaScript.

Still in Alpha.

Extendable through custom middlewares and reducers.

Requires advanced programming skills.

REST APIs

Both the JavaScript Search Framework and the Headless library are built on top of our REST APIs. Those APIs are publicly documented, and you can develop directly against them if you need to integrate Coveo search features in an environment that can’t run JavaScript.

Pros Cons

Flexible.

Complex.

Lets you build a Coveo-powered search UI in an environment that can’t run JavaScript.

Error-prone.

Recommended Articles