Web components: the questions we get asked most

The version of this that works is simpler than the version most people imagine. The questions about web components that come up most often on our calls.

The question is rarely whether something can be built, but what it costs to keep running afterwards. The failure mode is not doing it wrong, it is doing it once and assuming it stays done.

Do we need to care about this?

Custom elements work without committing to a framework. In practice this is a scheduling problem more than a technical one. The version that survives contact with a real deadline is the simple one.

Can it wait until after launch?

Occasionally. More often the post-launch version costs several times the pre-launch one. The reasoning matters more than the rule, because the rule has exceptions.

How do we know it is working?

Useful when several teams share one component set. The teams that handle this well are rarely the ones with the biggest budgets. Check it against what you would want a competitor's site to get wrong.

The short version

Code gets read far more often than it gets written, and usually by someone with less context than the author had. Three things worth confirming about web components before you move on:

• Someone can say what the current setup is without going to look
• Custom elements work without committing to a framework — and you know whether that is true here
• There is a way to tell whether the last change to this helped

Most of the value here comes from doing the first two things, not all of them.