FreeSoft
English EN

History & articles

Moving Forward — PhoneGap’s 2017 direction

An editorial summary of the PhoneGap team’s discussion of web standards, plugins and progressive web applications.

Editorial archive guide29 May 2017 · Simon MacDonald
Archive note. Historical reference. PhoneGap tools and the former Adobe services are no longer maintained as described in the original material. Recovered text and newly written explanations are identified below; consult current platform documentation for active development.

What the article discussed

In May 2017, Simon MacDonald revisited PhoneGap’s original purpose: let web developers create applications across mobile platforms while filling gaps in browser capabilities. He explained that some early plugin APIs had diverged from evolving web specifications.

The team proposed reviewing those APIs against newer W3C specifications. The questions were practical: which plugins were still needed, which should change, and which capabilities belonged in the platform itself. The post linked that work with progressive web applications and continued packaging of web applications where native distribution was useful.

Read the original

Moving Forward, by Simon MacDonald preserves the author’s complete argument and original references. This page is a summary, not a reproduction.

Sources & archive notes

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.