Web Browser as an Application Platform

Taivalsaari, Antero; Mikkonen, Tommi; Ingalls, Daniel H. H.; Palacz, Krzysztof

doi:10.1109/seaa.2008.17

Cited by 58 publications

(35 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Such problems could be alleviated by introducing a more fine-grained security model, e.g., a model similar to the comprehensive security model of the Java SE platform [1] or the more lightweight, permission-based, certificate-based security model introduced by the MIDP 2.0 Specification for the Java Platform, Micro Edition (Java ME) [4]. As already pointed out in [6], the biggest challenges in this area are related to standardization, as it is difficult to define a security solution that would be satisfactory to everybody while retaining backwards compatibility.…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

Lively3D: Building a 3D Desktop Environment as a Single Page Application

Voutilainen¹,

Mattila²,

Mikkonen³

2014

Acta Cybern

Self Cite

View full text Add to dashboard Cite

The Web has rapidly evolved from a simple document browsing and distribution environment into a rich software platform, where desktop-style applications are treated as first class citizens. Despite the associated technical complexities and limitations, it is not unusual to find complex applications that build on the web as their only platform, with no traditional installable application for the desktop environment -such systems are simply accessed via a web page that is downloaded inside the browser and once loading is completed, the application will begin its execution immediately. With the recent standardization efforts, including HTML5 and WebGL in particular, compelling, visually rich applications are increasingly supported by the the browsers. In this paper, we demonstrate the new facilities of the browser as a visualization tool, going beyond what is expected of traditional web applications. In particular, we demonstrate that with mashup technologies, which enable combining already existing content from various sites into an integrated experience, the new graphics facilities unleashes unforeseen potential for visualizations.

show abstract

Section: Discussionmentioning

confidence: 99%

“…The World Wide Web has undergone a number of evolutionary phases [6]. In the first phase, web pages were truly pages, and navigation between pages was based simply on hyperlinks -a new web page was loaded from the web server each time the user clicked on a link.…”

Section: Introductionmentioning

confidence: 99%

Lively3D: Building a 3D Desktop Environment as a Single Page Application

Voutilainen¹,

Mattila²,

Mikkonen³

2014

Acta Cybern

Self Cite

View full text Add to dashboard Cite

show abstract

“…With respect to location data, the notion of utilizing client geographic location to customize web media has been around for at least a decade and in the last few years HTML5 and related technologies have significantly extended standardsbased support for a large number of useful features that promote the web as a first class application platform [13,14].…”

Section: Mobile App and Mobile Web Appmentioning

confidence: 99%

Accuracy, Security, and Architecture Impacts and Challenges of Mobile and Web Technologies: Geolocation Field Data Collection in Washington State Water Resources

Miller¹,

Chung²,

Escrig³

et al. 2014

IJCA

View full text Add to dashboard Cite

The purpose of this paper is to examine accuracy, security, and architecture impacts and challenges of mobile and web technologies through the case study of collecting geolocation field data in Washington (WA) State water resources. Effective management of water as a public resource relies on the capture, storage, and retrieval of accurate geographic position data. This is also true of a broad range of business domains beyond water resources, such as earth sciences, city planning, and navigation to name a few. Application developers must choose how to capture this information (with enough accuracy to be useful for its intended application) and get that data to a place where it can be processed and used. A traditional monotonic application using a Global Positioning System (GPS) and a mobile app using a smartphone are available today. The advent of HTML 5 now allows the development of a mobile web app, which is not dependent on any particular smartphone platform. These multiple technical options lead to two research questions: How does an HTML5 mobile web app solution work in terms of accuracy, security, and architecture, compared with a GPS-based solution and a mobile native app solution for collecting geolocation field data? And second, as HTML5 mobile web apps are a relatively new technology, what best practices can we uncover to assist in the process of choosing between an HTML5 mobile web app and a mobile native app, and also what are the best practices for building a mobile web app that can operate offline? To answer these questions, we build an HTML5 mobile web app called "LocationSharpener" for collecting GPS locations leveraging three of the new HTML5 features: IndexedDB, AppCache, and GeoLocation. We use the mobile web app to collect locations of water resources facilities like wells and diversions and analyze how accurately the app collects the geolocation data. We apply threat risk modeling to the mobile web app to analyze its security and privacy compared to that of the native mobile app approach. In addition, by documenting the architecture of the mobile web app with multiple views, we analyze how HTML5 affects the architecture and present best practices for building a mobile web app that can operate online and offline. The analysis of location accuracy shows the HTML5 mobile web app approach provides acceptable location accuracy even when offline. Threat modeling demonstrates that, in contrast to native mobile apps, mobile web apps offer a clear advantage to users and developers: an isolated execution environment makes it more difficult for a malicious mobile web app to read private data; As an outcome of the architecture documentation we also propose new best practices of developing a mobile web app using HTML5: the developer must consider two subsystems for online and offline use cases and a sequence of connected, disconnected, and connected deployment modes. Also, standards-based web apps are portable across virtually any operating system. This also eases the burden on developers, since ...

show abstract

“…With the increasing number of mobile devices such as smartphones and tablets [4] and declining support for many once-popular universal runtime environments [7], the Web emerges as a leading platform for device-independent applications [8,9]. Therefore, most of the current research on deviceindependent applications is focused on various aspects of Web applications: from differences among Web browsers [10], to new HTML5 APIs, CSS3 properties and crossbrowser Java Script libraries that try to unify [11] and enhance Web browser behavior [12], to new server-side frameworks [13].…”

Section: Device Independencementioning

confidence: 99%

Device-Independent Architecture for ubiquitous applications

Chmielewski

2013

Pers Ubiquit Comput

View full text Add to dashboard Cite

The part of the Internet of Things composed of devices that directly interact with users has grown considerably in the past years. With new smartphones, tablets and other Internet-enabled devices that appear on the market, this trend is still increasing. However, existing application development processes and tools, designed for single device applications, do not allow developers to fully and efficiently address this opportunity. Applications are developed for a particular type of devices or a particular programming platform. This limits the number of potential users and makes it difficult to seamlessly use an application on multiple devices owned by users. To take full advantage of the Internet of Things, applications should be able to run on any device-they should be ubiquitous. In this paper, we present a concept of Device-Independent Architecture, which provides separation of applications from devices and facilitates development of device-independent applications. Additionally, the separation introduced by the DeviceIndependent Architecture enables implementation of multidevice scenarios where a single application employs multiple devices at the same time. The experiment described in the paper proves that such device-independent applications indeed may be used on any suitable device-they have a chance to become ubiquitous.

show abstract

Web Browser as an Application Platform

Cited by 58 publications

References 4 publications

Lively3D: Building a 3D Desktop Environment as a Single Page Application

Lively3D: Building a 3D Desktop Environment as a Single Page Application

Accuracy, Security, and Architecture Impacts and Challenges of Mobile and Web Technologies: Geolocation Field Data Collection in Washington State Water Resources

Device-Independent Architecture for ubiquitous applications

Contact Info

Product

Resources

About