Case Study: GraphCMS and DMarket
Powering in-game trading with a Headless CMS for gaming marketplaces, enhanced with AI and Blockchain.
SportScheck and Fitfox choose GraphCMS to power their new, mobile-first product with a Headless CMS for sports and fitness.
GraphCMS allowed us to create different type of content (fitness studios, events, sport items) in a very short period of time and, at the same time, the webhooks and the GraphQL API made it possible to get an easy layer on top.
Fitfox is the innovation arm of SportScheck, a Germany-based sports equipment and clothing retailer with over 1600 employees. The company’s vision is to become a sports activity platform – the booking.com of sports.
Fitness-on-demand is the most important trend in the activity and sports industry right now. Fitfox and SportScheck are launching a new product – the Pulse Club. The Pulse Club mobile-first web application is a loyalty program with exclusive benefits like clothing and equipment discounts and personalized recommendations for sports articles and activities. It also offers a free ticket SportScheck RUN, free access to a gym and free delivery of SportScheck goods. Moreover, members have an exclusive access to SportScheck articles from brands like Nike, Adidas, FitBit and Under Armour.
GraphCMS is used for managing the entire content architecture of the mobile application:
The team, led by Antoine Verger, CTO of Fitfox, follows the principles of agile product development. Rapid development cycles, modular architecture and strict product KPI monitoring are the foundation of their work.
The team was firmly against building their own CMS from scratch. The total cost of ownership of having GraphCMS in their stack was much lower and without the associated risks of maintaining a complex system on your own. The team was free to fully invest in features that are directly related to SportScheck's core business. GraphCMS offers an extremely flexible API that can satisfy any custom content modeling and API design needs.
The key technology trend that Antoine Verger identifies is the need for a software product to be “an ecosystem player”. An application’s content should be available via a flexible API. Other services will certainly need to access it – for either adding a specific functionality via another microservice, or for powering a new product in the future.