Documentation

Complete guide to working with Mini Maximum

1. What is this

Mini Maximum is a no-code builder for creating mini-apps inside the MAX messenger. You assemble projects from visual screens, configure behavior scenarios, connect data and AI — all in one system without writing code.

Key Facts:

No code required — all interface and logic built in visual constructor
Version control — like Git: change history, rollbacks, project branching
Safe simulations — testing changes before publication without risks
AI with control — automation actions only with your confirmation
Integrations — ability to connect external services and custom solutions

2. Quick Start

Register in Mini Maximum and create a new project
Describe your project idea — the system will suggest a basic structure
Add screens: home, catalog, profile — use ready templates or create from scratch
Configure scenarios: describe navigation logic between screens and user interactions
Connect data: create collections for storing information (products, users, orders)
Run simulation: test the entire app flow in a safe environment
Fix errors if any, and run simulation again
Publish the project — your app becomes available to MAX users

3. Terms and Definitions

Project

Complete mini-app with all screens, scenarios, data and settings. One project = one app in MAX.

Screens

Visual pages of your application. Each screen contains interface elements: buttons, text, images, forms.

Scenarios

Application behavior logic: what happens on button click, how forms are processed, conditions for screen transitions.

Data (collections)

Structured information storage: products, users, orders. Works like a database table.

Versions

Snapshots of project state at a specific moment. Allow rollback to any previous version.

Simulations

Safe mode for testing changes before publication. You see how the app works, but users don't.

Publication

Deployment of the project for real MAX users. After publication, the app becomes available.

4. Versions and Rollbacks

The version system works like Git — every change is recorded and can be undone.

Change History

Each save creates a new version. You can see: who, when, and what changed.

Rollback in Seconds

Found a bug after update? Return to previous version with one click without data loss.

Project Branching

Create parallel versions to test new features without affecting the main branch.

Version Comparison

View changes between versions: what was added, deleted, or modified.

5. Simulations

Safe testing mode before publishing changes.

Pre-publication Checklist:

Run simulation before every publication
Check all main scenarios: registration, checkout, navigation
Check screens on all devices (mobile/desktop)
Ensure forms work correctly and submit data
Test edge cases: empty fields, invalid data formats
Check integrations with external services (if connected)
Ensure AI actions trigger correctly and require confirmation
Fix found errors and run simulation again

6. AI and Manual Review

✓ What AI Does

Suggests project structure based on your description
Generates basic screens and scenarios for typical tasks
Automatically fills data for demonstration
Suggests optimizations and interface improvements
Helps with integrations: suggests APIs and settings

✗ What AI Does NOT Do

Does not publish changes without your confirmation
Does not delete data without explicit permission
Does not change critical security settings automatically
Does not send requests to paid APIs without confirmation
Does not make final decisions — only suggests options

⚠️ Where Manual Confirmation Required

Publishing changes to production
Deleting data collections or screens
Changing payment settings and integrations
Bulk operations with user data
Changing access rights and security
Sending notifications to app users

7. Common Errors and Solutions

❌ Screen not displaying after publication

✓ Solution: Check that screen is added to navigation and has correct URL. Ensure there are no hiding conditions.

❌ Form not submitting data

✓ Solution: Check field bindings to data collection. Ensure all required fields are filled and submission scenario is configured.

❌ Scenario not triggering

✓ Solution: Check trigger conditions. Ensure the trigger (button/event) is correctly linked to the scenario.

❌ Data not saving

✓ Solution: Check collection access permissions. Ensure data structure matches collection schema.

❌ Integration not working

✓ Solution: Check API keys and endpoint URLs. Ensure external service is available and properly configured.

❌ Simulation hangs

✓ Solution: Check scenarios for infinite loops. Simplify logic and try simulating individual parts.

8. Support and Contacts

If you didn't find the answer in documentation, contact us:

Support channel in MAX

Quick answers from team and community

Email support

Detailed consultations and help with integrations

Turnkey build

Full development and launch of app by our team