Matthijs Hollemans

Use an iPhone XS or better. :-) On older devices, YOLO doesn't really perform very well. The best thing you can do there is switch to something like MobileNet+SSD: https://machinethink.net/faster-neural-networks/...

On anything from iPhone 7 up to (and including) the X, the best way to get better speed is to not use YOLO but MobileNetV2+SSDLite. (I don't have any recommendations...

That's really the same thing. The more efficiently a model runs, the faster it is, and the better the battery usage is. See also https://machinethink.net/blog/how-fast-is-my-model/

It is at least 4x faster / more efficient than (tiny) YOLO v2. Only on the XS / XR is YOLO faster because it can take advantage of the Neural...

Did you run both at the same number of FPS? Naturally, if MobileNetV2+SSDLite runs as fast as it can, it will use more energy than TinyYOLO running at a lower...

There was a problem with the Metal compiler in iOS 11.3 on the iPhone X. These problems should be solved by iOS 12 (and maybe by 11.4?). But I don't...

If you run the app and then pause it, you’ll see that CoreML is using something called ANE, which stands for Apple Neural Engine. I think the reason MPS supports...

I think it’s more the other way around: they first had MPS kernels for doing convolutions etc. Then they realized they could add a graph API. And then even later...

The iPhone 6 is really too slow for this kind of thing.

You need to choose your own development account in the Project Settings screen in Xcode. Right now it is set to my own account.