Comparing Titanium and PhoneGap

The post compares Titanium and PhoneGap at a high level and argues that their similarities are limited to cross-platform mobile development, JavaScript use, and permissive open-source licensing. It then separates them by purpose, workflow, architecture, strengths, weaknesses, and the broader goals of the companies behind them.

Reading notes

#

• PhoneGap is described as a way to deploy HTML-based web applications as native applications by wrapping them in a native shell and installing them through app stores.
• PhoneGap also tries to expose a common set of native APIs that web apps usually cannot access, such as camera, contacts, and sensors.
• PhoneGap development uses HTML, CSS, and JavaScript files in a local directory, often with browser-based tools, and can be deployed with native toolchains or cloud build services.
• PhoneGap works through a web view that loads the app’s HTML and uses an asynchronous bridge to pass messages between JavaScript and native code.
• Native extensions for PhoneGap require a JavaScript interface, native project registration, and native code that handles requests from the web view.
• The post says PhoneGap’s strengths are its small scope, simple plugin model, and low barrier to entry for web developers.
• The post says PhoneGap’s weaknesses include uneven web view performance, browser compatibility issues, lack of native UI integration, and a limited native API set by default.
• Titanium is described as a high-level JavaScript runtime and API for mobile development that aims to share code where mobile APIs can be normalized while still allowing platform-specific code where needed.
• Titanium is presented as a framework for writing native apps in JavaScript, not as a write-once-run-everywhere abstraction.
• Titanium development uses the native toolchains for iOS and Android, while the developer usually interacts with Titanium Studio or the command line and works with JavaScript source, assets, and configuration files.
• Titanium applications run with native UI components and a JavaScript interpreter, and proxy objects connect JavaScript code to paired native objects.
• Titanium extensions can add both non-visual and UI capabilities by implementing proxy and view proxy interfaces in native code.
• The post says Titanium’s strengths are broad access to native features, the ability to build complex native UI, native look and feel, and lower entry cost for developers already familiar with ECMAScript languages.
• The post says Titanium’s weaknesses are the difficulty of adding new platforms, uneven performance in some UI cases, the current limits of mobile web support, and the non-trivial work needed to extend the framework.
• The philosophical section says PhoneGap aims to become unnecessary as browser standards for device APIs improve, while Titanium aims to remain an enduring platform for native and web targets.
• The post frames Adobe as a tools company focused on the web as a platform, and Appcelerator as a platform company trying to help developers target multiple platforms from one codebase while keeping native features and performance.