You're offering a fantastic brand new service, and it'll revolutionize your customers' world! Because it's smart, it delivers an API-first solution wrapped in an edge architecture. And because you're smart, you're offering to your end-users several SDKs to let them use those APIs at their full potential: PHP, Java, Ruby, Go, Python, JavaScript… Wait, JavaScript? When entering the world of frontend architecture in an API-first world, we should take time to answer this simple question: SDK or Web Components? The frontend world comes with a UI-first paradigm, so should we switch our mindset? [color=#111111][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][size=2][font=Verdana, Arial, Helvetica, sans-serif][h2][/font][/size][/font][/size][/color][/color][b][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][url=https://m4dz.net/t/sdk-vs-wc/#/11]Slides[/url][/font][/size][/color][/font][/size][/color][/b][color=#111111][color=#111111][size=2][font=Verdana, Arial, Helvetica, sans-serif][size=2][font=Verdana, Arial, Helvetica, sans-serif][/h2][/font][/size][/font][/size][/color][/color] On the other hand, Web Components now have a mature ecosystem where you can build advanced UI elements that already embed all the logic they need. API-first backend only requires HTTP streams, and Web Components embed the required network primitives. Should we distribute a JS SDK or a library of Web Components for our service? Here's the match between the two giants! SDKs vs Web Components: Place Your Bets.