SnapComms Architecture

 

From an architectural perspective, the SnapComms solution consists of three components: the SnapComms Cloud Server, SnapComms Desktop App and SnapComms Mobile App.
 

CLOUD SERVER

The Cloud Server provides business logic and interfaces for the communication with Desktop and Mobile Apps as well as the web-based Content Manager app for Content Administrators. Desktop Apps poll the Cloud Server every 120 seconds over HTTPS/TLS connection, asking for new content and reporting the readership status. Mobile Apps also connect to the Cloud Server over HTTPS/TLS but only on request when the app is opened by the mobile user. Large content is delivered through CDN which improves the latency and ensures that large messages can be delivered to end users more quickly.

DESKTOP APP

The Desktop App is a tiny piece of software that needs to be installed on each desktop or notebook that should receive messages published via SnapComms. It runs in the background and periodically (every 120 seconds) connects to the Cloud Server over HTTPS/TLS through the TCP port 443. The desktop client is responsible for the following tasks:

• Collecting AD information about the currently logged-in user and transferring it to the SnapComms server (this topic is detailed in the Importing from Active Directory article)

• Receiving content and displaying it to the user

• Reporting readership status back to the server

MOBILE APP

This is a Mobile App for iOS or Android-based devices that needs to be installed on each mobile device that should receive messages published via SnapComms. When new content is published, the mobile apps are notified using the notification services of Google and Apple. Google’s GCM is using TCP ports 5228, 5229 and 5230 and Apple’s APN is using TPC ports 2195, 2196 and 5223. The Mobile App is responsible for the following tasks:

• Receiving content and displaying it to the user

• Reporting readership status back to the server