Well, I'm currently sitting at a 4 day wait for a BETA app review of a macOS app. On iOS, it typically takes less than a day.
Same with incremental releases on the same version: it takes so much longer on macOS than iOS.
We go through a lot of effort to make our apps work well across Apple's platforms, you should too.
Make the sandbox accounts actually useful: give us some control over team accounts.
As a simple example, give us a way to reset purchases for a user on TestFlight. Once someone has purchased a non-consumable (lifetime subscription) they can never see the subscription screens. We have a designer that made this mistake years ago and has never seen his designs on device because of that errant purchase.
If this is limited to App Store Connect Users, that's fine (preferable, in fact). It's something that the team needs to test, not customers.
The StoreKit debugger in Xcode is awesome. Something like that hooked up to TestFlight would be equally as awesome.
Replying to feedback is a mailto: link. That sucks, because you don't have any context. You have to copy and paste a shitload of information from the feedback to start a conversation. And some of that information, such as screenshots, is a pain in the ass to collect.
Why can't we reply in the place where the feedback is being reported?
First, let us include < (less-than) and > (greater-than) as a part of an app description. While you're at it, you might want to look at what happens when you put an ampersand, "amp", and a semicolon in a description (that's "&" which may not display here correctly either.
It wouldn't kill you to allow Block 209 (Emoticons) in app descriptions either. Everyone loves Emoji - developers and customers alike. Block 68 (General Punctuation) is not enough.
We've also run into cases recently where 4,000 characters for "What's New" has not been enough. For people who use this as a way to communicate details to customers, extending that would be helpful. Rt now we hv to abbr more thn we'd like to.
Here's a thing: managing thousands of folks in a large TestFlight group is incredibly painful because you have to work with one person at a time. You can find a group of people with search terms, but there are no bulk operations to work on that collection of folks.
Here's an example we recently had to deal with: people who signed up on our mailing list using Apple Private Relay addresses. The TestFlight emails would bounce because the email was being sent from your domain, not our domain (where the emails were collected).
It was easy to find the problematic emails, but updating them in bulk wasn't possible (you can import with a CSV, but not update in a similar way).
There is also no way for us to communicate folks in bulk. We can filter to find a group of folks that might be affected by a change, but have no way to contact them.
Also, knowing that someone has installed an app isn't really that useful. What would be better to know if that someone has installed it recently. I'd love to delete all the people who installed 1.0 now that we're on version 1.3 (a year later).
This feels like a thing where it was designed and tested for a TestFlight group with dozens of folks, not thousands.
A lot of these are general problems with App Store Connect, but they all affect TestFlight because it makes it hard to get at what you need...
Please, for the love of $DIETY, allow us to hide apps from the picker page. We created our first Apple ID in 2007 (281795480) and it's appearing above the fold on our list of apps.
I never want to see "Developer Removed from Sale" in our list of apps, but I'm seeing 9 of them right now.
Then there are the apps that Apple has "Removed from App Store" on our behalf. It's fine that you do that: it's not fine that I have to look at it every day.
A lot of apps can't be deleted because they are a part of an App Bundle and those are like cockroaches: they will survive a nuclear blast.
Retail demos are another thing that I'd like to hide: they are important to Apple, not to us.
Ideally, the list of apps should be something that we can define ourselves. Let us have favorites (which would be the apps we are currently actively working on). Then give us a mode to only show favorites.
Has anyone on your team ever used search?
It finds stuff just fine (although it's not super quick). But then as soon as you click on one of the apps that's a result, you lose your search. Same with the "meta searches" like for status and type.
It's basically useless.