Looks like loose language to fit some buzzwords in to me, but I'll give them the benefit of doubt. I'm guessing (hoping) it means either that by consistently u

Looks like loose language to fit some buzzwords in to me, but I'll give them the benefit of doubt. I'm guessing (hoping) it means either that by consistently using their design system, you'll see consistent results no matter the environment (browser, platform, etc.). Another interpretation could be that regardless of the aspect ratio viewed, resolution, etc., content will always render in a relatively consistent fashion regardless of if it's a phone or billboard, so everything is vector based with no rasterization or discrete level of details baked into content. And negative space and what not are all sort of relatively baked in to give the same style. It could also mean that since it's ran client side independent of other clients, you can inherently scale up indefinitely so long as your backend infrastructure can deliver the base content. This of course has been the case in pretty much anything delivered over the internet since its inception though. Of course there was the trend for several years of server side content rendering to enable dynamic content (e.g. the rise of SSI, CGI, PHP, etc.) where scaling was/is more of a consideration but in the current trends of front ends that paradigm seems to be mostly dead and it's just assumed your front-end design will "scale" easily... It's pretty easy to abuse generalized tech terms that are heavily overloaded and not lie while creating all sorts of implications to the reader should they decide to glance over it.