1/ 🧵 We’ve reimagined our SDK to better serve web3 developers—especially those building mobile-native onchain apps. Here's what we learned and how we improved 🛠️:

aggregated blockchain scaling ethereum with zk tech.

2/  Initially, we tried to abstract away all web3 complexity: tokens, contracts, transaction building, etc. Our goal? Empower any developer, even without web3 experience. 🚀

But real-world feedback from early builders on @0xpolygon and @base told a different story. 🧵👇

3/ 🧐 Most developers already understood the basics of web3 (tokens, contracts). The bigger challenge? Handling mobile-first constraints like unreliable networks and high latency.

5/ 🚀 Solution? Shift to pre-baked configurations at build time. Instead of fetching data dynamically, we embed static blockchain data (e.g., token decimals) directly into the SDK. The results speak for themselves:

6/ 🏎️ Faster performance: Transactions now build seamlessly without waiting on RPC calls.

🛡️ Better reliability: Fewer network dependencies mean fewer failures.

📱 Mobile-optimized: Lower resource use = better user experience.

7/ 🔒 Why does this work? Blockchain contracts are immutable, so pre-baked data remains valid.

For edge cases, we built web tools to generate configs for devs who need custom setups. ⚙️

8/ 🌟 This journey taught us a lot about designing tools for mobile-first blockchain devs:

1️⃣ Simplifying workflows is good.
2️⃣ Prioritize mobile performance.
3️⃣ Iterate based on real-world needs.

9/ We’re excited to see what the dev community builds with this improved SDK, especially now that we’re on 
@base
! What’s your take? Drop your feedback below—we’re always evolving. 🚀

10/ Read the whole blogpost below:

https://blog.rallyprotocol.com/redesigning-our-sdk-a-journey-to-optimize-for-mobile-web3-developers

4/ ⚡ Our old approach relied heavily on RPC calls (e.g., fetching token decimals, EIP-712 salt). This simplified dev workflows, but created big issues for mobile users:

- Higher latency 📈
- Increased failure rates 🚨
- Resource-heavy operations 🔋