Earlier this year did a similar thing in my the I was working on, but my solution was to also down-scale it to a limited max 1600px (longer edge), as the project allowed to use smaller resolution images for the given purpose. As many new phones make too high resolution images for many purposes, down-scaling worked much better for me.
Hey Philipp, Could you please make a video how to navigate back from a page to previous page, by swiping left to right, current page shifts left to right revealing previous page below? Please
The app compressed 20MB images for me without any issues. Since the loop uses a new stream with each iteration, the previous one can be freed up. Therefore, there are allocations for the input byte array, the bitmap and the currently compressed byte array which even for a 20MB image is 50-60MB in memory allocations and is not a lot given what modern devices have as RAM.
@@PhilippLackner 20 mb is a compressed image, but when processing it converts to uncompressed bitmap that could take more than 1gb of RAM depends on resolution. Images in Android are displayed with ARGB888 with 4 bytes for 1 px. if we have image resolution 20000x20000 ( I really have one, it is space photo) Bitmap from this image has 1.5 GB size. I checked just know - if I open default image in MS Paint - it take 100-140 mb of RAM (In Task Manager) But if i open the large one - it takes 3.6 GB of RAM. The same happens when you just loading and compressing image in loop but several times! I understand that this case with 20000x20000 image is super rare, but if you develop serious apps with many active users your app will crash if try to load this image. The only workaround is to use BitmapOptions.inSampleSize and already load much more smaller image. For example Telegram compresses all images to fixed 1280px by the larger side. And Telegram doesnt crash when trying to load this image. But if use "loop" approach - it will crash 100%
