Maintain a published product

Keep the source and assets for each release, tell customers what changed, and give them a way to report a problem. An update is ready when it works in the environment you offer it for, including saved settings and required content.

Preserve a known version

Keep the editable source and assets behind each release. Describe changes in terms customers understand: a control behaves differently, a preset was added or a host issue was fixed.

Test saved settings and required content in the intended destination. A new browser version does not update an installed plugin automatically; use the delivery mechanism actually offered for that release.

Keep the offer accurate

State which version, formats and content a customer receives, and where updates appear. Future major versions, support plans and online services may have different terms. Link to the current offer instead of promising all future development.

See publishing plugins for release preparation and purchases and downloads for the customer's account path.

Maintain connected features

If your product generates new sounds, players also depend on their account access and the generation service. Plan behavior for service interruptions and explain how users keep sounds they have already saved.

If you change app permissions, admission or availability, review the effect on existing users. Creator apps and generation in your products describe those dependencies.

Learn from support

Collect the product version, host, operating system and the smallest steps that reproduce a problem. Use creator reporting to identify stages worth improving, then pair the numbers with musical feedback.

For retiring a product or changing a paid service, contact Maru to agree customer communication, existing access and delivery responsibilities before making the change.