Obigo Browser

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Obigo Browser
Platform Cross-platform
Type Microbrowser, browser
License Proprietary, Open Source License
Website www.obigo.com

Obigo Browser started as a micro browser for mobile phones, smartphones and other Mobile Internet Devices (MIDs) developed by the Obigo company. Obigo browser supports various mobile platforms such as Windows Mobile, S60 and BREW. Obigo browser has been evolved to HTML5 application and HMI framework by adapting open source browser engine and other open standards concerning application packaging and security models.

History[edit]

Obigo Browser has been around since 1999, when it was the world's first WAP 1.1 browser, but its development process started in 1998

In 2000, AU-System launched the world’s first WAP 1.2.1 browser, and in 2001, the Mobile Internet Client was the first multi-content and dual stack mobile browser. Obigo MIC became part of Obigo C-line (Mobile Suite 1.0) in 2003, when the Q-line (Mobile Suite 2.0) Obigo Browser appeared as well and the Obigo brand was launched. In 2005, Obigo Browser handled Internet browsing from mobile devices. Obigo is the second mobile browser to pass the Acid2 test. In 2010, Obigo decided to shift to open source Webkit engine and released the first version called W10. The W10 has been rolled out across diverse embedded devices such as feature phone, smart phone, TV and automotive systems. In 2014, Obigo moved to Chromium-based rendering engine and developed the next version named by W20.

To bring HTML5 to Automotive[edit]

There are many operating systems and platforms available for end users that offer various services and applications. Unfortunately these services and applications require different development environments in terms of APIs, compilation and distributions. All these different variables that are available lead to fragmentation in the market place.

HTML5 provides a uniformed way to develop, build and deliver applications, which is managed by a global standardization unity called World Wide Web consortium(W3C). It is also strongly backed by major IT companies such Google and Apple. Native applications are still more prevalent in the application market places but many content providers and developers have begun turning to HTML5 for the purpose of building apps on a cross platform with minimum efforts.

Adopting HTML5 for IVI systems will still bring about some issues such as network latency, system resource limitations for example. Therefore, any HTML5 solution must be highly optimized to overcome these barriers.

Obigo HTML5 Automotive Solutions[edit]

The Obigo design is highly modular in order to provide as much flexibility as possible. The Obigo functionality and scope is reflected in the architecture and also in the process of integrating/porting Obigo products to a target OS. Obigo HTML5 platform consists of three major modules:

  • Browser Engine : Core rendering module based on Chromium Blink and V8 JS engine and 3rd party libraries and optimized to resolve system resource constraints.
  • App Management Service : Application manager to install/execute/delete HTML5 applications
  • Device API : Java script extension module to access and retrieve data from host systems

Each module is connected with well defined interfaces so that they can be easily de-coupled to respond to customers’ various requirements. They also offer strong functionalities of web standards such as HTML5, CSS3, DOM3 and WebGL. In addition to these advantages, Obigo HTML5 platform conforms to GENIVI browser requirements and Web APIs. This is a result of Obigo’s active participation in IVI SW standardization and working closely with global automakers.

Security is one of key functionalities of IVI platform. Applications running on top of IVI platform must be highly secured by strict security mechanism to prevent unauthorized access to system resources or malicious code injection. Obigo’s Widget Access Resource Policy(WARP) allows only certified apps to be installed and executed.

External links[edit]