Hello experts,
We are looking for some guidance\opinions regarding adding mobility in our Portal Environment.
Our Environment:
- Portal 7.4
- ECC EHP7
- Separate Gateway with Fiori wave 2 apps installed (HUB deployment) and running.
- We are also using Web Page Composer
- We have the option to setup 'Portal on Device'
We are not clear on how to use a mixture of all these functionalities to accomplish the best user experience.
KEY QUESTION:
- Should we decide between using 'Portal On Device' OR 'Fiori Desktop'? (I know it is recommended for Portal customers to use Portal and Fiori together, but seems like its not straight forward implementation. And does this mean we do not use ‘Portal On Device’ at all!).
We see these options:
OPTION 1: Implement ‘Portal On Device’, and have Fiori run independently:
- Fiori URL will open up Fiori Launchpad.
- Portal URL opened from Desktop Browser will open up regular portal.
- Portal URL opened from Mobile device will open up Tablet, or Smartphone Desktop.
CONS:
- Would this lead us to manage 3 different entry places for ESS\MSS portal applications?
OPTION 2: Don’t use Portal on device, but use Fiori Desktop in the portal:
- Portal URL opened from Desktop Browser, regular portal loads up.
- Portal URL opened from mobile device, Fiori Desktop will create the tiles.
CONS:
- Not able to use the easy Fiori Launchpad Designer?
- Not sure if we can use Fiori Client App in this scenarios?
Any past experiences\guidance\opinions would be much appreciated....
Thank you,
Harman