SwiftUI List performance

I learned my lesson to not color outside the lines with pure SwiftUI. I've not tried it again since April, so maybe something changed with the Xcode releases since then, but I just export pure arrays from my view models instead of trying to be clever with custom collections. It would be cool if it were predictably extensible, but there's too much goddamn magic going on to waste time with it in my opinion.

There is something called the MatchMaker ViewController. Your app should open this up - that's where your list of open matches lives. True. I can get it to show up by enabling showExistingMatches. But what about the initial invitation when the recipient doesn't have the game installed?

[quote='813195021, CamJN, /thread/813195, /profile/CamJN'] that's a LOT of overhead! [/quote] In relative terms, sure. But it’s also a short amount of total time, so it doesn’t give you a lot of space to optimise. Anyway, there are a bunch of things you can do on this front, but there are also certain fundamental limits to how fast a given process can launch. If you use C to create a small ‘hello world’ project, how does its performance compare to that of your tool? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hey, I have a same question. All I could do was a crutch through UIKit, it works exactly for action in a preview, however it broke, another swiftUI effects, such as swipeAction or confirmation dialog(iOS 26). Did you find the right way to implement this feature? Thanks.

There is something called the MatchMaker ViewController. Your app should open this up - that's where your list of open matches lives.

[quote='872985022, nightow1, /thread/813147?answerId=872985022#872985022, /profile/nightow1'] You have a choice, right? [/quote] No, you literally don't. Every iPhone app is expected to work on an iPad. It doesn't have to be written as an iPad app, i.e. it doesn't have to take up the full screen and have all the same navigation stacks, tabs and layout as an iPad app does, but the app must function on an iPad. App Store Connect shows it is an iPhone app, yes, but that just means it is listed in the App Store for iPhones. If someone downloads it on their iPhone it will also become available on their iPad, too, so it must work on their iPad as well. As I said, run it on an iPad and see if the app works properly. If it doesn't, then you have to fix it. The App Review Team are literally telling you that they are rejecting it because it doesn't function properly on an iPad. Your app must work on an iPad, so make it work on an iPad. Just run it on an iPad and see what needs fixing. It might be a really simp

the lengthy lecture about what App Review is doing me a favour with a bit strange After your initial greeting, you said, and I quote, I'm seeking advice. And then, at closing, you doubled-down on that with, Any advice, experiences, or suggestions would be greatly appreciated. You've also managed to argue both that Launchpad is terrible (and Tahoe's version is even worse), and that I shouldn't bother building something better. You're mischaracterizing my statement. I suggested that you shouldn't build something that looks like LaunchPad, and apparently App Review agrees with me. That's what an app launcher looks like. As I said in my first reply, I recently purchased a nice app launcher from one of my favourite developers. It looks nothing like LaunchPad. That fact was part of the appeal. My original question was a straightforward one: have people encountered IP issues during review for apps that improve on native functionality? You posted a numbered list of 5 specific questions, followed by an explic

Hi, some additional context: The app is in open beta and not public yet. Multiple support emails did not get a reply The entitlement request does not get reflected on the app listing in the developer portal.

I know this is years later.. but I am going through a reverse situation. I have falsified everything for iPad in the code, am not required upload iPad photos, but the reviewers keep being told to judge how my app performs on iPad for some reason. So frustrating. And only a small number actually read the messages before reviewing, so I am stuck in a loop with the reviewers of them thinking the app is for ipad when it is not. Hopefully, I can get some help with resolving this soon.

Hi, we have an open feedback listing that we are still awaiting a response for FB21147185. Is there any update on this?