1) Perhaps as a future feature request, some means to define the
default image. Note that if we did not have a default image,
someone else would open a bug complaining about the lack of a
2) This is just the nature of remote images. There's a number of
factors, including the speed at which the server sends back images.
Another possibility is that the first images are requiring a DNS
lookup and firing up the network connection, while latter images
already have the DNS cached and possibly even still have a
connection to the server. So the faster-loading later images
'appear' to have loaded first, since there was less of a wait.
One possible solution to remote images being slow is to make
them not remote. For example, in the background before the
coverflow is even used, and you know the images are going to used,
use HTTPClient to save them locally.
Either way, the original bug is fixed.