nick
Performance with lots of image contents
I like this -- it works great. However, my use case is 20 fullscreen images. I think how it works is that all of the compressed JPG get uncompressed into memory when the app starts. So it takes a bit of time to start on an iPad Air 2 (I don't have an iPad 1st generation to compare). It works but I'm worried about running on older iPads.
I think my problem is outside of the core of what this project is aimed at but do you have any thoughts on it or not so much? I am thinking I need to implement my own carousel that just renders the current page, the next page and the prior page (so swiping is fast). Maybe it is current +2 on each side -- whatever tradeoff feels right. But that direction seems likely or going to direct native (I hesitate though -- my app isn't very complicated and I got it together about 95% in a day but I imagine that will translate into quite a bit more time on native).
