Classic ui vs touch ui

[vanky_s]

What are the major differences between classic UI and Touch UI? Why should we use Touch UI

[Singaiah_Chintalapudi]

Vanky S wrote...

What are the major differences between classic UI and Touch UI? Why should we use Touch UI

See below links:

https://docs.adobe.com/docs/en/aem/6-1/deploy/best-practices/ui-recommendations.html

https://docs.adobe.com/docs/en/aem/6-1/develop/the-basics/touch-ui-concepts.html

https://mkbansal.wordpress.com/2016/01/19/aem-touch-ui-what-and-why/

[smacdonald2008]

Touch UI is mobile friendly - that is - if you want to modify a site with a Tablet - you can via Touch UI. 

When developing components with Touch UI - you use different APIs to build the dialog. You use Granite APIs. This is covered in this ASK THE AEM Experts on Touch UI. 

https://communities.adobeconnect.com/p3kcgxkqvy3/?launcher=false&fcsContent=true&pbMode=normal

A components view is the same - that is-  the component script is the same and same data is rendered. TOuch UI or Class UI - the same component is rendered. Only difference really is how you build the dialog for authors to use on Author instance during design time. 

[smacdonald2008]

Also - look at this article to learn how to build a Touch UI component: 

https://helpx.adobe.com/experience-manager/using/creating-touchui-component.html

[kautuk_sahni · Accepted solution]

You should use Touch U.

Adobe is moving towards touch UI across marketing cloud solutions to provide an unified experience. 

Adobe introduced a new touch-optimized UI with AEM 5.6 for the author environment. This differs considerably from the original classic UI as it is designed to operate on both touch and desktop devices. The basic principles of the touch-optimized UI are:

    Mobile first (with desktop in mind)
    Responsive design
    Context relevant display
    Reusable
    Include embedded reference documentation
    Include embedded tests
    Bottom-up design to ensure these principles are applied to every element and component

Classic UI versus Touch UI

                         

ExtJS	Granite UI
Remote Procedure Call	State Transistions
Data transfer objects	Hypermedia
Client knows server internals	Client does not know internals
“Fat client”	“Thin client”
Specialized client libraries	Universal client libraries

AEM is gradually migrating existing layouts/modules to Touch UI, but at the current point in time some UI’s are still on classic (original) UI (eg. design dialog). Adobe will continue supporting Classic UI in near future.

Please reed this full community article :- https://mkbansal.wordpress.com/2016/01/19/aem-touch-ui-what-and-why/

I hope this will help you.

Thanks and Regards

Kautuk Sahni

[Jitendra_S_Toma]

Vanky S wrote...

What are the major differences between classic UI and Touch UI? Why should we use Touch UI

To be frank, it is not worth for any project. Nobody likes to update or fill the component details from Mobile device. I don't see any business value in it. it is just another feature.

[Opkar_Gill]

Jitendra S.Tomar wrote...

Vanky S wrote...

What are the major differences between classic UI and Touch UI? Why should we use Touch UI

To be frank, it is not worth for any project. Nobody likes to update or fill the component details from Mobile device. I don't see any business value in it. it is just another feature.

All new features since version 6 have been developed for Touch UI only, so unless you want to be restricted to the older classic ui features, you should really be using touch ui now. If you are starting a new project(i.e. 6.2) there is no point in developing it in classic ui.

Regards,

Opkar