The Process
When Line Break started qualifying their needs for headless content management, they looked at some of the hosted solutions which were too big and expensive (for example IBM Websphere). Homebrew solutions like combining a MongoDB-based backend with a React frontend didn’t give them the “hands-off” scalability they required.
Hygraph struck the right balance for them with the simplicity and intuitive design they were seeking. Hygraph has become a daily flexible tool for both the Developers and the Content Editors of Line Break and Cleveland Clinic.
Why Hygraph?
The Cleveland Clinic team chose Hygraph for the following reasons.
GraphQL Content APIs APIs
In the past, Line Break built RESTful APIs for its clients, and were keen to migrate from REST to GraphQL. Building the AR+ App was the first time that Line Break worked with GraphQL. They found that the syntax is concise and logical; you can set up powerful APIs in minutes.
Intuitive UI
The intuitive Hygraph UI enables the Content Teams to enrich the app with more information around the art pieces, the artists, and other helpful resources for those at Cleveland Clinic. The Content Editing functionality has all of the functionality the team needs, and is simple enough for the content team to use regularly.