I did back in 2016-17 when v1 web component support came to Chrome. Overall it's an approachable problem and takes quite a bit of time and attention to detail.

I did back in 2016-17 when v1 web component support came to Chrome. Overall it's an approachable problem and takes quite a bit of time and attention to detail. The two significant problems I found are depth of familiarity with Web APIs and the nuance and attention to detail for complete problem solving. The time cost in doing this isn't trivial so it competes with delivering a product on short timelines--which means your MVP delivery might be slower and you might spend less time on design (I have a design background). The most significant secondary observation I've made is how entrenched the community is in these proprietary solutions, and the cost associated with their maintenance over time. The time cost of knowledge and productivity for React, Vue and Angular are similar so in the end the long life of native web api knowledge is the better investment. Since making the product (it automated antibody analysis for routine compatibility profiling in transplant medicine) Lit (LitElement, lit-html) became available and they're so lightweight I use these as often as the native web component mix. It's probably more accurate to say I use them equally because that's just how it works.