The Java framework has enabled
TM Mobile to leverage the "write once,
run everywhere" technology to become fully functional across all major desktop platforms
(Windows, Apple Macintosh
and Linux).
TM Mobile departs from a web-based application in that the
desktop client is not browser-based but it is a full-featured
Java-based application that effectively and efficiently communicates and
exchanges customer data with its mobile client counterpart.
In today's disparate computing/smartphone
marketplace, the hardware platform coverage TM Mobile
provides is nearly perfect.
TM Mobile
Design
Each of the elements outlined below play
an important role in forming a cohesive software application
that operates seamlessly across various hardware
platforms:
1.Data
Integrity:
Your data is centrally located on a web server that
hosts TM Mobile on the internet. This data is then accessed
by both the mobile thin client and desktop
client sharing the same data file format to store
information.
2.Data
Security: Access to both mobile thin client and desktop client is restricted by a
shared customer ID and password. The modifiable password and the
static customer ID ensure that your data can travel
across various hardware devices and not be accessible to unauthorized
users .
3.Application
Mobility: The
software application for TM Mobile is highly mobile and
transferable across many devices and platforms. The mobile client
can be accessed from any device with full HTML capabilities.
The desktop client software can be downloaded to any computer
with broadband web access and installed within a
matter of minutes on any of the supported platforms.
For example,
your can edit your data in the
morning in an Apple Mac notebook computer at home then
make desired changes in the field through your Blackberry and once at the
office switch to a Windows-based desktop computer. All of this achieved seamlessly
without any direct data transfer from one device to
another.
4.Hybrid
Application Design:
TM Mobile
is designed to take advantage of the best
of both worlds: the lightness and mobility of a thin
mobile client which makes best use of the limited resources
and restricted form factor of smartphones and the
power and flexibility of a desktop client which
provides the customer with a rich feature
set and expanded functionality generally not within the
purview of a thin mobile client.
5.Segmented
Functionality: The thin mobile client provides a
subset of desktop client functionality and features. This
segmented functionality is purposefully designed to provide
the mobile client with a unique set of features that is
suitable for smartphone's computing power and form factor
restrictions. So while the desktop client serves as the
primary tool for editing and reviewing data, the mobile
client makes data conveniently available on the mobile
platform providing only the editing and updating features the on-the-go customer
needs
.
6.File-Based
Data Storage: TM Mobile data is saved in
a propriety file format that is highly compressed to create
the smallest possible footprint necessary for rapid network
file transfers to and from the desktop environment.
Periodic automatic server uploads ensures that data is
incrementally saved. This "batch" file update methodology reduces the
need for frequent per-record updates that take place in
a database model and necessitate a robust network
connection. In the event of network connection instability, the
data save process is performed to the local media to ensure
data integrity and subsequently re-tried at regular
intervals to update the server when the connection is
re-established.
7.Quasi-Network
Independence:
The file-based
data storage provides quasi-network connectivity independence for
the desktop client. In a client server model,
once the desktop client loses the network
connection, the application has to shut down. Whereas in the TM Mobile
batch model, the application continues working and saving
data locally while it is waiting for the network
connection to be reestablished. In a web-based application that lacks a
desktop client, if the network
connection is down, the application is totally unusable
and consequently you become unproductive on the application (such
as during air travel)
.
TM
Mobile takes into account the inherent nature of today's unstable
network environments and makes you productive outside
of a network accessible environment. Additionally, if you decide
that you do not want to operate outside of
a network active environment in order to fully ensure data
integrity, you can do so by setting an option within
the desktop client to prevent further data editing once
the network disconnects.
8.Multi-user
Facility: The current TM
Mobile application architecture allows multi-user access to data
files stored on the server. The key to data access is the
customer ID and password and once data is loaded into a desktop
or online environment, all other attempts to view or modify
the you data are blocked by the application until the current
session is terminated.