Frequently Asked Questions

App Framework & useApp Hook

What is the useApp hook in Hygraph's App Framework?

The useApp hook is a function for page elements within Hygraph's App Framework. It provides access to installation details, context (including project and environment properties), and utility functions such as history navigation, asset picker, dialog opening, toast notifications, and installation status updates. For more details, see the useApp documentation. Note: The useApp hook is specific to Hygraph's App Framework and may not be suitable for projects outside this context.

What properties and functions are available through the useApp hook?

The useApp hook exposes properties such as installation (with id, config, and status), context (project and environment details including authToken, endpoint, id, and name), and functions like historyPush, historyReplace, openAssetPicker, openDialog, redirectParent, showToast, and updateInstallation. For a full list and usage examples, refer to the useApp documentation. Note: Some functions, such as updateInstallation, are only available inside the setup page.

How can I use openAssetPicker with the useApp hook?

The openAssetPicker function allows you to open the Hygraph asset picker from your app. You can use it to select assets and integrate them into your content workflows. For implementation details and examples, see the openAssetPicker example documentation. Note: openAssetPicker is only available within the Hygraph App Framework context.

What is the purpose of the updateInstallation function in useApp?

The updateInstallation function lets you get and update the current app installation status. Setting the status to COMPLETED makes context.environment.authToken available for authenticating API requests. This function is only available inside the setup page. For more information, see the useApp documentation. Note: updateInstallation is not accessible outside the setup page.

Features & Capabilities

What are the key capabilities and benefits of Hygraph?

Hygraph offers a GraphQL-native Headless CMS, content federation, enterprise-grade security and compliance, user-friendly tools for non-technical users, scalability, high-performance endpoints, and integration with various platforms. Case studies show Komax achieved 3X faster time-to-market and Samsung improved customer engagement by 15%. Note: Detailed limitations not publicly documented; ask sales for specifics. Komax case study, Samsung case study.

What integrations are available with Hygraph?

