Ionic 3 Mobile app Development Tasks

Technology Stack • Ionic 3 • Angular2 • Cordova 7.0 library for native apps • Typescript • Node.JS • NPM Scripts General requirements - The project’s tasks should be provided in a well-structured ionic project - The project should contain an end user interface that shows the implemented functionalities of each task - The code should follow clean code standards and angular 2 best practices and should be also testable, maintainable. - Documentation for the project setup and also for the complex parts of the apps. Task1: Web API Provider Description: Developing a provider around REST API that can be easily injected in any components or other services as well, the returned provider uses the web request modules to make HTTPs call. It will be mainly used for middleware integration layer, the layer between the mobile app and all the backend systems. Acceptance Criteria - Wrapper should be easily created with the minimal configurations - The wrapper should handle the following features but not limited to: o Authentication ( OAuth 1.0 & 2.0) o JSON request and response formatting o API Errors Handling Task2: Local Storage Provider Description: Developing a provider around local storage that can easily inject in angular components, the returned provider uses the low-level mobile APIs to manage the read/write operations into/from the local storage. Acceptance Criteria - Provider should be easily created with the minimal configurations - Local storage will a key/value repository - Apply encryption/decryption from the App layer to protect local data - The provider should handle the following basic operation but not limited to: o Add o Update o Delete o Query Task3: Caching provider Description: Developing caching manager which will have injected dependency of Storage Provider described in the previous task, The returned providers defines the rules that govern the data in the app. Acceptance Criteria - Cache provider should re-use the storage provider described in task2 - Cache provider should provide the following features but not limited to: o All cached objects will be stored in the Local DB through the storage provider created in the previous task o Each cached object will be tagged with this information (“StoredAt” Datetime, “LastRetreival” At Datetime, “ValidFor” TimeStamp ) o Retrieving only object value along with state (valid or invalid) by key. o Retrieving Object regardless of state by key Task4: Middleware provider Description: Developing Middleware provider that manages the business APIs calls and apply caching defined rules for each API according to the business rules. It should re-use both Web API & Cache base providers described in task1 & task3. Acceptance Criteria - Middleware provider that can be easily injected in services and components. - Middleware provider should encapsulate all Middleware web APIs calls in a way that support the below rules o Any Middleware web API call will be wrapped in a function in the provider and can be tagged configured with the following cache attributes if required  CacheEnabled - bool  RefreshInterval – Timestamp  Lastretreivetimestamp- timestamp o For any request from the presentation layer for Middleware provider’s function (if tagged as cached) will retrieve the result directly from storage provider even if it was invalid and to return along with the result another promise that retrieve the fresh copy of the data. This will allow the presentation layer to display the cashed value until it receive the fresh copy and update the UI. o The middleware provider should be injected at the app level where there will a function called once that execute a logic regularly at certain time interval that call Middleware API retrieves a list of cached objects needs to be immediately refreshed through a middleware API and action the response by invalidating or purging (will be decided later) these list of object in the local storage.