Hygraph
HygraphReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
700 reviews
from
External reviews are not included in the AWS star rating for the product.
CMS with potential, but lacking many features
What do you like best about the product?
- Conditional fields
- Cloud-based
- API Playground
- Webhooks – they allow for easy integration of ISR in Next.js applications
- Cloud-based
- API Playground
- Webhooks – they allow for easy integration of ISR in Next.js applications
What do you dislike about the product?
Unfortunately, there are more things to dislike:
- It lacks such a basic feature as content duplication, which is terrible! When we have an array with items that have identical data and differ in only one element, you still have to input it 20 times!
- Singletons! Oh my, why is this important feature missing? Sometimes, and even often, it's necessary to create a model that allows setting globals like Navigation, Footer, etc.
- Conditionals: It's great that they exist, but they need refinement. When you don't select a value in the Enum that is used as the basis for multiple conditionals, they all show up.
- There's no option to group components, enums, models, etc., in the Schema view. When you have a larger number of them, they start to overwhelm the screen.
- Why, if I want to create an array of some objects, do I have to create a special new component for that? It's very cumbersome and unnecessarily consumes the maximum number of components! This essentially makes it impossible to implement a larger site that allows the dynamic creation of subpages based on the design system introduced into the CMS.
- If a component is required and it’s a single component, the options within that component should be available to fill in immediately, not only after clicking the “add” button.
- There should be an option to create enums with a local scope, not just a global one. Global enums are also nice, but there's a lack of local scope options.
- This is not a crucial feature, but it would simplify CMS implementation for developers: the ability to define schemas directly in code, as done by PayloadCMS, Sanity, or TinaCMS.
- It lacks such a basic feature as content duplication, which is terrible! When we have an array with items that have identical data and differ in only one element, you still have to input it 20 times!
- Singletons! Oh my, why is this important feature missing? Sometimes, and even often, it's necessary to create a model that allows setting globals like Navigation, Footer, etc.
- Conditionals: It's great that they exist, but they need refinement. When you don't select a value in the Enum that is used as the basis for multiple conditionals, they all show up.
- There's no option to group components, enums, models, etc., in the Schema view. When you have a larger number of them, they start to overwhelm the screen.
- Why, if I want to create an array of some objects, do I have to create a special new component for that? It's very cumbersome and unnecessarily consumes the maximum number of components! This essentially makes it impossible to implement a larger site that allows the dynamic creation of subpages based on the design system introduced into the CMS.
- If a component is required and it’s a single component, the options within that component should be available to fill in immediately, not only after clicking the “add” button.
- There should be an option to create enums with a local scope, not just a global one. Global enums are also nice, but there's a lack of local scope options.
- This is not a crucial feature, but it would simplify CMS implementation for developers: the ability to define schemas directly in code, as done by PayloadCMS, Sanity, or TinaCMS.
What problems is the product solving and how is that benefiting you?
I am just a frontend developer implementing a large website. Unfortunately, there are much better alternatives on the market within a similar pricing range. All the problems I mentioned in the previous section highlight the difficulties in implementing Hygraph. It's also worth mentioning the component limit! In the pricing, there is a mention of a 150-component limit. If this is true, then implementing any large website that relies on dynamically building pages using a design system within the CMS becomes impossible!
Great Content Management System
What do you like best about the product?
* The admin API and ease of content/module building
* Ease of connecting between environments
* Speed
* Ease of connecting between environments
* Speed
What do you dislike about the product?
* The User Interface is engineering friendly, but some of our content editos are not as into it
* Could see some improvements in migrating models between environments
* Could see some improvements in migrating models between environments
What problems is the product solving and how is that benefiting you?
Creating a way for our marketing team to create content quickly
Great tool for use directly out-of-box
What do you like best about the product?
It's easy to setup, integrate and use in your system or platform. They are also active on teaching/learning and provided some talks in our company showcasing the platform.
What do you dislike about the product?
We miss a page builder with a rich preview.
What problems is the product solving and how is that benefiting you?
It saves us time when in need to implement a content management system that is easy to use and we can put directly in non technical hands.
Great platform for your interfacing for data
What do you like best about the product?
I use hygraph for creating interfaces for my datasets. It works perfectly for that. It is very developer friendly (and oriented in a way) but results in a simple cms ui. I think it is powerful, though it comes with a cost (if you need more than the free plan)
What do you dislike about the product?
The pricing plans are enterprise minded. The cms ui could be simplified for non technical users.
What problems is the product solving and how is that benefiting you?
A cms i can bring to customers for a nextjs websites.
Good CMS with Some Complex Features
What do you like best about the product?
I like using Hygraph because it provides a good overview and is easy to navigate. The user interface is clean, making it simple to manage content. Overall, Hygraph is a solid choice for managing content, especially if you’re looking for a modern solution. Just be prepared to spend a little time learning some of the more advanced features.
What do you dislike about the product?
Some features can feel a bit too complex or intricate, which might be challenging for beginners.
What problems is the product solving and how is that benefiting you?
It enables the unification of data from multiple sources into a single API, which simplifies the content operations and reduces redundancy.
A tool like no other
What do you like best about the product?
As a developer who's worked with various CMS platforms, I'm consistently impressed by Hygraph. It's quickly become my go-to solution for building dynamic and content-rich websites and applications.
What do you dislike about the product?
Learning Curve: While Hygraph is relatively easy to learn, getting started with GraphQL might require some initial effort for developers unfamiliar with it.
Pricing: Hygraph's pricing can be a bit steep for smaller projects or individual developers. However, the value it provides justifies the cost for larger projects and businesses.
Pricing: Hygraph's pricing can be a bit steep for smaller projects or individual developers. However, the value it provides justifies the cost for larger projects and businesses.
What problems is the product solving and how is that benefiting you?
Hygraph-powered websites and apps are incredibly fast. The platform's global CDN and optimized content delivery ensure a smooth and snappy user experience.
Hygraph is absolutely amazing.
What do you like best about the product?
Hygraph is really good for API calls, I have had much worse experiences with platforms like Firebase where my data gets compressed. Hygraph is a great alternative to platforms like that.
What do you dislike about the product?
My colleagues don't know about Hygraph so they didn't accept it at first. Hygraph could do better at marketing.
What problems is the product solving and how is that benefiting you?
Hygraph has made the entire API calling process for my open source independent projects really fast and efficient. It's fairly easy to set up as well.
Unmatched Characteristics and Problems-Free Usage
What do you like best about the product?
Cool — Some of the features speak to me and yet an interface feels like an area that should be easy to navigate/transcribe/resolve. Keeps the navigation simple yet very customizable. Moreover it has also lessened the workload for us to a great extent due to its powerful content modeling and integration capabilities. In truth, it is a much more efficient and truly contextual form of content management — organization and collaboration better than ever due to these attributes.
What do you dislike about the product?
Sincerely, it would be nice if the welcome were friendlier. As is, the helping hands and instructions seem a bit few and far between. More fully fleshed-out step-by-step guides and manuals would help get the newbies settled in and taking advantage of the many cool features this application has.
What problems is the product solving and how is that benefiting you?
In a way, Hygraph addresses quite a number of the major pain points that many enterprises are already suffering from in the course of their normal content management and content distribution practice. For example, it makes very easy the distribution of content to several different systems. Work as such is often inefficient with messages being disjointed, brand manuals getting violated, a lot of work invested… just to mention a few.
Efficient resource management with Hygraph. It only made processes a lot simpler, but it literally helped to save so much time. They make this API-driven approach so easy, that a content can effortlessly be integrated and disseminated across various websites and applications without falling into some endless rubbish of update request loops.
In addition, customize and manage multi-language content, codification or data is another strong point while adaptability is another crucial merit. But for a global corporation, it would be something tough because you have to interact a lot and with polygots, and with lots of different accents. This is where Hygraph ameliorates the issue in content and language variations management, thus easing your task of handling diverse content versioning.
Efficient resource management with Hygraph. It only made processes a lot simpler, but it literally helped to save so much time. They make this API-driven approach so easy, that a content can effortlessly be integrated and disseminated across various websites and applications without falling into some endless rubbish of update request loops.
In addition, customize and manage multi-language content, codification or data is another strong point while adaptability is another crucial merit. But for a global corporation, it would be something tough because you have to interact a lot and with polygots, and with lots of different accents. This is where Hygraph ameliorates the issue in content and language variations management, thus easing your task of handling diverse content versioning.
Hygraph as an international student and Intern
What do you like best about the product?
Hygraph enables me to generate content for my company as an intern in the best and most orderly manner. It makes it easier to integrate and implement my work to the web on a weekly basis.
What do you dislike about the product?
I don't have much to say on the negative side and would not be able to comment on the available customer support as I haven't even had to use it.
What problems is the product solving and how is that benefiting you?
It makes time management and content generation much faster.
Hygraph is amazing
What do you like best about the product?
When I used Hygraph for my react native projects, I found that it is much much faster and efficent compared to other API platforms like Firebase because the data quality isn't compromised and the experience is still fast.
What do you dislike about the product?
Not a lot of people in my team knew about it, so there was some resistance to adopting Hygraph.
What problems is the product solving and how is that benefiting you?
It makes the entire process of managing APIs much much better and practical compared to Firebase like I mentioned earlier. Makes development easier and hasslefree.
showing 251 - 260