Releases

Releases give you version control over your widgets and notifications. This guide covers the full release lifecycle.

What Is a Release?

A release is a versioned snapshot of your app's widgets and notification templates. It includes:

• Version (e.g., 1.0.0)
• Name and description
• Logo and category
• A set of widgets
• A set of notification templates

Release Lifecycle

Every release follows this progression:

Draft → Testing → Review → Live → Archived

Draft

Your working state. In draft, you can freely:

• Add, edit, and remove widgets
• Create and modify notification templates
• Update release metadata (name, description, logo)

Testing

Move a release to testing when you're ready for real-device validation.

• Testers (invited users) can see and interact with the release
• You can still observe behavior but cannot edit widgets/templates
• If you need changes, pull the release back to Draft

One test at a time

Only one release per app can be in Testing status at a time. This prevents confusion about which version testers are seeing.

Review

Submit your release for review by the NativeSuite team before going public.

• The review ensures quality and compliance
• You'll be notified when the review is complete
• If rejected, the release returns to Draft with feedback

Live

The public-facing version of your app.

• All users who've installed your app see this release's widgets
• Only one release per app can be Live at a time
• Publishing a new release automatically archives the previous Live release

Archived

Retired releases. They're kept for history but no longer served to users.

Creating a Release

1. Navigate to Releases → Create Release
2. Fill in:
   • Version — Semantic version (e.g., 1.0.0, 2.1.0)
   • Name — Human-readable name (e.g., "Launch Release")
   • Description — What's included in this version
   • Logo — Upload an image for this release
   • Category — Choose a category for discoverability

Moving Between States

From the release detail page, use the action buttons:

Current State	Available Actions
Draft	Start Testing
Testing	Submit for Review, Pull Back to Draft
Review	Waiting for NativeSuite team
Approved	Publish to make Live
Live	Will be archived when next release goes live

Iterating Safely

The release system lets you work on the next version without disrupting the current one:

1. v1.0.0 is Live — users see it
2. Create v2.0.0 — it starts as Draft
3. Add new widgets, modify templates in v2.0.0
4. Move v2.0.0 to Testing — testers validate it
5. Submit v2.0.0 for Review
6. Publish v2.0.0 — it becomes Live, v1.0.0 is archived

At no point are live users affected by your in-progress work.

Best Practices

• Use semantic versioning — Major changes get a major version bump
• Write descriptive release notes — Help testers and reviewers understand what changed
• Test on both platforms — Widgets render differently on iOS and Android
• Don't rush past Testing — Real-device testing catches issues that preview can't