Our Technology

List of technologies employed in our products 

  • Java client software with pen/mouse optimized user interface components
  • Java server, compliant to j2ee servers or standalone, serving hundreds of device clients
  • RDBMS connected via JDBC, schema supplied by Pocket-Biz. Robust Oracle products as standard option
  • XML exchange interfaces to surrounding systems, including SOA or RMI/Corba

True graphical user interface


Compare these to web applications! Graphical entry of measurement values and localization of defects. These examples highlight the capabilities of a local application. Do not assume, an applet could do the same. It will fail in other domains.

WEB based mobile applications fail completely when dropping their (wireless) connections. Any current work is immediatly lost in many cases. Applet technology is not an alternative, because applets neither support complex persistance, nor survive the exceptions raised on connection loss (session). Excessive loading times occur on each re-start of an applet.

How to solve these conflicts ?

OnlineOffline ?

See our technology discussion about the strategical choices and our conclusions:

Use the mouse to activate the presentation slides. Each click will forward you to the next slide.


You may download this presentation as a PDF file.


in short: The synchronization between devices and server is confronted with a very complex scenario of items on change. Here is one of the application hearts - we use elaborated algorithms to resolve all possible conflicts in order to present consolidated data to the user and the server side applications. With our applications, it is even possible to have more then one user operating on the same data, e.g. on the same work-list. Look at this Scenario:
2 or more devices get the same work order, because their users are working on the same object. Their data will be combined the smart way.  Ask us for details, we can proof this!

Template driven technology

Templates define major parts of the application's behaviour and functionality. Templates are text files in standardized XML format.

Where are the benefits?

The application is generated on server side using the template input and distributed to the clients. This approach has all those advantages, which came up with the web technologies. But it takes a step further, because we now can run the clients even offline, while keeping the central, single point deployment and therefore an inherent update capability for data and code. 


The template finally defines, which user data fields appear with which data, capabilities, constraints and so forth. The server processes it for the database persistance layer and produces the user interface code and data files, which are downloaded on demand to his clients, whenever they touch him.

We provide the best of both worlds: Online and Offline


Components of a typical application

The root components are marked green. We support and integrate the entire environment, if requested.

The term 'MDE client' is used for device applications.


Top of page Recommend page Print version Contact  Accessible Version