Question

I create app called it ( app A ) which need to store large No. of high resolution images in res drawable folder , ( i know that i can downloaded remotely , but i need to keep it in drawable res folder ) , its:

3000 x 4000 JPEG images taken by digital camera , as this will lead to unacceptable increase app size and lead to rise memory exception when run it on device ,so can we create another app called
( app B ) , just for resizing the images , which will pick this images that will be stored on SD
( just for purpose of resizing ), then resize it to smaller sized images but without loss image quality and keep high image resolution , then save it again to SD either with PNG or JPEG format , so then i can take images from SD card then save it to ( app A ) resource file and use it , with reasonable size and high resolution ,

hope if any one can supply tutorial or link explaining that or an full code answer applying this ,

Note : i tried using computer software as : photoshop or format factory but all affect the resolution.

your help will be highly appreciated and thanks.

Answer 1

This is best solved using image tiling. You break your image into a number of smaller ’tiles’, say 500x500px which are then laid out on a grid – pick your favorite layout. For rendering zoomed in, only those tiles that are on-screen will be drawn.

Here is a reference for more details: How to tile and scroll a large image (10000×10000) in android

To split the image, follow the instructions here: Android – Split Drawable

For really smooth behaviour, you can additionally create a scaled down image from the original and use the downscaled tiles when the grid is zoomed out. Switch back to the original resolution as the user zooms in.

EDIT

my goal im have large pic of 3000*4000resolution i want to transform it to smaller size but keep same resolution

There are a few concepts to keep in mind:

1. The original resolution of the picture (In your case 3000×4000 pixels)
2. The resolution of the display. For example, a Nexus 4 has a display of 768×1,280 pixels. Displays have an important property: DPI or dots per inch. This is the number of pixels that together measure 1 inch (25.4mm) on the physical screen. Apple’s ‘retina’ displays on the iPhone have a DPI of 326 – this is the benchmark of sharpness; pixels on this screen are too small for the human eye to see individually/sharply at typical holding distance. Old monotone LCD displays have a DPI somewhere in the 30-60 range – you can easily see the square shape of individual pixels.

3. The portion of the picture to be shown on the display – the view port. There are two different extremes:

   1. Zoom out: You want the complete picture shown on the display. In your case, the picture has more pixels than the display (the display has a physical limitation that there are not enough pixels to show the original picture at the original resolution), so one pixel on the display will render a group of pixels from the picture, averaging the colour and brightness, or
   2. Natural resolution: Natural resolution is where one pixel from the original image is displayed on precisely one pixel on the screen. In you case you would only get to see about than a quarter of the image. This scaling has the greatest sharpness, but some details of the image may be too small to see, because the eye cannot actually see the individual display pixels.
   3. Zoom in: You want to display an even smaller portion of the picture on the display, where the original pixels from the picture are actually larger than the display. Here one pixel from the picture will be displayed on several or many pixels on the display.

Now, the Android image libraries will help. When you render an image on the display, the libraries will scale the picture to “fit” the pixels on the display – your actual picture will be unaltered.

I hope with this new language that you can see the fundamental constraints and can therefore decide how to proceed.