Join Our Email List

 

TapWalk Architecture

 

 


TapWalk’s architecture provides the benefits of a native mobile application (runs without a network connection, responsive user interface, etc) as well as all the benefits of a mobile web application (always up-to-date, easy to change, etc). Our web-based content management and configuration management system allows non-programmers to make changes at any time.

Primary components to the TapWalk architecture:

  1. Web-based admin system: content & configuration management
  2. Web-based analytics system
  3. Data storage “in the cloud”
  4. Native mobile app
  5. Mobile web app
  6. Web-based, RESTful API to allow integration with other systems

 

Admin System (Content Management & Analytics)

Our admin system allows you to control the content published to your mobile app.  Maps, points-of-interests, calendar events and news items can all be added, removed, and modified. The app’s configuration can also be changed from the admin system.  Menu options can be added, removed, or modified and introductory screens can be added, removed, or modified.  Most aspects of the app’s look & feel can be changed.  This allows your app to serve different purposes during different time periods – before, during, and after a major scheduled event for instance. Future releases will allow variable configuration based on different users or user types.

 

Data Storage

Once published by the admin system the data is cached in highly available, high performance, highly redundant servers.

 

Native Mobile Apps

Your custom branded mobile app is based upon a well-tested framework that leverages all the features of each mobile platform. They are “native apps” but can be configured and reconfigured from the admin system. They periodically check for newly published configuration and content data from the data storage.

Mobile Web App

In addition to the native mobile apps, the TapWalk architecture includes a purely-HTML mobile web version. This version serves two primary purposes:

1) Supporting less popular and less powerful phones that lack native apps.

2)Providing an initial experience for smartphone users, who have yet to install the native app. Installation of a native app can be a barrier to users. By providing a mobile web experience we ease the transition from QR code, to mobile web, to native app installation.

 

API

A web-based RESTful API allows integration with other systems.  Data can be read from TapWalk’s admin site as well as written to it.  This allows easy initial load of large amounts of data as well as ongoing synchronization with other systems.

Share!