Feature Request / Discussion: Offline Capabilities for Angular UI

[AhmadAlMunajjed]

Hello ABP awesome community,

I'm working on enhancing the offline experience within an Angular web application built on the ABP framework. Currently, I'm facing the following challenges when internet connectivity is unstable:

Core Requests: On every page/window load, there are 4 mandatory network requests:

OpenID: openid-configuration, and jwks (plus a token refresh if necessary)
ABP: application-configuration and application-localization

Objective: My aim is to provide users, particularly in point-of-sale scenarios, the ability to:

• Log in and fetch essential data.

• Continue working with a degree of offline functionality.

Feature Consideration:

Would it be feasible to introduce a caching or storage mechanism for the responses of these four core requests? This would allow the application to open subsequently, even with limited or no internet connection. To minimize user disruption, I propose using longer token validation periods.

Discussion Points:

Caching Strategies: What would be the most suitable caching strategies (e.g., Service Workers, IndexedDB, LocalStorage) within the context of the ABP framework and Angular architecture?
Security: How can we ensure the secure storage and management of these sensitive authentication and configuration details?
Framework Integration: Could you provide guidance or potential features within the ABP framework that might streamline the implementation of this offline functionality?

Additional Notes

I understand that initial network requests for authentication and core data are essential for first-time users. My focus is on enhancing the experience for subsequent access when a user is already logged in.

I welcome your insights, suggestions, and potential approaches.
Thank you for your time and consideration!

[AhmadAlMunajjed]

I found out after checking the source code that there is an option called skipGetAppConfiguration to skip calling application-configuration and application-localization requests.

However, for OpenID requests, we need to skip calling authService init. So we need an option similar to skipGetAppConfiguration
that skips calling authService.init() even if authService is injected. Let's call the new option skipInitAuthService

Lastly, after enabling skipGetAppConfiguration and skipInitAuthService, we will be able to write custom implementation to load each request when needed only and to caching its response to be used in later (in office mode).