Applications and Schemas

Understand how Appivo applications are structured

Applications and Schemas

Every Appivo application is built on a Schema - the complete blueprint that defines your application's structure and behavior.

What is a Schema?

A Schema is the comprehensive definition of your application. Think of it as the master blueprint containing:

  • Models - Your data structures (database tables)
  • User Interfaces - All screens and views
  • Rules - Automated triggers and business logic
  • Actions - Operations that execute when rules trigger
  • Security Settings - Roles, permissions, and access control
  • Features - Enabled capabilities and configurations

Every application has exactly one schema that defines everything about how it works.

Creating an Application

Start a New Application

  1. Click Create New Application in the Application Builder
  2. Choose your starting point:
    • Template - Start with a pre-built application
    • From Scratch - Begin with an empty schema
  3. Name your application
  4. Select target platforms (Desktop, Mobile, or both)
  5. Choose initial features to enable
  6. Click Create

Application Settings

After creation, configure your application:

SettingDescription
NameDisplay name for your application
DescriptionBrief description of purpose
PlatformsDesktop, Mobile, Public
Default LanguagePrimary language
FeaturesEnabled capabilities

User Interfaces

Your application can have multiple user interfaces, each optimized for different purposes:

Desktop UI

The primary interface for web browsers on computers. Designed for:

  • Complex forms and data entry
  • Full-featured dashboards
  • Administrative functions

Mobile UI

Touch-optimized interface for smartphones and tablets. Features:

  • Mobile-specific widgets (MButton, MTextField, etc.)
  • Touch gestures and interactions
  • Compact layouts for small screens

Public UI

Interface for unauthenticated users. Typically used for:

  • Landing pages
  • Self-service portals
  • Public forms and submissions

Multiple Views

Each UI can contain multiple views (screens):

  • List views for displaying data
  • Form views for data entry
  • Detail views for read-only display
  • Dashboard views for visualizations
  • Custom views for specific purposes

Features and Configuration

Platform Features

Every Appivo application includes these core features:

FeatureDescription
LocalizationMulti-language support for 8 languages
IntegrationsConnect to external systems
AuthenticationUser login and security
BrandingCustomize look and feel
Multi-TenancyServe multiple customers

Custom Features

You can create application-specific features that can be enabled or disabled:

Feature: Advanced Reporting
Description: Detailed analytics and custom reports
Status: Can be enabled/disabled per tenant

Configuration Levels

Configuration can be set at multiple levels:

  1. Application Level - Default settings for all users
  2. Tenant Level - Customer-specific settings
  3. User Level - Individual preferences

Environments

Appivo supports multiple environments for your application:

EnvironmentPurpose
DEVELOPMENTBuilding and testing new features
QAQuality assurance testing
PRODUCTIONLive application for end users
LABExperimental features and prototypes
LOCALLocal development (if applicable)

Environment Configuration

Each environment can have:

  • Different configuration values
  • Separate databases
  • Unique integration settings
  • Environment-specific features

Version Management

Appivo tracks all changes to your application:

  • Version History - See all previous versions
  • Rollback - Revert to a previous version if needed
  • Comparison - View differences between versions
  • Deployment - Deploy specific versions to environments

Deployment

Deploying to Production

  1. Complete testing in preview mode
  2. Review all configuration settings
  3. Verify security and permissions
  4. Click Deploy to Production
  5. Monitor the deployment status

Deployment Checklist

Before deploying, verify:

  • All features work correctly
  • Data validations are in place
  • Security roles are configured
  • Integrations are tested
  • Mobile UI is responsive (if applicable)
  • Localization is complete (if multi-language)

Best Practices

Planning

  • Plan your data models before building
  • Sketch out user interfaces on paper first
  • Define security requirements early
  • Identify integration needs upfront

Organization

  • Use clear, descriptive names for views
  • Group related views logically
  • Document complex business logic
  • Keep the schema organized as it grows

Testing

  • Test in preview mode regularly
  • Test with different user roles
  • Verify all workflows end-to-end
  • Test on target devices for mobile apps

Next Steps