Apache Cordova
free software framework for multiplatform hybrid mobile apps

Apache Cordova (formerly PhoneGap) is a mobile application development framework created by Nitobi. Adobe Systems purchased Nitobi in 2011, rebranded it as PhoneGap, and later released an open-source version of the software called Apache Cordova. Apache Cordova enables developers to build hybrid web applications for mobile devices using CSS3, HTML5, and JavaScript, instead of relying on platform-specific APIs such as those in Android, iOS, or Windows Phone. It enables CSS, HTML, and JavaScript code to be packaged for different mobile platform. It extends the features of HTML and JavaScript to work with the device. The resulting applications are hybrid, meaning that they are neither truly native mobile applications nor purely web-based. They are not native because all layout rendering is done via Web views instead of the platform's native UI framework. They are not Web apps because they are packaged as apps for distribution and have access to native device APIs. Mixing native and hybrid code snippets has been possible since version 1.9.
The software was previously called just "PhoneGap", then "Apache Callback".
The public source identifies “Apache Cordova” as free software framework for multiplatform hybrid mobile apps. This brief keeps that definition visible, then builds a research path around Apache, Cordova and free.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Apache Cordova”, the useful work is to connect “free software framework for multiplatform hybrid mobile apps” to the records capable of establishing context and consequence.
The date and method of observation matter as much as the stated conclusion, especially where classification or consensus has changed. The source revision retrieved here is dated Sep 6, 2026. The linked authority identifier is Q16626338. 1 of 1 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 2011.
Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Apache Cordova”, its source revision and the description used here.
- Expand the search: follow Apache Cordova primary sources, Apache Cordova archive and Apache research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Apache Cordova”?
- Is the terminology current, historical or disputed?
- Has classification or technical consensus changed since the cited source?
Search terms from this dossier
This entry incorporates text from “Apache Cordova” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.