Using Hi DPI Images in your Mobile App

Getting Started with ADF Mobile Sample Apps

Whether you are developing an ADF Mobile application or a classic ADF Server application, it is becoming more and more important to support hi-DPI screens (high resolution or "retina" displays). There is no easier way to make your application look out-dated than to use grainy, unprofessional image assets or use them improperly.

In HTML, the "px" unit corresponds to the same amount of space regardless of the DPI of your device (however, the number of device pixels may vary). The original iPhone models did not have hi-DPI displays. Each point of color on those screens corresponds to one HTML CSS "px" unit. Newer iPhone models introduced a hi-DPI (or "retina") display that has 4 device pixels in the same amount of space that 1 device pixel used to take up (2 device pixels wide by 2 device pixels tall); on these new devices, the width and height "px" values use twice the amount of device pixels.

Why is this a common problem? Since ADF Mobile uses HTML, displaying an image is not as simple as just specifying the source path and magically hoping the browser will know that you are using a high resolution image. You must specify dimensions to go along with the source path.

Let's work with an example. You have an image named "image-64.png". This image has a size of 64 by 64 individual dots of color (individual points of color information). If you coded your page like the following, the image will be shown with a width of 64px and a height of 64px (one color dot per "px"):

   <amx:image id="i1" source="images/image-64.png"/>

This would look just fine on a classic low-DPI display. However, on a hi-DPI display, it still takes up the same space but since there are more device pixels, the image will look very grainy.

In order to look crisp and professional, you need to set a size so that each dot of color corresponds to at least one device pixel. For a hi-DPI display, this means your image needs a width and a height specified such that you use 2 dots of image color information per HTML CSS "px" unit (e.g. a 64 by 64 sized image should be specified to use a width of 32px and a height of 32px. In code, your page should look like this:

   <amx:image id="i1" inlineStyle="width:32px;height:32px" source="images/image-64.png"/>

Even if you still want to support legacy devices for your application, this same image (with the same specified width and height) will look beautiful on low-DPI screens because of how images are processed modern browsers.

If for some reason you really needed or wanted to specify alternate images for each kind of device, you have the option to use a device properties EL variable to toggle the rendered state of alternate amx:image components or simply use that EL to alter the inlineStyle and the source path as desired.


The use “HiDPI” in this article is a general way of describing higher resolution displays to help explain this concept. Using XHDPI for Android or Retina for iOS is more specific. For example:

Technically Android has 4 basic buckets for these displays:
LDPI (x .75)
MDPI (x 1.0) – Android’s Baseline
HDPI (x 1.5)
XHDPI (x 2.0)

While Mac OS X and Apple iOS have 2 buckets that map to MDPI and XHDPI in Android:
Non Retina (x 1.0)
Retina (x 2.0)

Posted by guest on March 14, 2013 at 11:52 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed

This blog is is dedicated to announcements,tips and tricks and other items related to developing, integrating, securing, and managing mobile applications using Oracle's Mobile Platform. It is created and maintained by the Oracle Mobile product development team.

Archive of past entries

Even More Mobile Development Blogs

Oracle A-Team Site - Mobile Related Entries

Code samples from the Community

Fusion Middleware Blogs


« February 2016