Lifecycle Overview
A Mini App progresses through the following stages:1
Create
Register Mini App and set up project
2
Develop
Build UI, logic, and backend integrations
3
Test
Validate functionality in sandbox
4
Submit
Package and submit for review
5
Review
Rebell reviews for compliance and quality
6
Publish
Release to production users
7
Maintain
Bug fixes, updates, and versioning
Create
The lifecycle begins with the creation of a Mini App project. At this stage:- A new Mini App is registered in the Rebell developer console
- A unique Mini App identifier is assigned
- The Mini App type is selected (Native or H5)
- Basic metadata is defined (name, description, category)
Creation does not make the Mini App visible to users. It only establishes the project container used during development.
Registration Information
| Field | Description | Required |
|---|---|---|
| Mini App Name | Display name in SuperApp | Yes |
| Description | Short description of service | Yes |
| Category | Service category (e.g., Food, Transport) | Yes |
| Mini App Type | Native or H5 | Yes |
| Icon | App icon for display | Yes |
Develop
During development:UI Implementation
Mini App UI and client-side logic are implemented
Backend Integration
Backend APIs are integrated
Navigation
Navigation flows are defined
Payments
Payment triggers are implemented where required
- Local simulator
- Logging and debugging tools
Development Checklist
Core Implementation
Core Implementation
- All pages and components implemented
- Navigation flows working correctly
- Data binding and state management complete
- Error handling implemented
Backend Integration
Backend Integration
- API endpoints connected
- Authentication flow implemented
- Data loading and caching working
- Error states handled
Payment Integration (if applicable)
Payment Integration (if applicable)
- Payment flow triggers implemented
- Payment UI integration complete
- Error and cancellation handling
- Success/failure states displayed
Test
Testing validates that the Mini App behaves correctly before submission.Testing Activities
- Functional Testing
- Backend Integration Testing
- Payment Testing
- Edge Case Testing
- Test all user flows end-to-end
- Validate navigation and transitions
- Test form inputs and validation
- Verify data display and updates
Recommended Test Scenarios
User Scenarios
User Scenarios
- New user first-time experience
- Returning user flow
- User with empty data state
- User with maximum data
Error Scenarios
Error Scenarios
- Network timeout
- API error response
- Invalid data input
- Session expiration
Payment Scenarios (if applicable)
Payment Scenarios (if applicable)
- Successful payment
- User cancels payment
- Payment fails (insufficient funds)
- Network error during payment
Submit
Once development and testing are complete, the Mini App is submitted for review. Submission involves:1
Package
Mini App code is packaged for deployment
2
Select Environment
Choose target environment (typically production)
3
Provide Metadata
Supply required metadata and documentation
4
Submit
Submit package to Rebell for review
Submission Requirements
| Requirement | Description |
|---|---|
| Functionality | All features working as documented |
| Metadata | Complete and accurate app information |
| Screenshots | Screenshots for store listing |
| Privacy Policy | Privacy policy URL (if collecting user data) |
| Test Accounts | Test credentials for reviewers (if needed) |
Review
Rebell performs a review before allowing publication.Review Areas
Compliance
Platform guidelines and policies
Security
Security and data usage practices
Payment Flow
Payment flow correctness
UX Consistency
User experience consistency
Technical Stability
Technical stability and performance
Content
Content appropriateness
Review Outcomes
- Approved
- Rejected
- Mini App is eligible for publication
- No further action required before publishing
- Merchant can choose when to go live
Review timelines and criteria are defined by Rebell and may vary by Mini App category.
Publish
After approval, the Mini App can be published to production. Publishing:- Makes the Mini App available to real users
- Activates production configuration
- Enables live payments
Pre-Publication Checklist
Backend Readiness
Backend Readiness
- Production backend deployed
- Production credentials configured
- Webhook endpoints ready
- Monitoring enabled
Configuration
Configuration
- Production API endpoints configured
- Production credentials active
- Sandbox references removed
Operational Readiness
Operational Readiness
- Support team briefed
- Runbook prepared
- Escalation paths defined
Maintain
After publication, the Mini App enters the maintenance phase. Maintenance includes:Bug Fixes
Address issues reported by users
Feature Enhancements
Add new capabilities
Performance
Optimize performance
Security Updates
Address security issues
Each update:
- Requires a new version
- Follows the same submit → review → publish process
Versioning & Rollback
Mini Apps are versioned explicitly.Versioning Principles
| Principle | Description |
|---|---|
| Version per release | Each release corresponds to a version |
| Multiple internal versions | Multiple versions may exist internally |
| Single active version | Only one version is active for users |
| Immutable releases | Published versions cannot be modified |
Rollback
Rollback is available for risk mitigation:- When to Rollback
- Rollback Process
- Critical bug discovered after release
- Performance degradation in production
- Security vulnerability identified
- Compliance issue detected
Lifecycle Responsibilities
| Stage | Primary Responsibility |
|---|---|
| Create | Merchant |
| Develop | Merchant |
| Test | Merchant |
| Submit | Merchant |
| Review | Rebell |
| Publish | Merchant |
| Maintain | Merchant |