Expand my Community achievements bar.

SOLVED

Adaptive design from InDesign

Avatar

Level 1

Hi everybody, I tested Adobe DPS 2015 from a couple of weeks. In the past, we create in InDesign, different models for each device.   Is it possible in Adobe DPS in 2015 to combine two versions of an article from InDesign in the same app / project. One showed for the iPad and the other for the iPhone.

1 Accepted Solution

Avatar

Correct answer by
Level 6

Hey BLUE;

We used to have to build different folios for iPhone and iPad back in the previous version of DPS (DPS 2014.)

In DPS 2015, the differentiation is more about phone and tablet, rather than specific devices (or platforms) it's about device classes.

If your project is setup with two top-level nav systems (Project Settings) then you build collections and collection content for both phone and tablet. And the organization in the phone structure goes to all phones, all tablets get the tablet structure. These structures might have differently design/exported content for the two device classes if you're working with pixel-perfect content, or one article using HTML/CSS could be loaded into both structures...

All pixel-perfect content will scale to fit any screen, so a layout designed for phone will scale to all phones regardless of OS/manufacturer. An iPad sized design will scale to fit all tablets. Phablets might get one or the other depending on how the device identifies itself -- and then it'll scale the content.

HTML-based content will fill the screen, and if you include CSS/media querries/etc. it can adapt to the device size. Greater flexibility, perhaps less interactivity depending on your HTML skills.


There's a different approach in DPS 2015.


HTH -- Colin

View solution in original post

2 Replies

Avatar

Correct answer by
Level 6

Hey BLUE;

We used to have to build different folios for iPhone and iPad back in the previous version of DPS (DPS 2014.)

In DPS 2015, the differentiation is more about phone and tablet, rather than specific devices (or platforms) it's about device classes.

If your project is setup with two top-level nav systems (Project Settings) then you build collections and collection content for both phone and tablet. And the organization in the phone structure goes to all phones, all tablets get the tablet structure. These structures might have differently design/exported content for the two device classes if you're working with pixel-perfect content, or one article using HTML/CSS could be loaded into both structures...

All pixel-perfect content will scale to fit any screen, so a layout designed for phone will scale to all phones regardless of OS/manufacturer. An iPad sized design will scale to fit all tablets. Phablets might get one or the other depending on how the device identifies itself -- and then it'll scale the content.

HTML-based content will fill the screen, and if you include CSS/media querries/etc. it can adapt to the device size. Greater flexibility, perhaps less interactivity depending on your HTML skills.


There's a different approach in DPS 2015.


HTH -- Colin