Handling backtracking in Web applications

Abstract

Abstract

Visual history mechanism on mobile internet browser

“…The users' interests of obtaining the piece of information omit the presentation of other trivial data. As screen space is scarce on a handheld device [6,3,15], this in turn causes visualisation more difficult to be implemented. The ML2DSS [21] utilises the space by displaying a large pool of overlapping and related data.…”

“…Due to the limited processing capabilities [6,3,15], the devices are not able to run applications that are resource-consuming. Therefore, the mobile financial application system [23] adopted a 3-tier architecture, whereby the processing and data retrieving are executed on normal web servers.…”

“…Conversely, most of the mechanisms reviewed provide only limited functionalities for users to navigate through the history list. Keeping a thumbnail for every webpage visited is memory consuming [3] and the current mobile technology might have difficulties in handling it. Furthermore, visual history mechanism is graphical intensive, where it somehow slows down the application [15] as new nodes is drawn and added to the current list or tree.…”

“…However, the small size of the mobile devices leads to one technical limitation, which is small screen size [6,3,15,9]. Although Internet offers abundance of information, the issue of displaying the results remains a problem [8].…”

Modelling Safe Interface Interactions in Web Applications

“…For example, Milic et al [1] study the different problems that can occur in the context of back navigation and have proposed a specific solution called Smartback. Alternative approaches have been proposed [17,18,19]. To address the problems identified by these authors in a generic and model-based design method is precisely the goal of our method.…”