Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

‘Corporate’ world use to rely on ‘User Endpoint Management solutions’ such as mobileiron, , Microsoft Intune, etc. Additional costs might be required.

Long-term Vision

To confirm

  • use of device with multiple users?

  • transition strategy?

Questions to be answered:

  • Design of the mobile applications UX/UI

  • Combination of the functionalities in only one app: modular mobile application

    Client mobile app
    • Advantages one app

      • one codebase

  • Web/native solution: Android vs PWA

      • can make “variant“ to simulate multiple apps

      • easier for users to find

      • mirror UX from web application (if PWA ?)

      • detailed customisation possible for the implementers

      • reuse of common functionalities (e.g. enquiring, barcode reader)

      • modular architecture: might allow additional implementation features

      • Show/display menu based on roles (possible issue if there is multiple user using on app)

    • Advantages multiple apps

      • versioning easier to read, a lesser impact for the update because the user-based of each app will be smaller

      • on app per role

      • “ready to use“

      • specialized apps => know its purpose, easier marketing/visibility

      • fit to segmented usage (claim and enrolment)

  • Native/Web/hybrid solution: Android vs PWA (progressive web application) vs Ionic/Xamarin/ReactNative

    • Advantages native mobile app

      • not dependent on version of browser

      • Code already exists

    • Advantages PWA

      • “one” codebase for web and mobile front end even if mobile optimization is required

      • the ReactJS Frontend(used in modular) can integrate PWA capability => code can be reused

      • Regular web app gains offline functionality

      • can migrate one module at the time (no big bang required)

      • access to browser capabilities (e.g. GPS, camera)

    • Disadvantage PWA

      • Design to be reviewed => responsive design

      • Show only required fields => don’t pollute the view

      • Offline DB / Synchronization logic can be complex (service worker / Cache management)

      • Need SSL signed by a trusted body (let’s encrypt, GlobalSign ….) which complexify the testing by preventing usage local servers (current modular has the same limitation)

      • Don’t have access to full device hardware - limited to browser permissions/access.

      • dependent of the version of the browser / webview

    • Advantages Hybrid

      • code more likely to be independent of the phone vendor libraries

      • access to native platform capabilities (through Cordova)

    • Drawback for Hybrid

      • New language to be used

      • Possible license fees (tbc per solution)

      • Redevelopment required

  • Client mobile app (insuree app)

Next step:

Nils: clean up formatting → Table

Uwe/Dragos/Patrick/Nils - meeting April 6th