TCS PWA Architectural Suggestions
TCS PWA Architectural Suggestions
TCS PWA Architectural Suggestions
Jan, 2020
2
1b Environment Setup
3
2a Functional Architecture
Sales
Representative Upload / Update Case Records / Reports Video Local SQLite
PWA
Documents (.pdf)
APIs
• Product
Catalogue &
description
APIs • Characterises
Description
• Images
• Technical
Insights
Images
Content (Showpad) Service Worker
Azure SQLite
Physicians
4
2b Technical Architecture
PWA Application
Functional Components Mobile Backend
Case Procedures Middleware APIs Data
Clinical Ablation
Login Sales Rep Records / &
Cases Size
Home Reports Documents
c
UI/Presentation Layer
(Ionic Framework) Data Content Ablation
Offline
Rendering Rendering Algorithm
5
2c Integration Architecture
Showpad APIs
Security Management Rest API
Clinical Case,
Record, Report, Rest API
Orchestration Showpad Storage Showpad
Details
Synchronization • Brochure
• Tech docs
e Rest API • Image
Rest API • Procedure
Ablation Data Azure APIs Videos from
Azure API different
Rest API doctors
Rest API Authentication • Case Records
Authentication API Reports
6
3a Without Service Worker application work model
1. Request
3. Get Data
Depend on network connection!
2. Response
Browser
Server
7
3b PWA Work Model
Local Network
1.Request
3. Return the Data
5.Response
Browser
Service Worker Online
Cache
8
3c PWA Work Model
Local Network
Request
Server
Cache
9
4 PWA Workflow
• App Shell: Fast Loading, Host Pages, Help provide native experience
Overview • App Manifest: Home Screen icon, App like experience
• Service Worker: Offline Experience, Cache
Request
App Service
App Shell
Manifest Worker Response
11