--- title: "Search experience development" date: "2025-05-05T14:23:19+00:00" summary: "Explore options for implementing Acquia Search powered by SearchStax APIs in your search experience, from UI Kits to custom solutions." image: type: "page" url: "/acquia-cloud-platform/search-experience-development" id: "3c6f0114-3b69-480e-8a68-5a0e0e49854e" --- Several implementation options enable the use of Acquia Search powered by SearchStax APIs in your search experience. The following table helps you to quickly understand the benefits and limitations of the various approaches: Feature [UI Kits](#ui-kits) [Custom UI](#custom-ui) [Drupal Views](#drupal-views) **Support for all Search UX features** Yes Yes No **Highly flexible** No Yes No **Maintainability** Low High Low **Setup development effort** Low High Low The UI Kits approach is the recommended approach. The following are more detailed insights for each approach to assist in your decision-making: UI Kits ------- The UI Kits approach is the recommended approach to deploy search pages in typical site search scenarios. They include essential features such as a search box, results lists, dynamic filters, typo tolerance, and accessibility, along with additional optional UX features. UI Kits are available in several front-end frameworks, such as JavaScript, Vue, React, and Angular. These kits enable you to deploy ready-to-use components that incorporate abstracted API integrations and elegant styling, reducing your development effort. The following diagram illustrates common components within each UI Kit that deliver UX best practices for standard site search experiences: ![Search results page for "police reports" on Nashville.gov, showing filters, pagination, and related searches. Results include reports, news, and filing instructions.](https://acquia.widen.net/content/2454dcde-54e6-47f3-bdf3-11fd80c9d518/web/srsx_components-in-ui-kit.jpg?h=720&itok=sVQDZPMY) The Search UI can include downloadable components listed on [this page](https://www.searchstax.com/docs/searchstudio/search-ui-kit/). Consider allocating time to style the components' CSS to align with your organization’s brand and design. The following are the links for styling tips for each framework: * [JavaScript](https://www.searchstax.com/docs/searchstudio/styling/) * [Angular](https://www.searchstax.com/docs/searchstudio/searchstax-ux-angular-styling/) * [Vue](https://www.searchstax.com/docs/searchstudio/searchstax-ux-vue-styling/) * [React & Next.js](https://www.searchstax.com/docs/searchstudio/searchstax-ux-react-styling/) For additional resources about how to build Drupal search blocks and Drupal search pages, and use libraries for front-end frameworks with Drupal, visit [this page](https://www.searchstax.com/docs/searchstudio/building-drupal-pages-with-search-ui-kit/). Custom UI --------- When you have unique requirements for how a website visitor interacts with APIs for search and discovery, building a Custom UI for search provides the flexibility to leverage APIs as needed. The following are the links to each API reference and suggestions on typical UX components to use or position nearby for an optimal site search experience: API Link UX Components Typically Integrated [Search API](https://www.searchstax.com/docs/searchstudio/searchstax-studio-search-api/) * Search Input * Facets on the search results page * Sorting option on the search results page * Pagination on the search results page * Spell Check on the search results page [Auto-Suggest](https://www.searchstax.com/docs/searchstudio/searchstax-studio-auto-suggest-api/) * In proximity to Search Input as a dropdown before a final search is sent by the user [Related Searches](https://www.searchstax.com/docs/searchstudio/related-searches-api/) * In proximity to the Search Input component to display results as suggestions before a search is executed * On the search results page as a standalone with a separate result set displayed [Popular Searches](https://www.searchstax.com/docs/searchstudio/searchstax-studio-popular-searches-api/) * In proximity to the Search Input component to display results as suggestions before a search is executed * On the search results page as a standalone with a separate result set displayed [Analytics](https://www.searchstax.com/docs/searchstudio/searchstax-studio-analytics-rest-api/) * Search Input and search results pages to track all user searches and clicks * [Related Searches](https://www.searchstax.com/docs/searchstudio/related-searches-api/) and [Popular Searches](https://www.searchstax.com/docs/searchstudio/searchstax-studio-popular-searches-api/) are only available for the Premier Plus search plan. * The [Analytics](https://www.searchstax.com/docs/searchstudio/searchstax-studio-analytics-rest-api/) API is only available for the Premier and Premier Plus search plans. **Drupal Views** ---------------- If you want to continue to use pre-existing Drupal Views, you can use them. They continue to interact with the Search API the same way they interact when using the previous Acquia Search service. For such simplified migrations, utilize the migration submodule with instructions available on [Migrating to Acquia Search powered by SearchStax](/acquia-cloud-platform/migrating-acquia-search-powered-searchstax " Migrating to Acquia Search powered by SearchStax"). Be aware of feature limitations because Drupal Views govern the display of data returned from the search engine. As a result, many features in the SearchStax Dashboard can be toggled or modified without the changes being reflected in the front-end search experience. ### Feature limitations with Drupal Views **SearchStax Feature** **Limitation** Result’s Display Fields Settings in the Dashboard are overridden by Drupal Views. Faceting Settings in the Dashboard are overridden by Drupal Views. Sorting Settings in the Dashboard are overridden by Drupal Views. Pagination Settings in the Dashboard are overridden by Drupal Views. Spell Check Spell Check results are returned as a second API response after a no-result set is initially returned by the Search API. Drupal Views do not capture or display this second, spell-checked result set. Related Searches Drupal Views do not call the Related Searches API. A component must be created to display the results. Popular Searches Drupal Views do not call the Related Searches API. A component must be created to display the results. * Multiple Search Profiles in a Search App are only available for Premier and Premier Plus search plans. * Related Searches and Popular Searches are only available for the Premier Plus search plan.