applaudsplash

Applaud, its here.

Applaud is our inexpensive white-label mobile framework for B2B and B2C.   The pre-developed components in Applaud provide businesses with the foundation needed to quickly build out a custom mobile application on the iOS and Android mobile platforms.

A quick-start into the mobile world.

Applaud is a modular system that consists of seven core (7) modules.   Depending on business requirements, modules can be used standalone or combined to provide a complete cross platform solution from your mobile user to your backend legacy system.

Its important to note that Applaud consists of standard elements and functions fundamentally required by the majority of mobile business applications and as such the framework does not have any of your specific business functions pre-built.  Rather, Applaud is a generic framework that gives you the foundation needed to save on custom development time and lets you focus solely on delivering your business requirements to mobile devices.

Components

The seven (7) standalone components that make up Applaud are:

1.   Server Backend

Clients requiring control or management of their mobile audience can purchase the Backend module. Mobile apps then send tombstone user information collected up to the backend. User information is stored in a backend database (MySQL) for your further use.    From the backend you can send messages to devices, email users and disable users.   User data can also be passed to your bespoke systems via integration customizations.

The backend module consists of four main components:

Admin area – this lists your staff members who can manage mobile user data and enables them to log into the mobile portal.

LOB Area – the framework supports multiple lines of business, if you wish to segment mobile users this feature is available and can be ‘switched on’ at the mobile device.

Mobile Users Area – this section will show you the users have registered and are using your app.   You can delete a user and this will cause the app to fail the login process.

Web Services – we have a suite of underlying web services that are used for user registration, retrieving passwords, sending emails to users, sending push notifications, amongst other things.

Database – The default backend database for Applaud is MySQL.   However, a SQL-Server add-in is available at an extra cost.

2. Mobile Apps (iOS & Android)

Applaud supports both iOS and Android.  For iOS Applaud comes in two versions, one that supports iPhone and one that natively supports iPads. The Android version supports phones and scales up to also run on tablets.

The core workflow and functions of the Applaud framework are:

  1. Users download the app from a link on your website or directly from the iTunes or Google Play stores.
  1. Users are first required to register themselves in the app before they can access the main launch menu of the app.
  1. The registration process consists of the mobile user entering the following data:

First and Last name [mandatory]

Email Address [mandatory]

Mobile app password – this password grants access to the app only. The password is not used to access any of your backend applications. [optional] Note – if the backend module is not being used to process ‘forgot password’ requests a mobile password is not needed

User Photo – A photo upload option is available to allow you to associate an image to the mobile app user. The image is stored in the backend and included with the user detail record for viewing or onward transmission to a client bespoke system [optional].  This function is often used for many financial based applications.

Account Number – If the Back-end module is being used, input and verification of an ‘account number’ will be done via a web service called by the app. The account number is used to filter-out mobile users you wish should not to have access to the mobile app a during the registration process.   For clients not using the backend we provide a ‘hard-coded’ value that is communicated to your audience via email.   If using this filter, a valid account number will be required before the mobile user can proceed to the main menu of the app. [optional]

Geo-Location – we also deliver geo-location data to the backend so you are able to target messaging to the devices by location.

  1. Main Menu (seen after registration or a valid login)

“My Details” Button – takes user to page containing personal information that can be edited.   Updates are sent and stored on the backend if the back-end option has been chosen.

“About” Button – Takes mobile users to a url of your choice. Can be used as ‘how-to’ page or for marketing.   This page needs to be setup by the client in advance and the url given to us.

“Form 1” Button – Currently Applaud shows a “Form Mate” button that takes the user to a client backend login page.   This button would be relabeled and repointed to your URL where your app user would login to your backend web application

“Schedule” Button – A “Schedule” button is shown in the default framework that takes the user to a demo mobile scheduling tool to illustrate a scenario where appointments can be made on the device and sync’d with a backend calendar (iCal format).   This button can be customized to any other URL required, or hidden.

Note:  These buttons can easily be customized and, new buttons added as required.

3. Mobile CMS

Available as an add-on, Applaud has a mobile-optimized CMS system that can be setup and configured on an Apache server.   The CMS content can be maintained via any PC and the pages rendered to the mobile device either via the “About” button, or a new button if required.

The mobile CMS system is a handy add-on in cases where there are instructions or information needed to be available to your mobile user base that you want delivered in a mobile standard.  It does, however, require effort from you to update and maintain.

4. Push Messaging (iOS & Android)

Applaud has the capability to send push messages to iOS and/or Android devices using Amazon Web Services.  Push is integrated with the backend system, however, if the back end is not required, custom web services may be required to deliver this functionality.