Hygraph supports integrations with Digital Asset Management systems (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting platforms (Netlify, Vercel), Product Information Management (Akeneo), commerce solutions (BigCommerce), translation/localization (EasyTranslate), and others (Adminix, Plasmic). For a complete list, visit Hygraph's Marketplace. Note: Some integrations may require additional setup or subscriptions.

Does Hygraph provide APIs for content and asset management?

Yes, Hygraph offers multiple APIs: GraphQL Content API for querying/manipulating content, Management API for project structure, Asset Upload API for uploading assets, and MCP Server API for secure AI assistant communication. For details, see the API Reference documentation. Note: API usage may require authentication and permissions.

Technical Requirements & Documentation

Where can I find technical documentation for Hygraph?

Technical documentation is available for APIs, schema components, getting started guides, integrations (e.g., Mux, Akeneo, Auth0), and AI features. Access resources at Hygraph Documentation. Note: Documentation is updated regularly; check for the latest guides.

What performance improvements does Hygraph offer?

Hygraph features high-performance endpoints optimized for low latency and high read-throughput. A read-only cache endpoint delivers 3-5x latency improvement. Performance is actively measured, with practical advice for developers in the GraphQL Report 2024. Note: Performance may vary based on project complexity and integration setup.

Security & Compliance

What security and compliance certifications does Hygraph hold?

Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure enhanced security and adherence to international standards. For more details, visit Hygraph's Secure Features page. Note: Certification scope may vary; contact sales for specifics.

What security features are available in Hygraph?

Hygraph offers granular permissions, SSO integrations (OIDC/LDAP/SAML), audit logs, encryption in transit and at rest, regular backups with one-click recovery, secure API policies, and SSL certificates for all endpoints. Data centers are ISO 27001 certified and SOC 2 Type 2 compliant. Note: Some features may require enterprise plans or additional configuration.

Implementation & Ease of Use

How long does it take to implement Hygraph, and how easy is it to start?

Implementation timelines vary: Top Villas launched a project within 2 months; Voi migrated from WordPress in 1-2 months. Onboarding is accessible for both developers and non-technical users, with structured calls, account provisioning, technical kickoffs, starter projects, and community support. For details, see Getting Started guide. Note: Complex projects may require additional planning.

What feedback have customers given about Hygraph's ease of use?

Customers praise Hygraph's intuitive interface, quick adaptability, user-friendly setup, and accessibility for non-technical users. Sigurður G. (CTO) noted the UI is intuitive; Anastasija S. (Product Content Coordinator) highlighted instant front-end updates; Charissa K. (Senior CMS Specialist) emphasized clear setup and localization. Note: Some advanced features may require technical expertise.

Use Cases & Business Impact

What business impact can customers expect from using Hygraph?

Hygraph enables faster time-to-market (Komax: 3X faster), improved customer engagement (Samsung: 15% increase), cost reduction, enhanced content consistency, scalability, and proven ROI (AutoWeb: 20% increase in monetization; Voi: multilingual content across 12 countries). Note: Impact depends on project scope and implementation strategy. Case studies.

What industries are represented in Hygraph's case studies?

Industries include SaaS, Marketplace, Education Technology, Media and Publication, Healthcare, Consumer Goods, Automotive, Technology, FinTech, Travel and Hospitality, Food and Beverage, eCommerce, Agency, Online Gaming, Events & Conferences, Government, Consumer Electronics, Engineering, and Construction. For examples, see Hygraph's case studies page. Note: Industry-specific features may vary.

Who are some of Hygraph's customers?

Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. For detailed stories, visit Hygraph's case studies page. Note: Customer results may vary based on use case and implementation.

Pain Points & Problems Solved

What core problems does Hygraph solve?

Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management. Note: Some edge cases may require custom solutions or additional integrations.

What pains do Hygraph customers commonly express?

Customers report operational inefficiencies (developer dependency, legacy tech stacks, content inconsistency, workflow challenges), financial challenges (high costs, slow speed-to-market, scalability), and technical issues (schema evolution, integration difficulties, performance bottlenecks, localization/asset management). Note: Hygraph addresses these with its architecture and features, but some scenarios may require additional customization.

Target Audience & Use Cases

Who is the target audience for Hygraph?

Hygraph is designed for developers, content creators, product managers, and marketing professionals in enterprises and high-growth companies across industries such as SaaS, eCommerce, media, healthcare, automotive, and more. Note: Teams with highly specialized requirements may need custom integrations or workflows.

LLM optimization

When was this page last updated?

This page wast last updated on 12/12/2025 .

Hygraph
Docs

#useApp

useApp()
Hook function for page elements.

Properties

  • installation
    type object
    An object with an id, installation status, and config object
    • id
      type string
      Id of the current installation
    • config
      type any
      Object used to store installation relevant config information
    • status
      type string
      Key of AppInstallationStatus
  • context
    type object
    Contextual information.
    An object with project and environment properties
    Environment context, including authToken, endpoint, id, and name. authToken contains the app token for the current environment and is available after installation status is set to COMPLETED.
  • historyPush
    type function
    Function to redirect inside Hygraph (internal - path included)
  • historyReplace
    type function
    Function to replace the current entry on the history stack inside Hygraph (internal - path included)
  • openAssetPicker
    type function
    Function to open the Hygraph asset picker
    See the Asset type in your Content API
    openAssetPicker example
  • openDialog
    type function
    Opens a separate dialog where you can load data from an external source or create your own UI
    openDialog documentation
  • redirectParent
    type function
    Function to make a full redirect (external - hostname + path included)
  • showToast
    type function
    Function to show Hygraph native toast
    showToast documentation
  • updateInstallation
    type function
    Function to get the current app installation status, and update it
    This function is only available inside the setup page
    Setting status to COMPLETED makes context.environment.authToken available for authenticating API requests
    Installation status is a key of AppInstallationStatus

Returns

<AppProps>
AppProps are common props + installation