Mobile performance improvements

[matthinc]

Different strategies (optimized rendering, caching) to improve the performance of the mobile app.

Progress:

• Allow > 60 FPS rendering on some Android devices
• Load assets in 3 steps (thumbnail -> SD -> HD) instead of 2 (thumbnail -> HD)
• Prevent all gestures on remote_photo_view until HD version is loaded (prevents jumping)
• Loading indicator in toolbar of image_viewer_page

[alextran1502]

There are two issues I noticed

1. The loading circulation is a little bit distracting and I don't think we need it there. Additionally, it takes a while to finish loading all three stages, is it supposed to be that long?

2. The action swipe up to show the photo's detail is rendering blank, probably null properties are passing in. Clicking the horizontal three dot works fine. See video below for more details

Android.Emulator.-.PixelXLAPI30_5554.2022-08-07.13-16-17.mp4

[matthinc]

I think the loading indicator (or something like it) is necessary here because zooming is disabled in stage 1 and 2.
Especially stage 2 looks almost like the full-scale image, so I think it could be confusing without some information that the asset is still loading. But I'm open to suggestions on how we could solve this differently.

Good catch with the exif sheet! I think I messed this up during a rebase.

[alextran1502]

I think the loading indicator (or something like it) is necessary here because zooming is disabled in stage 1 and 2. Especially stage 2 looks almost like the full-scale image, so I think it could be confusing without some information that the asset is still loading. But I'm open to suggestions on how we could solve this differently.

Good catch with the exif sheet! I think I messed this up during a rebase.

So this poses the question, do we need 3 stages of loading? Especially on mobile, since it increases data consumption with a little trade-off on quality.