Many thanks for that info. I managed to find the nativescript-fresco plugin when I went back in for another look . I think the search text box works in a peculiar way. I think that needs a little attention. I then made the mistake of just selecting it and including it in my project thinking that would work with my companion app & livesync. For some reason I picked up lodash a month or so back that way, and it did work. I think that module must be bundled in with the companion app already.
So I can see from your example how to use it. The listviewlayouts.xml is insightful. I can see that you can load images in ios and android differently (Android using fresco). That is cool. My app works really well on iOS. I have to hand it to those guys they manage memory better than Android, in that I don't have to deal with it.
The drawback I've discovered to using fresco is that the developer app (companion app?) can no longer be used once you include these packages. To develop in platform and use those packages I would need to do a build and deploy, which is a long turnaround and not a favourable way for me to debug. The advantage of coding in Platform is that I don't have to install and maintain tools, and that I can code and test on real devices (via livesync) in the companion app rapidly. If I go down that route that becomes one less reason to stay on platform. For the meantime I am implementing bespoke image resizing using android bitmapFactory and using image-cache to manage the data. Though it still looks like I am having to invoke gc() to keep my app going on Android. I'm explicitly dereferencing the image.src (= null) when I leave a page. But if I don't invoke the gc() nativescript stops.
Is image-cache only for loading pictures off the internet? It seems you have to specify a url. Can that point to the local file system? All the documentation and examples I have seen all refer to "https://..."