A one star review on launch day is usually a bug report with a star on it.
Read the words before you look at the star. Most launch day one stars are one of three things: something is broken, something is missing, or somebody is angry about money. Only the first is urgent, and it belongs in your crash reports rather than in a reply. You cannot delete the review. You get one public reply per review on both stores, you can edit it later, and the customer is told you answered and can change their review in response. Everything below comes from App Store Connect Help and Play Console Help, read on 16 October 2026, because the first hour after a bad review is the worst time to be guessing at what each store allows.
What follows is how to triage the review, how replying works on each store and how long it takes to show, what Google forbids you from saying, and the one lever Apple gives you over the rating itself. It is irreversible, so it is worth understanding before you reach for it.
Start with the triageThe short version
Fix the thing, reply once, then stop looking at it.
One rating on day one is a sample of one. It feels enormous because it is the whole of your rating so far, which is an arithmetic problem that solves itself as more people rate the app. The part that does not solve itself is whatever the review describes. If it says the app closes on open, that is a fact about your build and it is costing you every install after it.
So the order is: read it, check your crash reports, fix the bug if there is one, reply once in plain words, and go back to work. A launch day review is a cost of running a live app, like the server bill and the yearly developer fee. Worth knowing what an app costs to maintain before launch day, so none of this arrives as a surprise.
What should you do first when the review lands?
Separate the rating from the report. The rating is a number you do not control. The report is information, and on launch day it is often the only information you have, because almost nobody has your app yet and the people who do are not filling in bug trackers. A customer saying it closes straight away is a tester doing you a favour in the rudest possible format.
So check it before you believe it, and before you dismiss it. Open your crash reports for the version the review names and see whether anyone else hit the same thing. A single unreproducible complaint and a crash showing up on a tenth of sessions are the same one star on the store and completely different problems in your week. The work of debugging a crash from a store report starts with matching the device and the version, not with the review text.
It helps to know how much the number itself will move. Google says the rating users see on Google Play is weighted towards more recent ratings, so that it reflects the changes and updates you make, and that it is calculated from your most recent ratings. Your lifetime average since launch is a separate figure inside Play Console. On the App Store, ratings are shown for each country or region, and the country attached to a rating reflects where that customer first got the app. Apple documents no recency weighting at all.
Practically, that means a bad first rating on Google Play is a fading problem and a bad first rating on the App Store is a persistent one. Both get better the same way, which is more people rating the app, and neither gets better by arguing with the person who left it.
Play Console Help, ratings and reviews in Play Console, read 16 October 2026
Read it first
What does the review actually say?
Pick the closest one. The star rating is the same in every case. What you should do about it is not.
This is a bug report that happens to carry a star rating.
What to do: Reproduce it before you answer. Check your crash reports for the version named in the review, fix it, ship it, then reply saying which version fixes it.
The rating: Nothing to report. A true statement about your app is not a policy breach on either store.
A guide to what each store documents, not a ruling on your review.
How do you reply on the App Store, and when does it show?
In App Store Connect, open Apps and select the app, click Ratings and Reviews in the sidebar, pick the platform from the top right, find the review and click Reply next to it. You type into the dialog and click Submit. You need the Account Holder, Admin or Customer Support role, and somebody whose only role is Customer Support is taken straight to Ratings and Reviews after choosing an app, which is a sensible way to let a support person answer reviews without giving them the rest of the account.
Three details save a panic. Only one response per review appears on your product page, so there is no thread to win. Responses may take up to 24 hours to appear on the App Store, and until then they show as pending in App Store Connect, which means the silence after you hit Submit is normal. And you can edit or delete your response at any time, through Edit Response next to the review, without being the person who wrote it. Edited responses carry a notation saying they have been edited, so a quiet rewrite is not available to you.
The reason to reply at all is in Apple's own overview of ratings and reviews: when you respond, the customer is notified and can update their review in response. That is the whole return on the exercise. Not the people reading your product page, one of whom might notice, but the one person who can change the thing you mind about. If you make several edits in a short time, to fix a typo for instance, Apple says the customer gets only one notification.
Which makes the shape of a good reply obvious. Name the problem in their words so they can see you read it. Say what you changed or when you will. Give them one way to reach you. Leave out the marketing, leave out your reasons, and leave out any detail about their account, because this is a public page. A reply that reads like a person fixing something gets reviews updated. A reply that reads like a press release gets screenshotted.
App Store Connect Help, respond to reviews, read 16 October 2026
What are Google Play's rules for a developer reply?
Stricter than most people expect, and written down. You get one public reply for each user review, from the Reviews page in Play Console, under Ratings and reviews. Google tells you to make sure you have the Reply to reviews permission, so check that before launch day rather than during it. You can edit your reply at any time. There is also a Reply to Reviews API if you want this inside your own tooling, with quotas, and a form for asking for a higher one.
The reply reaches the person directly. Google says that after you reply the user gets a push notification and an email, and that the email contains your app name, the date of the review, their rating and review, your reply, and a link to contact you using the contact email on your store listing. So the contact email on your listing is now a support channel whether you meant it to be or not. Point it somewhere a human reads.
Then the policy. Google asks you to address the comment directly, clearly and truthfully. It forbids content that is abusive, hateful, dismissive, threatening or harassing, and asks you not to engage with inappropriate comments at all. It forbids soliciting and promoting. It forbids sexually explicit content and profanity. And it says in as many words that replying is a privilege and not a right, with suspension of the app or the developer account as the consequence. Dismissive is the word to sit with: a reply that amounts to "it works fine for everyone else" is a policy problem, not just a bad look.
Google also offers suggested replies, but narrowly. They appear only for recent English language reviews with Play Console set to English, never for a review you have already answered, and only once you have saved a phone number, an email address or a website on your account details. Useful for the twentieth polite thank you. Not for the review that matters.
Play Console Help, reply to reviews and the comment posting policy, read 16 October 2026
Can you get the review or the rating taken down?
The review, no. Neither store documents a way for a developer to delete a customer review. What Apple gives you is Report a Concern, next to the review in Ratings and Reviews, where you choose a concern from a menu, describe it and submit. Apple says the customer who wrote the review is not notified that you reported a concern. On a device running iOS 18.4 or later you can also tap and hold the reviews summary on the App Store to report a concern about the summary itself. Google has its own route for reporting a review that breaks the comment posting policy. Both are reports. Neither is a delete button, and neither is for a review that is merely unfair.
The rating is different, and only on the App Store. When you release a new version you can choose to reset your overview rating. You tick Reset rating when this version is released, in the Reset Overview Rating section of that version, and it takes effect when the version goes live. It needs the Admin or App Manager role. Read the small print before you use it. It affects all regions and countries simultaneously. Once the new version is released you cannot restore the previous rating. It does not apply to written customer reviews, which carry on displaying, so the one star text stays and only the number goes. Your product page shows a message saying the rating was recently reset until enough people have rated the new version, and you can see the reset date in the Distribution tab under Ratings and Reviews. For a universal app it applies only to the platform version you reset it for, and app bundle ratings cannot be reset at all.
So it is a real tool and a bad first move. Burning it on day two costs you the lever you will want in six months, when you have fixed the thing the early reviews were about and have an app worth re-rating. It is also no use at all against the review text, which is usually the part that is actually putting people off.
Two escape routes people reach for and should not. Starting a fresh app record does lose the rating, along with your downloads, your install base, your ranking history and your product page URL, and it leaves everyone who already installed the app without updates. Moving the app elsewhere does not work either: Apple says that during and after an app transfer the app retains its reviews and ratings, so transferring an app to another account moves the record and the history together. The better defence is earlier: on Android, shipping through a staged rollout on Google Play means a launch day crash reaches a slice of your users instead of all of them, and you can stop it before the rest arrive.
App Store Connect Help, monitor ratings and reviews, read 16 October 2026
The same reply, handled differently by each store
| What you want to know | App Store | Google Play |
|---|---|---|
| Where you reply | App Store Connect, Ratings and Reviews in the app sidebar | Play Console, Ratings and reviews, then Reviews |
| Public replies per review | One | One |
| Editing the reply afterwards | Yes | Yes |
| The customer hears about it | Notified, and can update their review | A push notification and an email containing your reply |
| How long before it is public | Up to 24 hours, pending until then | No figure documented |
| Headline rating leans on recent ratings | No weighting documented | Yes |
| Resetting the overall rating | At a new version, every region at once, not reversible | No equivalent documented |
| Who is allowed to reply | Account Holder, Admin or Customer Support | Anyone with the Reply to reviews permission |
Read from App Store Connect Help and Play Console Help on 16 October 2026. Where a row says nothing is documented, that means the store does not publish a figure, not that the answer is no.
Where this lands if a builder generated your app
It lands on you, and the account is already in your name. App Store Review Guideline 4.2.6 says apps created from a commercialized template or app generation service are rejected unless they are submitted directly by the provider of the app's content. That is why Newly uploads an iOS build to TestFlight and leaves the submission to you. The reply box, the roles, the Report a Concern menu and the rating reset are all in your App Store Connect account, not a vendor's, which is the right way round the day a review needs answering.
Newly is an AI app builder. You describe an app in plain English and it writes a real React Native and Expo project that you own. It uploads iOS builds to TestFlight, publishes to Google Play internal testing, builds a standalone Android APK, and keeps two way GitHub sync so the code is never trapped. It is $25 a month and there is no free tier. The part that matters on launch day is the GitHub sync: a crash named in a review is a change in a repo you control, which you can fix in the builder or by hand.
The honest limit is that no builder shortens this loop much. Finding the crash, shipping a build, waiting for review and getting the version out still takes what it takes on each store. What generation changes is the hours between understanding the bug and having a build, not the hours after. Write the reply while you wait. It is the only part of the day that is entirely up to you.
Questions people ask after a bad launch day review
No. Neither store documents a way for a developer to delete a customer review. Apple lets you report a concern on a review you find offensive or inappropriate, and says the customer who wrote it is not notified that you reported it. Google Play lets you report a review that breaks its comment posting policy. Both are reports, not deletions, and somebody being harsh about your app is not a policy breach. What you can delete is your own reply.
Ship the fix, then answer the review
The review you can answer in ten minutes. The bug is the real work, and it is the only thing that changes the next twenty ratings.
Start building