WebGL, Web-Audio, Web-MIDI, and these other obscure APIs are not popularly a part of front-end development. Front-end development is almost entirely defined by business need which is why a task runner like Gulp is more immediately included under the umbrella of front-end development before WebGL. (I understand Gulp is not required but I’m speaking about the business expectations that exist.)

These APIs I list should fall under a different category. Here is what is unique about the three I list: they are each cross-disciplinary. The average web developer doesn’t touch web-audio because it requires an understanding of digital audio and audio synthesis — who here understands FM synthesis and javascript closures?

Combine these APIs with a knowledge of Javascript and you have a cross-disciplinary practice.

I think this requires some reflection for a few reasons. These APIs are ignored (compared to other parts of front-end development) because they’re improperly framed as just web related technologies. This framing occurs when they’re tossed under the title of “front-end development” but they’re ignored like redheaded step children. They should not be considered front-end technologies anymore since front-end is instantly defined by business pressures.

Let’s acknowledge this: front-end development is 100% defined by business needs and expectations.

In the communities I work in I know many digital audio specialists who don’t even see web-audio on their radar but could offer a lot of knowledge and contribution. I suspect they ignore it because of it’s cross-disciplinary nature. “I’m a digital audio specialist who programs in C. Why do I want to learn Javascript in order to work with audio?”

WebGL has made much more progress for the obvious reason that most users prefer visual experiences rather than audio-based ones. But again, I never see a discussion of webGL in front-end development communities. It’s the cross-discipline curse again. The average Javascript developer is not specialized in OpenGL and has rare incentive to work with that API.

As an artist, designer, and programmer I find these APIs have been kludged into an industry that has little concern over it. I can rarely find anyone to discuss these APIs. Even though some programmers may still hold an ideal definition of front-end development I think we need to consider the reality of the industry.

These APIs need a new category. A new title. Something like Front-End Designer or Front-End Experience Developer or Creative Web Developer. Something.

To clarify, I think a new title is necessary in order to promote those APIs and concentrate a clear community around the category. I want to work with these APIs more for the sake of my own learning and creative practice. I am not driven by business needs as every other part of the front-end development community is.

I have found few people to discuss these APIs. Some people I know who specialize in one of these APIs are not inclined to consider him or herself a front-end developer. Another reason I new category is needed. This is about the creative web.