Skip to main content

Approval

To list your app on the Grigora App Store, you submit it for review. The Grigora team reviews your app and either approves or rejects it. Once approved, the app is live and users can install it.

How approval works​

  1. Submit — Complete the Store Listing (description, features, at least 2 media items, all required URLs). From your app in the Developer Portal, click Submit for Review. For an already-approved app, save your changes first (they’re stored as a draft), then submit an update and choose a version bump (major, minor, or patch) and an optional changelog.

  2. Under review — Your app’s status becomes Under Review. You can’t edit the store listing or submit again until the request is resolved. To cancel, click Unsubmit to withdraw the request.

  3. Decision — The team reviews your app and either approves or rejects it. You are notified by email (see below).

  4. After approval — The app appears in the Grigora App Store and users can install it. You can keep editing; changes stay as a draft until you submit another update for review.

  5. After rejection — You receive an email with feedback. Fix the issues, update the listing or app as needed, and submit again.

You will receive an email​

When the review is complete, you will receive an email at the address associated with your Grigora Developer account:

  • Approved — The email confirms that your app is approved and live in the marketplace.
  • Rejected — The email explains that the app was rejected and includes feedback from the review team so you know what to change. For a rejected update, the email explains that the update was not approved and what to address before resubmitting.

Check your inbox (and spam folder) so you don’t miss the decision. Use the feedback in rejection emails to fix issues and resubmit.

Best practices​

  • Complete the store listing — Fill in long description, key features, at least 2 media items, and all required URLs before submitting. Incomplete listings are rejected or blocked at submit.
  • Clear description — Explain what your app does, who it’s for, and how it works. Avoid vague or placeholder text.
  • Working links — Ensure documentation, support, privacy policy, and terms URLs open and are relevant. Broken or wrong links slow down review.
  • Honest scopes — Request only the OAuth scopes you need. Over-requesting can lead to rejection or extra questions.
  • Changelog for updates — When submitting an update, write a short changelog so reviewers (and users) know what changed.
  • Respond to feedback — If you’re rejected, address the points in the email and resubmit. If something is unclear, use your support or contact channel to ask.

Visual presentation​

How your app looks in the store affects both review and installs. Follow these guidelines:

  • App icon — Use a clear, recognizable icon (set in Settings). Avoid text that’s unreadable at small sizes or low resolution.
  • Screenshots and media — Use at least 2 strong images or videos. Show the app in action, the dashboard, or key features. High-quality, relevant media help reviewers and users understand the app quickly.
  • Consistent branding — Name, tagline, and description should match what the app actually does. Mismatches can cause confusion or rejection.
  • Preview in the portal — Use the Marketplace Preview on the Store Listing tab to see how the listing will appear. Fix layout, order, and text before you submit.

Taking care of the store listing and visuals reduces the chance of rejection and helps your app stand out once it’s live.