Expand my Community achievements bar.

SOLVED

Touch-Optimized UI vs Classic UI

Avatar

Level 7

Hi,

  1. If something is not worked or not achieved through Touch-Optimized UI(Granite), it means that component is not working in AEM6?
  2. Suppose if something is working in classic UI of AEM6 and not worked in Touch-Optimized UI. Can we say this component is working in AEM6?
  3. Is there any important difference between these 2 UIs except the way of authoring a component?

Thanks,

AryA.

1 Accepted Solution

Avatar

Correct answer by
Level 10

Note there are

  1. Couple of features which are available only on Classic UI & Missing in Touch UI
  2. Adobe making major investments in Touch UI but not in classic UI 

Following are the common usage now

  • Touch SiteAdmin UI
  • Touch DamAdmin UI
  • Classic Authoring UI

Answers to your questions are

  1. Make sure at least components working with Classic UI interface. I am sure engineering will find a way to reuse with less effort to move into touch ui for missing features.

  2. Yes. Note deprecation is not declared yet. 

  3. Off course, look at basic principals at http://dev.day.com/docs/en/cq/current/touch-ui/touch-ui-concepts.html

View solution in original post

1 Reply

Avatar

Correct answer by
Level 10

Note there are

  1. Couple of features which are available only on Classic UI & Missing in Touch UI
  2. Adobe making major investments in Touch UI but not in classic UI 

Following are the common usage now

  • Touch SiteAdmin UI
  • Touch DamAdmin UI
  • Classic Authoring UI

Answers to your questions are

  1. Make sure at least components working with Classic UI interface. I am sure engineering will find a way to reuse with less effort to move into touch ui for missing features.

  2. Yes. Note deprecation is not declared yet. 

  3. Off course, look at basic principals at http://dev.day.com/docs/en/cq/current/touch-ui/touch-ui-concepts.html