DEV Community

Andreas Galster
Andreas Galster

Posted on

Raise freelance price for hard to find skillset such as Polymer and webcomponents?

We're currently trying to find our first gigs on upwork, I'm super strong in Polymer (webcomponents) and frontend in general. It's a very rare skill because not that many people are doing webcomponents yet and I've been doing it for 4+ years.

I'm wondering if you can raise your prices higher than usual if you do something that's very much in demand, does it work, or does it just scare of potential customers? How do you approach it in the beginning? Should you go with normal rates, or does a specific skillset that's hard to find justify to raise the prices?

WDYT? e. g. meteor developers in the Philippines are paid quite well because it's super hard to find them.


title: "Raise freelance price for hard to find skillset such as Polymer and webcomponents?"
published: true
description: ""

tags: webcomponents, polymer

Top comments (7)

Collapse
 
nektro profile image
Meghan (she/her)

While I lean towards yes, I also wanted to point out that Custom Elements still has very sparing browser support caniuse.com/#feat=custom-elementsv1

Collapse
 
andreasgalster profile image
Andreas Galster

Absolutely, but if someone is looking for a Polymer dev, why not :).

Btw, Firefox is releasing shadow DOM and custom elements in October, so only Edge is left out soon (which you can polyfill technically, although with bad performance hits)

Collapse
 
andreasgalster profile image
Andreas Galster

BTW the light green bar does not mean it's buggy btw, it's just an improved version of custom elements.

Thread Thread
 
nektro profile image
Meghan (she/her)

the light green represents missing features from the spec and FF has them behind a flag

Thread Thread
 
hyperpress profile image
John Teague

That's what polyfills are for, and they're slowly being replaced as specs are adopted by browser vendors. FF just activated ShadowDOM support in their nightly build. Webcomponents moved to NPM module imports, which cleared a big hurdle, and a modified HTML imports spec is still under discussion. So, the color chart doesn't really tell the whole story.

In answer to the fee increase, I already have, and, if anything, I'm turning away work on Polymer PWAs and headless projects.

Collapse
 
darryldexter profile image
Darryl D.

To some degree, you need to find a fit. If people aren't looking for polymer, you cant force them to use it or seek it.

I would instead look at what is currently out there on freelance sites to get a better idea of what type of requests are paying the price you want.

I too am a UI dev and I almost never hear polymer brought up anymore. It's angular/vue/react/ember. Which changes this situation to look at how things are opposed to how they should be or how you want them to be.

Collapse
 
becky_rice_329e1340632e8f profile image
Becky Rice

Raising freelance prices for hard-to-find skill sets like Polymer and web components is a strategic move that reflects the value of specialized expertise in a competitive market. These technologies often require a deep understanding and experience, making qualified developers scarce. By adjusting rates, freelancers can better align their compensation with the complexity and demand of their skills, while also attracting clients who recognize the long-term benefits of investing in top-tier talent. For example, just as a unique menu at chipotle-menu.us/ draws in customers willing to pay for quality, a freelancer with rare skills can command higher rates. This approach not only enhances earning potential but also positions the freelancer as a sought-after expert in their field.