What was PhoneGap Build?
PhoneGap Build was Adobe’s hosted service for packaging HTML, CSS and JavaScript applications for mobile devices. Developers uploaded their web application and configuration; the service supplied the native build environment. It was distinct from the open-source PhoneGap framework, the local command-line interface and the mobile Developer App.
The entry points /apps, /plans and the service-status site belonged to that hosted workflow: managing builds, choosing a plan and checking availability. This archive explains those functions. It does not provide an account, build queue or subscription.
Closure and existing accounts
Adobe announced the end of PhoneGap development on 10 August 2020 and scheduled PhoneGap Build to close on 1 October 2020. The announcement asked customers to retrieve stored files by 30 September. The hosted Build product was not released as open-source software. This website cannot retrieve former accounts, signing files or uploaded projects.
Understand the old project structure
| Part | Purpose | What to keep when migrating |
|---|---|---|
| Web assets | The application’s HTML, styles, scripts and images | Original source and build process |
config.xml |
App identity, preferences, plugin declarations and platform options | App ID, version, permissions and required settings |
| Plugins | Native features exposed to JavaScript | Names, exact versions, source and any custom changes |
| Signing material | Identifies an application for installation and updates | Existing keys, certificates and provisioning records |
| Hosted build output | Installable packages produced by Build | Useful for reference; not a substitute for project source |
Continue with a local Cordova project
- Work from a copy of the original project. Record its PhoneGap/Cordova version and target platforms.
- Review the Cordova setup guide and install the SDKs required by the platform versions you choose.
- Create a Cordova project and transfer the application’s web assets into its
wwwdirectory. Preserve the application identifier if maintaining an existing published app. - Review
config.xmlitem by item. Build-specific preferences and plugin declarations are not automatically equivalent to current Cordova settings. - Install compatible plugins, build locally, and test on real devices. Revisit permissions, network access, deep links and signing before distributing an update.
This is a migration sequence, not a promise that a historical app will build unchanged. Custom plugins, old SDK assumptions and third-party APIs may require code changes.
Configuration and plugins
The archive includes the Build config.xml reference and plugin guide. They preserve historical behavior. Use them to understand an old project alongside the current documentation for the replacement toolchain.
Frequently asked questions
Can I sign in or buy another Build plan?
No. The historic hosted service has closed. This archive has no login or payment flow.
Can I download my old app from here?
No. We do not hold former Build uploads or private account data. Look for a local repository, CI archive or backup maintained by the original project owner.
Is Cordova the same thing as Build?
Cordova supplies the open-source application framework and local tooling. PhoneGap Build was a separate hosted packaging service. Replacing one with the other requires setting up a build environment.
Sources & archive notes
- Adobe: Update for Customers Using PhoneGap and PhoneGap Build
- Apache Cordova: Goodbye PhoneGap (14 August 2020)
- Original PhoneGap documentation
- Apache Cordova documentation
Recovered repository material is attributed to its original authors and distributed with its source license. Changes: FreeSoft layout, archive context, navigation, link and image locations. Apache License 2.0 · Notices and provenance. Editorial material is labeled separately.