Mind the gap
Tags: phonegap, libraries, frameworks, design
Published: 2020-08-26 12:05:28

---
title: Mind the gap
published: true
date: 2020-08-17 13:31:33 UTC
tags: phonegap,libraries,frameworks,design
canonical_url: https://adactio.com/journal/17309
---

In May 2012, Brian LeRoux, the creator of PhoneGap, wrote a post setting out the [beliefs, goals and philosophy](https://phonegap.com/blog/2012/05/09/phonegap-beliefs-goals-and-philosophy/) of the project.

The beliefs are the assumptions that inform everything else. Brian stated two core tenets:

> 1. The web solved cross platform.
> 2. All technology deprecates with time.

That second belief then informed one of the goals of the PhoneGap project:

> The ultimate purpose of PhoneGap is to cease to exist.

Last week, [PhoneGap succeeded in its goal](https://blog.phonegap.com/update-for-customers-using-phonegap-and-phonegap-build-cc701c77502c):

> Since the project’s beginning in 2008, the market has evolved and Progressive Web Apps (PWAs) now bring the power of native apps to web applications.
> 
> Today, we are announcing the end of development for PhoneGap.

I think Brian was spot-on with his belief that all technology deprecates with time. I also think it was very astute of him to tie the goals of PhoneGap to that belief. Heck, it’s even in the project name: Phone_Gap_!

I recently wrote this about [Sass and clamp](https://adactio.com/journal/16887):

> I’ve said it before and I’ll say it again, the goal of any good library should be to get so successful as to make itself redundant. That is, the ideas and functionality provided by the tool are so useful and widely adopted that the native technologies—HTML, CSS, and JavaScript—take their cue from those tools.

jQuery is the perfect example of this. jQuery is no longer needed because cross-browser DOM Scripting is now much easier …thanks to jQuery.

Successful libraries and frameworks point the way. They show what developers are yearning for, and that’s where web standards efforts can then focus. When a library or framework is no longer needed, that’s not something to mourn; it’s something to celebrate.

That’s particularly true if the library of code needs to be run by a web browser. The user pays a tax with that extra download so that the developer gets the benefit of the library. When web browsers no longer need the library in order to provide the same functionality, it’s a win for users.

In fact, if you’re providing a front-end library or framework, I believe you should be actively working towards making it obselete. **Think of your project as a polyfill.** If it’s solving a genuine need, then you should be looking forward to the day when your code is made redundant by web browsers.

One more thing…

I think it was great that Brian documented [PhoneGap’s beliefs, goals and philosophy](https://phonegap.com/blog/2012/05/09/phonegap-beliefs-goals-and-philosophy/). This is exactly why [design principles](https://principles.adactio.com/) can be so useful—to clearly set out the priorities of a project, so that there’s no misunderstanding or mixed signals.

If you’re working on a project, take the time to ask yourself what assumptions and beliefs are underpinning the work. Then figure out how those beliefs influence what you prioritise.

Ultimately, the code you produce is the output generated by your priorities. And your priorities are driven by your purpose.

You can make those priorities tangible in the form of design principles.

You can make those design principles visible by publishing them.