Overview
Offerings are the building blocks of the Vibing AI ecosystem, allowing developers to extend and enhance the platform in various ways. The platform defines five primary offering types, each with unique characteristics and use cases.App
A full-featured application with rich UI and comprehensive functionality.Characteristics
- Complete application experience with dedicated interface
- Can implement multiple interface surfaces
- Deep integration with platform capabilities
- Comprehensive user flows and functionality
- Persistent state and data management
Use Cases
- Document editors and content creation tools
- Project management systems
- Data analysis and visualization dashboards
- Creative tools and design applications
- Media management and playback
- Productivity suites
Development
Apps are created using the App Framework:Plugin
A specialized extension that enhances platform functionality, often with minimal UI.Characteristics
- Focused on specific capabilities rather than standalone experiences
- Lightweight UI footprint
- Tight integration with core platform
- Can extend other offerings
- Often operates behind the scenes
Use Cases
- File format converters
- Data connectors and integrations
- Workflow automations
- Content enhancement tools
- Search enhancements
- Message processors
Development
Plugins are created using the Plugin Framework:Agent
A specialized AI assistant with domain expertise, primarily using natural language interfaces.Characteristics
- Deep knowledge in specific domains
- Natural language interface
- Can use tools and external resources
- Purpose-built for specialized tasks
- Integrated with Vibing Super Agent
Use Cases
- Research assistants
- Creative partners (writing, design, music)
- Coding experts
- Domain specialists (legal, medical, financial)
- Teaching and training assistants
- Productivity coaches
Development
Agents are created using the Agent Framework:Theme
Visual customization for the platform experience.Characteristics
- Modifies visual appearance across platform
- Color schemes and typography
- Component styling
- Animation variations
- Accessibility considerations
Use Cases
- Dark mode and light mode themes
- High-contrast accessibility themes
- Brand-specific themes
- Seasonal or event-based themes
- Industry-specific visual styles
- Aesthetic personalization
Development
Themes are created using the Theme Framework:Studio
A curated collection of offerings for specific workflows.Characteristics
- Group of apps, plugins, and agents working together
- Preconfigured settings and permissions
- Customized onboarding flow
- Integrated experience
- Purpose-built for specific workflows
Use Cases
- Content creation suites
- Project management toolkits
- Research workspaces
- Development environments
- Learning and education bundles
- Industry-specific workspaces
Development
Studios are created using the Studio Framework:Integration Patterns
Standalone vs. Integrated
- Standalone offerings provide complete experiences on their own
- Integrated offerings work with other components to enhance functionality
Conversational vs. UI-Driven
- Conversational offerings primarily use natural language interfaces
- UI-Driven offerings provide graphical interfaces for interaction
Tool vs. Experience
- Tool offerings focus on specific tasks and functionality
- Experience offerings create immersive environments
Marketplace Submission
When preparing to submit an offering to the marketplace, developers need to:- Choose the appropriate offering type
- Implement required interfaces and hooks
- Specify permissions with clear purposes
- Define which interface surfaces are supported
- Provide comprehensive documentation
- Submit for review and approval
Best Practices
Choosing the Right Offering Type
- Use an App when building a comprehensive experience with rich UI
- Use a Plugin when extending platform functionality with minimal UI
- Use an Agent when providing domain-specific AI assistance
- Use a Theme when customizing visual appearance
- Use a Studio when curating multiple offerings for specific workflows
Development Guidelines
- Focus on one offering type initially before expanding
- Ensure clear boundaries between different offerings
- Request only the permissions necessary for functionality
- Design for interoperability with other offerings
- Follow platform design guidelines and best practices
Related Concepts
- Vibing Super Agent - Central orchestration system
- Interface Surfaces - UI contexts for offerings
- Permission Model - Security framework for access control
- Unified Memory System - Shared context system