sure you can but its not simulating literal iPhone SE hardware, the software goes as fast as the Mac can run it. which is more or less midrange iPhone speed although wildly different limiting factors
Nope - it's a simulator not an emulator, the code is even compiled separately to the Mac's arch in the simulator target, so it used to be that it was compiled to x86 and the device target compiled to arm64
That's a difference from Android app dev, where the SDK has an emulator that runs like a VM, emulating real hardware, which is why iirc Android devs always complained that it's super slow and annoying 😅
On iOS it at least used to be that the simulated app in the simulator on x86 ran much much faster than the app on the actual device, so you couldn't detect some performance issues until running on the device, right now it's probably about the same
I seriously suggested doing this instead of coding around some shitarse behaviour of some ancient Android device a dozen of our users had. Would have been an order of magnitude cheaper than the developers’ time.
Isn't it just 120Hz like a lot of phones? Mine's 120Hz. I'm out of the loop on iPhones so not sure what previous versions had tbh. 120Hz has been a flagship standard expectation for a while now.
from day 1 i've always ran opencode on an always on server
which means i've been getting the best possible experience that probably is not the most common
tricky thing
Astra's opinion:
> My vote is “caveat prodevsumptor.” It sounds just respectable enough that someone might need a second to realize you've committed crimes against Latin.