Although in this ever more connected world, offline support is increasingly less of an issue, it is still something that should be considered for enterprise applications. You may have users making changes on a subway, or on a flight. Or in an oilfield in the middle of nowhere with limited to no connectivity. It’s still not really acceptable for a line of business app to cease to function completely if there is no internet available. Again, we have seen how we can use local storage in the browser to cache changes. This philosophy can be build out further with the development of a progressive web application, that allows the user to continue to use the app in a disconnected state, utilises a local storage solution, and then performs some kind of background synchronization when connectivity is restored. These kinds of situations often will result in conflict resolution requirements, as we have discussed earlier. --ar 9:16