Out of curiosity, I went through posts the other day and counted the number of App Review complaints in a single day. I found 17, but it seemed like that was a slow day with numerous actual technical posts.
I just repeated the exercise and found 32. I'm not sure about my methodology at the edge. The forum doesn't have real, absolute timestamps. A timestamp of "23h" is definitely in range, but I'm not sure about "1d". And the forum list is limited to 10 pages. So the actual 24-hour count number this morning could be more or less than 32.
I'm probably not going to repeat the exercise. I'll just assume the average is 24 per day and leave it at that. I'm not claiming this is a good thing or a bad thing. I simply find it morbidly fascinating.
Qualitatively, the results are equally creepy. The posts seem to follow a template. They virtually always feature:
- A call for input to ask if anyone else has ever experienced anything similar, as if the past 8 months haven't happened. But perhaps this is just the modern approach - speak your truth first, read or listen to others later, if at all.
- A request for guidance from other developers for escalation strategies.
- A plea to the Apple gods for intervention or confirmation of properly queued status.
Engagement seems unproductive.
More concerning for other developers is a common practice of automatically requesting an expedited review. Not every post includes this, but virtually every post that involves a rejection says that a subsequent submission was expedited. I don't think I've ever requested an expedited review. It doesn't sound like a good idea in this age of AI-supported App Review. If there's a rejection model in training, it seems like expedited review status would be a significant input.
I noticed a recent attempt to bump some Apple posts pointing to App Review tips. I'm not sure such bumps are effective. For one thing, they're already on page 9. Who's looking at page 9 other than me? It would be better if they were truly pinned following common practice in other forums. And obviously none of these posters are reading any previous posts before making their own. They sometimes do some after-the-fact forum research and add a few "me too" replies.
On a more humourous note, it's telling that there is an assumption in this community that people recognize rejection reasons by App Review Guideline paragraph number. I'm starting to learn those myself from reading these posts. That's a clear signal to change my own behaviour, which is ultimately all I can do.
My plea to the Apple gods would involve some support for that endeavour in the form of forum updates to 1) better serve these hapless developers and 2) allow other developers to ignore them. For example, the Apple Support Community, apparently based on the same back-end discussion forum engine, has the ability to allow users to subscribe to specific communities. I don't see any way to do that here. I would sure like to be able to exclude both "App Store Distribution & Marketing" and "App Review" from any such subscription list. (And maybe SwiftUI too. đ )
I have other suggestions regarding comments, notifications, and update indications. But the current poor state of forums would overwhelm any such minor improvements.
Sorry it took me so long to reply here. Itâs been a hectic week.
Lemme start out with some sort of semi-official answer:
- Yes, we recognise that this situation is less than ideal and weâre working on ways to improve things (r. 190253666).
- I have no details as to what thatâll be, or any sort of timeline to share.
Oh, and thanks for all the work youâve put into answering questions on the forums over the years.
And with that out of the way, I want to give you my own thoughts about two aspects of this:
- What should this look like?
- What do you do right now?
Regarding the first, my take on this is that the forums are primarily a place to help folks with Apple APIs and tools. These are things that we can discuss in public, and having that discussion in public is beneficial for everyone involved.
However, there is a set of things that we simply canât handle here on the forums. For example, if you have a problem with your programme enrolment, fixing that will likely require a bunch of private info, which isnât appropriate for these public forums.
There are existing support channels for these things [1], including:
- DTS Code-Level Support Requests
- App Review
- App Store Connect support
- Developer Program Support
So, I see this as a problem of getting folks started on the right path. To continue the programme enrolment example, Iâd like to see folks with those questions encouraged to contact DevPrograms rather than posting here on the forums.
And Iâm using the word encouraged deliberately. If someone is really committed to talking about enrolment issues in public, thatâs fine by me, as long as they recognise that they wonât get formal support.
[1] Thereâs also Apple Support Community, for public discussions of user-focused stuff.
My second point is about what you can do right now. I agree that itâs not much fun wading through all of those threads looking to find technical questions to answer. I donât have a complete solution to that, but I can explain how I use the forums.
I never look at the All Posts view. Even back in the day, it always contained stuff thatâs way outside of my wheelhouse. I mean, I know as much about SwiftUI as the next network/thread/file system engineer, which is not a lot [1]. So, Iâve never tried sifting through the full list of threads to find questions to answer
Rather, I rely exclusively on subtopic and tags. I have a long list of subtopics and tags that I monitor, and I use that to build my list of questions to answer.
The way I do that is weird â itâs old, and itâs very specific to my setup â so Iâm not going to go into those details. Rather, I encourage folks to:
- Use RSS feeds to learn about new threads.
- Watch threads to learn about updates.
The latter is easy:
- When you find a thread youâre interested in, click the watch (bell) icon.
- Bookmark the Watching tab and go there when you want to catch up.
To learn about new threads, plug the forums RSS feeds into your RSS reader of choice. Every topic, subtopic, and tag page has such a feed.
This will yield duplicates, because a thread might have multiple tags that youâre watching, but you can de-dup based on the thread URL.
Now, this isnât perfect:
- Some folks donât set their subtopic and tags appropriately, so you might miss a question you wouldâve answered otherwise.
- Some folks apply incorrect tags, so you might see a thread thatâs not what youâre looking for [2].
Both of these are annoying, but hardly the end of the world.
[1] My SwiftUI apps typically have a single Test button that runs my test code (-:
[2] When I see those, I fix the subtopic and tags, but thatâs not an option for most folks.
Share and Enjoy
â
Quinn âThe Eskimo!â @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"