Problem: dApps today are set up to fail
Most dApps today have user retention and engagement problems.
Web3 notifications suck.
As developers, we spend a lot of time, effort and money building dApps and acquiring users. But we don’t have a good decentralised way to continually engage them; to notify them of events that require their attention, or encourage habit-forming behaviours.
Right now, notifications suck for users and developers
Without notifications, users must remember to constantly log back into your dApp to see if anything has changed, while following a Twitter and/or Discord for alerts. This is an extremely poor user experience, especially relative to Web2 expectations.
If Web3 developers want to use email, SMS or push notification services in our dApps, we’re forced to build centralised off-chain services to manage this for us. This both adds development overhead and also introduces points of failure.
So, as developers, how do we send notifications in the most decentralised way possible, without having to set up lots of new infrastructure?
With the IC’s HTTPS Outcalls feature and upcoming cross-chain integrations, we are creating a decentralised, secure notification service for developers building dApps on any chain, starting with IC.
Creating a Web3 Notification Service (W3NS)
I’m part of a team that’s solving the Web3 user retention and engagement problem.
We’re an Aussie Web3 development studio focused solely on helping developers build better on the Internet Computer.
With the IC’s HTTPS Outcalls feature, Internet Identify authentication and upcoming cross-chain integrations, we are creating a decentralised, secure notification service for developers building dApps on any chain, starting with IC.
Engage users with email HTTPS outcalls
We’ve just released our first product on the IC - an email notification service built with HTTPS outcalls.
Developers can now use this to engage users with transactional emails straight from their IC canisters.
We are using Courier’s idempotent API to make HTTPS calls. Courier then allows developer to configure their email provider of choice (e.g SendGrid, Gmail or SES) to send user emails.
Check out our demo video on Loom
Or watch our full IC Community pitch on YouTube
Right now we’re sharing a demo app you can use to send emails. However, our short term goal is to build an Open Internet Service that’s easily accessible by builders on any chain and supports:
- SMS & Push notifications
- Notification scheduling & flow designer
- Automations based on events and user behaviours
- Cross-chain notifications email, SMS and push notifications
Our end vision is a full-stack Web3 marketing and user-engagement platform.
Try it out!
Want to try our email notification service? You can access the code here and integrate into your own app:
We’d love your feedback! Are there other features you’d like to see, or do you have a cool idea? Let us know in the comments
Find out about Argon Studios here: https://www.argonstudios.xyz/