r/ethdev • u/TheWebbster • 7d ago
Question RainbowKit vs AppKit WAGMI vs Anything Else in 2026? What is best, now?
Hi
Stepped away from this area for... well, over a year. Probably more.
Looking to create a basic Dapp, and got up to the point of Wallet Integration.
Hit a bit of a wall with this because it seems it's either
- use Appkit or Rainbow Kit, have to get a "project ID" and analytics, tracking???? Yikes
- use Wagmi/viem and just code all my own other stuff, ui etc
- option 3... ? Not even sure.
What's the standard best practice for simple, easy wallet integration on a website?
Preferably without having to submit a project id, because... Why? It's not a complex dapp and I don't need their integrated RPC/swaps/onramp.
The problem is, if I want people to access via Mobile it seems WalletConnect is like the ONLY method. Is this true?? Because I do not like the idea of tracking/analytics/needing to beg for an ID for people just to get involved with my project. Things are supposed to be DEcentralized...
Thakns all
1
u/hikerjukebox Bug Squasher 7d ago
They each work with Walletconnect you have to set up an API key for separately. They are all good now. I think appkit is the most popular now, along with privy
1
1
5d ago
[removed] — view removed comment
1
u/TheWebbster 5d ago
Thank you for taking the time to write this.
What I am unsure about I suppose, is how many potential users would be likely to need the walletConnect functionality / QR codes and stuff. Personally I would never, but I may not be my users.
But what you say makes sense. Wagmi3 plus viem could be the better/simpler way to go.
1
u/TheWebbster 4d ago
Moderator removed a couple of ACTUALLY HELPFUL comments just because they were from a guy who also makes his own product.
Just because someone makes something, don't remove a USEFUL comment. I came back here to check again what was said and it's GONE.
2
u/gnidan tools guy 7d ago
It's the RPC node access for so many chains. We were supposed to get light clients but now we have three legged auth tokens.
Or you could run a lightweight VPS or Cloudflare thingy to wrap some server side RPC adapter, or give the client direct access to configurable RPC endpoints, etc., but these have tradeoffs.
I do think you can get quite far with the raw EIP-1193 interface and just writing raw RPC requests; it's not hard. I'm not sold on the libraries with all these wrapper abstractions.