Arrk | Enterprise application

Arrk has specific experience in developing thought leading applications utilising a number of architecture models. Applications are designed based on the connection type.

Connection Type

Always connected

Applications that are always connected to back-end servers via the internet or a mobile network. The Key features of these applications are:

• Real-time data processing
• Less dependent on mobile device and OS
• Web applications can be re-purposed to mobile devices
• Secure communication to the server

Partially connected

Applications that process data real-time when connected but also support offline data capture and data storage when the connection is not available. The Local Data Store can be synchronised with the server when the connection is re-established. In addition to always-connected applications the application functionality degrades gracefully and allows it to be used offline to capture data.

Not connected

Applications that are not connected to the server but support offline data capture, validation and processing. The data is synchronised later with the server. Key features of these applications are:

• Not dependant on network or Internet connection
• Application can be tightly integration with the handheld device
• Additional hardware like in-built camera, GPS, Bluetooth accessories can be seamlessly integrated with the application.

Client Device

An application is further architected based on the client. There are many mobile device types including mobile phones, PDAs and Tablet PCs. These devices can typically operate on pocket browsers, thin client and thick client.

Pocket browser based applications

• Accessed via the browser and are generally connected/real-time in nature.
• The applications can utilise the infrastructure of web servers and applications over the Internet for content delivery and data services
• Existing web applications can be re-purposed to cater for mobile devices.
• Secured by SSL certificates

Thin client

• Presentation layer and/or a set of business rules are implemented on the device
• Less device and OS specific than embedded applications.
• A separate detection and rendering logic is developed to determine the device capabilities and render the presentation layer accordingly for the device.
• Secured by SSL or VPN

Thick client

• Standalone applications installed on the device with presentation layer, business rules and business processes that are either validated in real-time with the back-end/database server or are synchronised and validated when connection is available
• The data is captured and stored locally until the connection is made to the server. They are either set to synchronised automatically or manually.
• Secured by VPN