Best practices for product exit criteria from beta to public availability?

I am Head of Marketing at Global AI Platform's US office in Silicon Valley, working on GTM for our app's US public availability launch this Summer'25. We’re in the final stages of beta testing our mobile app (focused on meal and weekend planning), and we want to be intentional and avoid rushing just because we feel ready.

We’re working on defining exit criteria—the metrics, signals, and checkboxes that say:

“Yes, it’s time to move from beta to full release.”

Here’s what we’re considering so far:

• Core flows are stable and bug-free (onboarding, meal planning, etc.)

• Day 1 and Day 3 retention are within target ranges

• Feedback from beta users has shifted from bugs to feature suggestions

• App store assets and support content are ready

• Analytics and error tracking are fully in place

I’d love to learn from those of you who’ve done this before:

• What signs or metrics did you use to know your product was ready to exit beta?

• Did you regret launching too soon—or too late?

• Any specific frameworks, scorecards, or gut checks you use before deciding?

Would really appreciate any wisdom, frameworks, or even hard lessons learned. Thank you!