You can change the styling, add features, and publish your own branded storefront as a PWA (Progressive Web Application) by importing these libraries into your custom app.
Spartacus is decoupled from the backend platform, meaning it runs on its own separate server node and communicates with the platform (Typically SAP Commerce Cloud) only through REST APIs. It’s a single-page application, meaning that only a single HTML page gets loaded, then the rest is driven by code. This strategy translates into good performance because Spartacus is a PWA that only loads the parts of the page that require updating.
Despite being a single-page application, SAP Spartacus supports search indexing and SEO as if each page view was independent. At its core, Spartacus will allow search indexing from web crawlers since Spartacus supports server-side rendering. The apps also control the URLs, so when users browse, they see proper URLs such as products/category/shoes.
Since version 5.0, Spartacus was officially renamed to SAP Composable Storefront by SAP.
So even though “SAP Spartacus” is the most common name to refer to it, its official name is now “SAP Composable Storefront”. SAP officially supports all Commerce Cloud Customers with the Composable Storefront angular-based libraries.
Spartacus was an open-source project which served as a base for the new hybris storefront: the SAP Composable Storefront. However, versions 4.x and older are not officially maintained anymore, meaning that all projects are transitioning from Spartacus to SAP Composable Storefront.
It is important to note that on-premise customers can still use Spartacus libraries and edit them as they want. Let’s remember that they are open-source. Nevertheless, SAP Composable Storefront should be the go-to option for anyone starting an SAP Commerce implementation project, as it’s the hybris PWA successor.