1 Create Release

The Bubl Developer Store release process consists of two main forms that need to be completed. This guide will walk you through each step to ensure a successful app submission.

The release process involves:

1. Release Information Form - Technical details about your app
2. Developer Information Form - Your developer profile information

Enter your app version using semantic versioning format:

• Format: v0.0.1, v1.2.3, etc.
• Example: v1.0.0 for initial release
• Follow semantic versioning principles (major.minor.patch)

Provide a detailed description of this version:

• Describe new features
• List bug fixes
• Mention performance improvements
• Include breaking changes if any
• Keep it concise but informative

Select “Yes” if your application includes:

• Frontend components
• Web interface
• User-facing GUI
• Any visual elements users interact with

Select “Yes” if your application provides:

• Backend services
• REST APIs
• GraphQL endpoints
• Any server-side functionality

Select “Yes” if your app requires:

• Google Calendar Api
• Intraction with any 3rd party api

Select “Yes” if your app needs:

• Access to Bubl controller features
• Integration with Bubl services
• Bubl system-level permissions

When you select “Yes” for Bubl permissions, you’ll see additional options:

Choose the appropriate permission category:

• Profile - User profile access
• Energy - Energy related data permissions
• Health - Health related data permissions
• Payment - Access for bubl payment system

Select the required access level:

• 1 - 1 level access
• 2 - 2 level access
• 3 - 3 level access
• 4 - 4 level access
• 5 - 5 level access

Check “Optional” if:

• The permission enhances functionality but isn’t required
• Your app can function without this permission
• Users should be able to deny this permission

Select your application type:

• 0 - 0 type
• 1 - 1 type
• 2 - 2 type
• 3 - 3 type
• 4 - 4 type

Upload your backend executable:

• Supported formats: .zip, .tar.gz etc.
• Requirements: Ensure compatibility with Bubl runtime
• Size limit: Check current file size restrictions
• Testing: Verify the executable works in Bubl environment

Upload your frontend build:

• Supported formats: .zip, .tar.gz containing static files
• Contents: HTML, CSS, JavaScript, images, etc.
• Structure: Ensure proper file organization
• Build: Use production-optimized builds

All fields in this form are automatically prefilled based on your previous releases, but can be updated if needed.

• Purpose: Displayed publicly on the app store
• Example: “John Doe” or “Acme Software Solutions”
• Note: This appears as the app publisher

• Purpose: Contact information for users and Bubl team
• Format: Complete physical address
• Privacy: May be displayed publicly depending on store policies

• Purpose: Primary contact for support and communications
• Requirements: Valid, monitored email address
• Usage: User support, Bubl notifications, updates

• Purpose: Secondary contact method
• Format: Include country code if applicable
• Usage: Emergency contact, verification purposes

• Test thoroughly in Bubl environment
• Verify file integrity of uploads
• Review permissions - only request what’s necessary
• Prepare release notes with clear, user-friendly language

• Minimize permissions to reduce security risks
• Document permission usage in your release description
• Test with minimal permissions first
• Consider user privacy when requesting external permissions

• Follow semantic versioning for consistency
• Maintain changelog for all versions
• Plan release schedule for regular updates
• Test backwards compatibility when possible

• Check file size limits
• Verify file format compatibility
• Ensure stable internet connection
• Try compressed formats for large files

• Review permission requests - remove unnecessary ones
• Provide clear justification in release description
• Test with alternative approaches that require fewer permissions
• Contact Bubl support if permissions seem incorrectly denied

• Complete all required fields before submission
• Use proper version format (v1.2.3)
• Ensure email format is valid
• Check file upload completion

1. Complete Release Information Form with all technical details
2. Review and update Developer Information if needed
3. Double-check all uploads and form data
4. Submit for review by Bubl team
5. Monitor submission status through developer dashboard
6. Respond to review feedback if requested
7. Celebrate your app launch once approved!