blittle

Probably more complicated to setup in a hostile environment because you'd need multiple transmitters, which also need to remain stationary, or at least you need to accurately know when they move.

It calls out O and 0 as unambiguous. I never find an ever so slightly more narrow ellipse to be less ambiguous.

Not a 1% engineer

Lots of e2e tests

This is primarily for embedding in 3p sites, Shopify already has liquid for hosted storefronts. As for search and collections, we don't quite yet have support for search and filters. Though we do support pagination.

I'm on the dev team that built this. Happy to answer any questions!

We essentially use web components as a templating language to dynamically generate a GraphQL query to Shopify. Then render the data as text nodes inside the web components. This is powerful because the components don't include shadow roots. So you can come with your own HTML and CSS.

Most web component libraries are opinionated about design, and give you many CSS custom properties or CSS parts to customize. We tried really hard to invert that, and instead give you the design control. Most of our web components just produce a text node, with no shadow root!

There's a few exceptions, like the cart for example, where it's easier to just have an out of the box component that does it all for you `<shopify-cart>`. Though...you can actually build the entire cart component with the lower level primitives!

You also don't communicate with human language to your lawnmower to get it to work.

I'm a software engineer, but my wife runs a regenerative flower farm. So I'm exposed to both worlds

Agreed, in my opinion the unnecessary emphasis on shadow dom is what prevented web components from gaining more adoption.