Discover more from Polywrap's Newsletter
Polywrap – Wrappers vs. Traditional SDKs
Polywrap is a framework for building cross-platform web3 SDKs
The problem with current Web3 SDKs
We see traditional SDKs as the primary bottleneck to web3's potential for composable, cross-platform protocols.
Web3 promises a new depth of composability in software development. Any application can interact with smart contract protocols like Uniswap or Safe. For web3 developers, software development kits (SDKs) simplify this integration process.
However, traditional SDKs come with a number of issues for web3 developers, namely they are:
difficult to compose. Due to the lack of SDK standards, the SDK for one web3 protocol may be difficult to mix-and-match with that of another.
not portable. SDKs are language-specific. With today's deployment platforms becoming more varied than ever (web, mobile, server, etc.), SDK codebases need to be duplicated and translated for each of these environments, leading to more bugs and higher maintenance costs.
not upgradable. When traditional SDKs undergo a patch update, the entire application needs to be rebuilt and redeployed.
Polywrap: composable web3 wrappers
Presenting Polywrap - a framework for building “wrappers”: composable, portable, and dynamically upgradeable SDKs.✨
Polywrap's wrappers offer a much better strategy for code reuse and composability than traditional SDKs. Wrappers are:
easily composable. Wrappers are developed in a standardized way, and all dApps powered by the Polywrap client library can communicate with wrappers with familiar graphQL-esque queries. Standardization means wrappers can be easily composed, resulting in even more sophisticated wrappers.
portable. Wrappers can execute in any host environment that has the Polywrap client installed (web, mobile, IoT, servers, and more). Instead of maintaining multiple language-specific SDKs, web3 dev teams can write one wrappers that can then be reused across all deployment platforms.
updatable on the fly. Wrappers aren't bundled into applications. Instead, they're fetched at runtime and any patch updates are delivered to them on the fly, without the need to rebuild your entire app.
Join us in the future of web3 dApp development!
Thanks for reading Polywrap's Newsletter! Subscribe for free to receive new posts and support my work.