|
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 |
|
Hi Yordan Since a few weeks we do offer an native iOS client for Ivy - https://itunes.apple.com/us/app/axon.ivy/id1086613359?mt=8. It offers a task list with all tasks of the user that is registered. You can start each task by tapping on it and the task runs on the client in an integrated browser inside the app. This works for all kind of tasks and for either web page or Html dialog based UI's. Rich dialogs do not work as the Java run time does not exist on all mobile platforms. Big advantage for using this approach ist that you can re-use all your existing work. If you need offline support, you can go one step further and use the app together with offline tasks and offline dialogs. Users can then work on their task even when their device is offline. As a drawback, you specifically need to design the process to support offline. And the UI is a little less rich as stuff like AJAX or server side validation do not work offline. If you want to develop the app on your own, we see two ways. Either you embed the web view in your app and you run a full Ivy process with UI (web page and HTML dialog) in that web view. Option 3 in your list. If you want a more native look, then we recommend to use the new REST API for tasks (minimum 6.0) or the new feature from Ivy 6.2 to publish REST services within Ivy. Whether you choose a native or hybrid approach depends on your needs. Hope this helps Michael Thanks for the explanation, Michael ! I wander if you are planning to release an Android version as well ? Best Regards, Yordan The Android app is in development, unfortunately slowly as we have more app projects wit customers ongoing. Therefore I cannot tell you a release date :-( 1
...and now almost 3 years later, what is the status of the Android app? Is it still on the Roadmap of Axon.ivy? 1
Thanks for asking. Almost 3 years later, the picture has changed a bit. Since we are heavily investing into our standard Axon.ivy Portal, we didnt push the Android development. Our standard Portal is already mobile-ready and will be fully responsive with the version 8.0. On the other hand, the "App Hype" for business apps is not as strong anymore. Therefore, we didn't push the Android development & encourage our customers to use the standard Portal (or the iOS App). Speaking about the iOS App. With the release 8.0, we plan to release v2.5 for the iOS App with bug fixes & iOS 12&13 support. |
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Tags:
Asked: 08.08.2016 at 10:26
Seen: 2,636 times
Last updated: 18.06.2019 at 07:13
