Overview

Apps in Hantera are resources meant for packaging multiple Hantera resources into a single distributable unit. They provide a structured way to group resources so they can interact together within a reusable, installable module.

This is achieved by defining all required resources and related files in an h_app.yaml file. This manifest acts as the central configuration that links those resources together inside an app.

Through this packaging model, developers can structure reusable units of backend logic, exposed APIs, and automated workflows that mirror their internal systems while mapping to Hantera's resource model.

Example Implementations

Apps can be used to:

• Create a custom returns and claims system tailored to your organization’s workflows
• Use webhooks to source order and delivery data from a storefront into Hantera
• Enable product lookup from an external system directly inside the Hantera portal
• Implement automated discount logic, validation rules, or background jobs
• Integrate external APIs and services

What an App Can Declare

An app can declare Hantera resources such as:

• Components (Reactor, Rules, Discount)
• Ingresses
• Registry entries
• Job definitions

The three component types that can be declared by an app are registered in the Components resource class. They execute within their respective runtime (Reactor, Rule, or Discount), and are mapped by other resources in Hantera to enable these use cases.

In addition, apps can include static files. The portal extension is a CLI-powered mechanism that bundles these files into the app package. When the app is installed, those files are loaded into Hantera’s portal runtime.

Through a portal extension, an app can:

• Extend views
• Inject components into UI slots
• Register services
• Create navigation sections
• Fetch and present data