PhoneGap: What It Is, Features, and Building Apps on the Adobe Platform

What Is PhoneGap?

PhoneGap is a platform for developing mobile applications, originally created by Nitobi Software in 2009. In 2011, Adobe acquired Nitobi and released PhoneGap as a commercial product, transferring the framework core to the Apache Software Foundation under the name Cordova.

History and Evolution

PhoneGap was created at the iPhoneDevCamp conference in 2008, where Nitobi Software developers demonstrated the technology of wrapping web applications in a native container. The first public version was released in 2009 and instantly attracted the attention of the web developer community who were looking for ways to enter the mobile market without learning Objective-C.

The main innovation of PhoneGap was that developers could use familiar web technologies — HTML, CSS, and JavaScript — to create applications that install on devices through app stores and have access to native features: camera, GPS, contacts, and accelerometer.

According to Adobe Developer Relations (2015), at its peak, PhoneGap was used by over 600 thousand developers worldwide. The platform was especially popular among web studios and freelancers who wanted to expand their portfolio with mobile projects without hiring iOS and Android engineers.

Differences Between PhoneGap and Apache Cordova

The main difference between PhoneGap and Apache Cordova lies in the distribution model and additional services. Cordova is a pure open-source framework managed by the Apache Foundation, while PhoneGap is its commercial distribution with exclusive Adobe features.

The main advantage and key commercial difference of PhoneGap over Apache Cordova is the PhoneGap Build service, which handles the compilation stage. The developer uploads the source files to the Adobe server, selects the target platforms, and receives ready-made binaries without installing Android SDK, Xcode, or related build tools.

Additionally, PhoneGap included integration with Adobe Creative Cloud, allowing designers to export layouts from Photoshop directly into the PhoneGap project structure. This feature was in demand in small teams without a dedicated mobile developer.

PhoneGap Build: Cloud App Building

PhoneGap Build is an Adobe web service that compiles PhoneGap/Cordova application source code into installation files for iOS (.ipa), Android (.apk), Windows Phone (.xap), and other platforms. The user does not need to install target OS SDKs on their computer.

The build process consists of three steps: the developer archives the project (or points to a Git repository), uploads it to build.phonegap.com, and selects the platforms. Within a few minutes, the server returns ready-made binary files for uploading to app stores.

PhoneGap Build supported two types of subscriptions: free (up to 2 apps, public build) and paid (up to 25 apps, private build, custom icons and certificates). For iOS, an Apple Developer Program signing certificate was required, which the user uploaded to their account. The Build mechanism was simple: the user sent a ZIP archive or pointed to a Git repository, the server automatically determined the platforms and returned ready-made binary files through the control panel.

According to the Adobe Blog (2017), over 500 thousand builds passed through PhoneGap Build monthly. The service was especially popular in educational institutions and hackathons where participants did not have access to Mac infrastructure. Developers also used Build to demonstrate prototypes to clients directly on devices without environment setup.

Code Examples and PhoneGap Setup

The structure of a PhoneGap project is identical to Cordova. The only difference is in the configuration file config.xml, where a element is added indicating the PhoneGap version and the Adobe application identifier.

<?xml version='1.0' encoding='utf-8'?>
<widget id='com.adobe.phonegap.app'
        version='1.0.0'
        xmlns='http://www.w3.org/ns/widgets'
        xmlns:gap='http://phonegap.com/ns/1.0'>
    <name>PhoneGapApp</name>
    <description>
        PhoneGap App
    </description>
    <gap:platform name='ios' />
    <gap:platform name='android' />
    <gap:plugin name='cordova-plugin-camera' />
    <gap:config platform='ios' min-version='13.0' />
</widget>

This configuration file defines an application with iOS and Android support, specifies a minimum iOS 13 version, and includes the camera plugin. When uploaded to PhoneGap Build, the server automatically recognizes these settings and builds the project with the required dependencies.

Example of basic JavaScript code handling the device ready event and calling a native dialog:

document.addEventListener('deviceready', function() {
  console.log('PhoneGap ready to work');

  document.getElementById('btnAlert')
    .addEventListener('click', function() {
      navigator.notification.alert(
        'Hello from PhoneGap!',
        function() { console.log('OK'); },
        'Message',
        'Close'
      );
    });
});

The deviceready event is a mandatory entry point in all PhoneGap and Cordova applications. Without this event, native API calls will not work because the bridge has not yet been initialized. Once ready, all plugins are available, including notification.alert for native dialog windows.

Advantages and Disadvantages of PhoneGap

PhoneGap had a number of advantages that made it popular in the mid-2010s, but also had limitations that led to a decline in its market share after 2018.

Strengths

The main advantage of PhoneGap is the low entry barrier for web developers. HTML, CSS, and JavaScript are technologies that any frontend specialist masters, allowing web development studios to quickly enter the mobile app market without hiring iOS and Android engineers.

The PhoneGap Build cloud service solved the infrastructure problem: Windows teams could build iOS apps without buying a Mac. This was critical for startups with limited equipment budgets.

Weaknesses

The main drawback of PhoneGap is performance. WebView is slower than native UI frameworks, especially with complex animations, large lists, and graphics processing. According to HTML5Rocks tests (2016), rendering a list of 1000 items took 200–400 ms in PhoneGap versus 16–30 ms in a native application.

Additional limitations included dependence on the WebView version on the user’s device, difficulties debugging native plugins, and lack of access to new iOS and Android APIs until corresponding Cordova plugins were released.

PhoneGap Today: Support and Migration

In 2020, Adobe announced the end of support for PhoneGap and PhoneGap Build. The company transferred the developments to the community with a recommendation to switch to Apache Cordova or Capacitor. PhoneGap Build was shut down, and cloud building is no longer available.

For existing PhoneGap projects, migration to Capacitor is recommended — this is a straightforward path with minimal code changes. Simply replace the initialization scripts and update the configuration. All JavaScript code and HTML templates remain unchanged, as Capacitor uses the same bridge principles.

An alternative option is to switch to Apache Cordova directly. This requires installing platforms locally via CLI and setting up local builds, but it fully preserves compatibility with existing plugins and application architecture.

Despite the shutdown, the historical significance of PhoneGap is hard to overestimate. It was PhoneGap that demonstrated to the market that web technologies could be the foundation for mobile applications, paving the way for modern hybrid and cross-platform frameworks. The cloud build concept, first implemented in PhoneGap Build, was later adopted by Ionic Appflow, Visual Studio App Center, and other continuous integration services for mobile projects.

PhoneGap’s architectural decisions — the bridge via WebView, the plugin system, and configuration through config.xml — became the de facto standard for hybrid development. Even in modern Capacitor projects, PhoneGap’s legacy is evident: the same principles of working with plugins and a similar build process.

For developers maintaining old PhoneGap projects, the key skill is understanding the plugin bridge and the ability to adapt plugins to modern Android and iOS versions. Without this, updating the application to meet new store requirements becomes impossible due to outdated system permissions.