Posted: 22 Feb 2020 9:03 EST Last activity: 2 Mar 2020 15:43 EST
Application skin configuration
Please select the most two appropriate answers for this question.
An online sales application supports both laptop and mobile devices. You are configuring the application skin and you notice the responsive layout in the mobile device is not displaying views as stakeholders require.
How to resolve this situation without negatively impacting the laptop users?
1) Update the process to give mobile users a separate portal
2) Adjust the responsive behavior in the skin for optimal viewing in the mobile portal.
3) Do not use a skin for the mobile application version.
4) Use the same application skin in all portals.
***Edited by Moderator Marissa to update platform capability tags****
I am with you for 2. Not sure if 1 would be an optimal solution. How much effort is needed to create a separate portal? Hope there is a way to re-use most of the code.
When we do 2 (Adjust the responsive behavior in the skin for optimal viewing in the mobile portal), then we can select 4 (Use the same application skin in all portals). Just talking it out loud. Couldn't figure out the most appropriate answer.
I have the same question. My issue with providing a separate portal is that you have not addressed the stakeholder requirements. You still have an issue with the way the application is rendering on the mobile.I am not sure you can avoid the skin. You still have to provide some skin, right, even if it is the out of the box default skin.
I would think you want to use the same skin and address the responsive behavior.
Posted: 1 year ago
Updated: 1 month ago
Posted: 29 Feb 2020 9:21 EST Updated: 14 Jun 2021 7:38 EDT
the only valid answer is #2 - note that by default in ui-kit, all the layouts that have a 2 or 3 columns have a responsive behaviors - so if you built your app, on top of ui-kit, this should not happen if you use the OTB formats
#1 will not resolve the situation since a new portal for mobile will default to your application skin and as such will inhibit the same problem - to fix the problem, you would need to create a new skin that makes the layout responsive... this is not a recommended best practice since you will need to maintain 2 skins.
#3 is not possible - all portals are using a skin
#4 will not resolve the situation since the original problem already assumes that you are using an application skin and sharing the same skin for both your mobile portal and desktop.