Feedback on Marketplace Update Review Workflow
K
Kaleem Mohammed
Hi Framer Review Team,
I wanted to share some feedback from our recent experience updating one of our live Marketplace components.
When an update to an already-approved component encounters compliance issues during review, the existing live component appears to become unavailable until those issues are resolved.
I believe this creates an unnecessary problem for both publishers and Framer users.
If the currently published version has already passed review and is live, it may be better for that approved version to remain available while only the new update is held for review. Once the updated version passes compliance, it could then replace the existing release.
This would provide a simple last-approved-version workflow:
Live approved version → remains available
New update → reviewed separately
Approved update → replaces live version
From a user perspective, this avoids situations where a component they recently discovered suddenly disappears from the Marketplace. From a publisher perspective, it also makes iterative improvements much safer without risking interruption to an established listing.
Another useful option could be a pre-publish compliance check or staging environment, allowing publishers to validate an update against Marketplace requirements before submitting it to replace a live release.
I appreciate the quality standards Framer maintains for Marketplace components. My suggestion is simply to separate release availability from update approval, so compliance reviews can continue without disrupting an already-approved product.
I hope this is useful feedback for the Marketplace team.
Log In