Hello Ivy Team, I want to provide some mobile experience to my users. There are currently 3 approaches in my head: 1.Native Mobile Client - Native iOS and/or Android app - no Web View - communicating to Ivy via HTTP - only data returned, no HTML - offline support 2.Hybrid Mobile Client - Phonegap or Ionic HTML SPA hosted on the device (web view) - communicating to Ivy via HTTP - only data returned, no HTML - offline support 3.Mobile optimized web view - OOTB provided by Ivy web technologies - JSF and PrimeFaces - no offline support Option 3 is the easiest to implement and release, but it has the worse UX. My biggest concern for option 1 and 2 is the security in terms of session management. Witch approach would Ivy Team recommend ? I saw in the documentation about the Offline User Dialogs, but they goes to option 1 Best Regards, Yordan Yunchov

Hello Ivy Team, I want to provide some mobile experience to my users. There are currently 3 approaches in my head: 1. Native 1.Native Mobile Client - Native iOS and/or Android app - no Web View - communicating to Ivy via HTTP - only data returned, no HTML - offline support 2. Hybrid 2.Hybrid Mobile Client - Phonegap or Ionic HTML SPA hosted on the device (web view) - communicating to Ivy via HTTP - only data returned, no HTML - offline support 3. Mobile 3.Mobile optimized web view - OOTB provided by Ivy web technologies - JSF and PrimeFaces - no offline support Option 3 is the easiest to implement and release, but it has the worse UX. My biggest concern for option 1 and 2 is the security in terms of session management. Witch approach would Ivy Team recommend ? I saw in the documentation about the Offline User Dialogs, but they goes to option 1 Best Regards, Yordan Yunchov

Hello Ivy Team, I want to provide some mobile experience to my users. There are currently 3 approaches in my head: 1. Native Mobile Client - Native iOS and/or Android app - no Web View - communicating to Ivy via HTTP - only data returned, no HTML - offline support 2. Hybrid Mobile Client - Phonegap or Ionic HTML SPA hosted on the device (web view) - communicating to Ivy via HTTP - only data returned, no HTML - offline support 3. Mobile optimized web view - OOTB provided by Ivy web technologies - JSF and PrimeFaces - no offline support Option 3 is the easiest to implement and release, but it has the worse UX. My biggest concern for option 1 and 2 is the security in terms of session management. Witch approach would Ivy Team recommend ? I saw in the documentation about the Offline User Dialogs, but they goes to option 1 Best Regards, Yordan Yunchov