@haerryrs For 5 days in London the thing to check is which network the plan actually rides on, EE, Vodafone or Three, since coverage on the Tube differs a lot. Also read what "unlimited" throttles to after the daily cap, and whether hotspot is included. I run a small travel eSIM shop.
@DanKlepar The permission ones are the easy half — you change the copy and they pass. Budget for a second round anyway. One of ours cleared the flagged screen and got pulled up on a different permission prompt we had not touched, so it went back twice for what looked like a one-line fix.
Added IT/RU/TR localizations to FlipSay 3 weeks ago. Search impressions went 2,821 → 4,872 → 7,062 over the last 3 days. Organic downloads 87 → 125 → 146. App store locale coverage is free distribution — the algorithm rewards it immediately.
@storiesofalan 24% is healthy, so I'd watch a different number. We raised annual $29.99 to $39.99 and trial-to-paid held fine, but trial STARTS halved, 21/mo to 6/mo, installs flat. Took weeks to spot because the metric we were grading looked good the whole time.
@Meffysto69 Check cost-per-tap early. Mine cleared at 2.00 to 2.57 a tap, above my whole CPI target, so even perfect tap-to-install lost money. Lower bids won no impressions. The auction floor decided it.
@nestor__studio It can hold up. One of mine is sitting at 5.6% and impressions grew to 8,218 with the rate not moving. Another one gets 5,313 impressions at 0.6%. Same store, same developer. The difference came down to intent: whether the keyword actually matched what the app does.
@timopowerz B, learned the expensive way. Three paywall experiments, all inconclusive. The paywall unmounted before rendering, so 23 people finished onboarding and none saw it. We optimised a screen nobody reached.
@whysumancode Localization is the cheapest option. I added Italian, Russian and Turkish listings to a small party game 3 weeks ago, didn't change anything else. Search impressions went from 2,821 to 7,062 in three days, organic downloads went from 87 to 146. The listing was the bottleneck.
@fizzibitz The disclosure is locked to monthly. It says "then $4.99/month" but you can pick Yearly at $44.99. If you pick yearly, the price by the button is wrong. That's the 3.1.2 mismatch. Just make that line match whatever you select.
@LucaCaponeX Same trap, just one layer deeper: it audits your UI copy as well.
We got hit with 5.1.1(iv) because a permission button said "Enable". It had to say "Continue". Your copy is part of the review surface.
@luongnv89 Worth splitting that complaint into two things: "too expensive" and "I hit the wall before I got it" need opposite fixes.
We had a paywall at 46 views, 11 taps, 0 purchases. Looked like pricing. But the StoreKit product never loaded, so the sheet never appeared.
@theappswelove@pcshipp Rank and downloads are two different things. One of ours pulls 5,778 impressions and only 7 downloads. Another one gets 1,200 impressions and 123 downloads. Same store, same account. So the first one ranks fine, it's just that the listing doesn't convert once people get there.
@SamuelPremji@danyxzb We checked ours: 11 of 11 submissions got removed, across three subs, for three different reasons. Spam filter, mod rules, a 100-karma automod gate. Comments were fine and scored fine. Posting is the lane that's shut, not Reddit.
@marklau6 Yeah, queues are mostly separate, that part I agree with. The exception is account-level rulings. We had 7 apps get rejected in the same minute under 4.3(a), and two of them had never been rejected before. Same scaffolding, same onboarding shape.
@arthurain About "which guideline", the email never includes it, and the ASC API doesn't either. We burned two days thinking Apple had gone silent. It only shows up in Resolution Center, and the number tells you whether it's the frame or the copy.
@SauregurkeDEV ASC's API is full of this stuff. There's a field in the web UI, it's not in the API at all, and you get a generic rejection instead of an unsupported error. So you waste an hour just trying to show your request wasn't the problem.
@Joey_Walker82 Localised metadata is the sneaky one. The build goes through fine, no warnings at all. We got rejected because of a permission button label that only read wrong in a single locale.
@heyChrisUX Hit us on two apps the same week. It matches structure, not keywords, so renaming symbols does nothing. We diffed our own apps: 100 shared type names, 51 identical filenames, same folder layout. Rebuilt one properly, got it to zero.