Skip to main content
Fusioncat is currently in its alpha stage. The main API server is located at: https://api.staging.fusioncatalyst.io/Please note that breaking changes and bugs are to be expected, as the product is still under active development.

App Management Commands

The paw apps commands allow you to create and manage applications within your Fusioncat projects.

Commands

apps list

List all applications in a project.

Options

  • --project-id (required): The ID of the project

Examples

apps new

Create a new application.

Options

  • --project-id (required): The ID of the project
  • --name (required): Name of the application
  • --description: Description of the application

Examples

Understanding Applications

What is an App?

In Fusioncat, an app represents a consumer or producer of your API definitions. Apps can be:
  • Frontend applications (web, mobile)
  • Backend services
  • Microservices
  • Third-party integrations

App Configuration

Each app can:
  • Generate code in different languages
  • Have its own configuration
  • Use specific schema versions
  • Define custom mappings

App Types

While the CLI doesn’t enforce app types, common patterns include:
  1. Consumer Apps: Use schemas to consume data
    • Web frontends
    • Mobile applications
    • CLI tools
  2. Producer Apps: Generate data conforming to schemas
    • API servers
    • Event producers
    • Data pipelines
  3. Full-Stack Apps: Both produce and consume
    • Microservices
    • API gateways
    • Backend-for-frontend (BFF) services

Code Generation

After creating an app, you can generate code for it:
See Code Generation for more details.

Best Practices

Naming Apps

  • Use descriptive names that indicate the app’s purpose
  • Include the platform/technology if relevant
  • Examples: “React Web App”, “iOS Mobile App”, “Order Processing Service”

App Organization

  1. One app per deployable unit: Each microservice, frontend, or mobile app should be separate
  2. Shared schemas: Apps in the same project share schema definitions
  3. Version independence: Each app can use different schema versions

Development Workflow

  1. Create project and schemas
  2. Create app for your implementation
  3. Generate initial code
  4. Implement business logic
  5. Regenerate when schemas change

Examples

Multi-App Project

Microservices Architecture