Thin Client - Bambookit GUI Benefits.


Increase End-User Productivity
and Save your Costs

Features Benefits Demo Widgets Set Purchase FAQ IDE
Lower development costs dramatically XML-based environment enables existing web developers to quickly build Bambookit applications. No compilation required, use existing skills and tools. Fast and responsive applications delivered cost-effectively in a fraction of the time of traditional web application. Easy to deploy No downloads, plug-ins or client side installations are required to view web applications built with Bambookit. Bambookit downloads dynamically within standard browsers. It is an ultra thin client that easy to deploy from a central server and easy to upgrade and maintain. XML files are deployed on the server and loaded as needed.

Responsive performance Bambookit adds value to end-users through responsive performance. Bambookit overcomes limitations of the "click-wait-refresh" model associated with HTML that requires a new page to travel from the server to the browser upon every user click. This refresh process can take precious seconds, and often minutes and significantly frustrates end user productivity.
Interactive User Experience Bambookit adheres to the principle of feedback through visual cues on any control that can manipulate the user interface environment. All controls that can be acted upon would highlight on a mouse rollover, mouse click and mouse release. Reduce Bandwidth by 90 percent Bambookit eliminates unnecessary communications between client and server of the "click-wait-refresh" model associated with HTML. The "click-wait-refresh" model also weighs heavy on the network infrastructure, with each page occupying a footprint of kilobytes - most of which is redundant. Concise, Bambookit's XML-based instructions are so thin that they reduce bandwidth use by up to 90% over HTML.
Read White Papers
Cross-device From PCs, to handheld devices, to any Internet terminal Bambookit based thin client applications will run equally well on different environments: operating systems, browsers, webpads, mobile phones. There is no need to rewrite the application for every device. For end users, applications look, behave and perform the same, regardless of their access means and connection.
See Architecture.

[Home]

[Home]