The internet is not ubiquitous; there are areas/environments where there is no access to WiFi or a Cellular network and people are forced to work disconnected/offline. That is the basic justification for the ICAA Client, which we believe is fundamental to the future of Domino.
Browser access was supported in the Notes Browser Plugin, which preceded the ICAA Client, and in ICAA prior to version 1.0.1.
Following is our justification for restoring Browser Access to the ICAA Client:
- Part of the "rejuvenation" of Domino, has to be a more modern UI. The Notes Client/ICAA UI, which has been in use for almost 30 years, is old and needs a face-lift, if it is to be embraced by the modern generation. Tools like teamWorkr are being used to "modernise IBM Notes" by moving applications to mobile devices and a Browser interface, which reinforces our point that a Browser UI is a requirement.
- Whether it's Chrome, IE of Firefox, people spend more time in front of a Browser UI than any other.
- The absence of a Browser UI will force Partners to retrofit their applications, which already have a Browser UI, to work with the Notes Client UI, when working Offline.
- Browser access in the ICAA Client will also give an advantage over Low Code platforms like Outsystems in that Users will be able to:
- Work Offline
- Run on Windows, Apple and at some point Android OS
- Use a Browser UI, which will change the perception that Users have of the Notes UI.
The logical conclusion is to restore a Browser interface to the ICAA Client, just like Verse has. Or at least, give Users the option of the Notes Client or Browser UI.