Web3 API
Applying the system thinking approach for designing the Notifications centre feature.
Web3 API
Applying the system thinking approach for designing the Notifications centre feature.
Web3 API
Applying the system thinking approach for designing the Notifications centre feature.
Web3 API
Applying the system thinking approach for designing the Notifications centre feature.
Web3 API
Applying the system thinking approach for designing the Notifications centre feature.
Years
Years
Years
2023-now
2023-now
2023-now
Role
Role
Role
Senior product designer
Senior product designer
Senior product designer
Platforms
Platforms
Platforms
Desktop, mobile
Desktop, mobile
Desktop, mobile
Domain
Domain
Domain
B2C, B2B
B2C, B2B
B2C, B2B
Contribution
Contribution
Contribution
UX strategy
prototyping
UI design
UX strategy
prototyping
UI design
UX strategy
prototyping
UI design
Web3 API is Ankr’s leading developer platform, enabling over 8 billion monthly requests across multiple blockchain networks. It offers a single dashboard for managing connections, usage analytics, and performance insights.
Web3 API is Ankr’s leading developer platform, enabling over 8 billion monthly requests across multiple blockchain networks. It offers a single dashboard for managing connections, usage analytics, and performance insights.
Web3 API is Ankr’s leading developer platform, enabling over 8 billion monthly requests across multiple blockchain networks. It offers a single dashboard for managing connections, usage analytics, and performance insights.
TL;DR
TL;DR
TL;DR
Problem
Users missed key updates (e.g., outages, charges) due to email-only communication.
solution
Designed and implemented a centralized Notification Center inside the Web3 API dashboard.
impact
Streamlined workflows, increased user engagement, and achieved a 6.4/7 satisfaction score.
context
context
context
In the Web3 API dashboard, users frequently top up balances, monitor usage, and manage integrations. Timely feedback is critical—especially for:
Network outages
Daily charges
Product updates
Previously, this information was delivered solely via email. But this created gaps in communication—especially for users actively working inside the dashboard.
To solve this, we introduced a dedicated Notification Center that provides timely, contextual updates within the platform itself.
In the Web3 API dashboard, users frequently top up balances, monitor usage, and manage integrations. Timely feedback is critical—especially for:
Network outages
Daily charges
Product updates
Previously, this information was delivered solely via email. But this created gaps in communication—especially for users actively working inside the dashboard.
To solve this, we introduced a dedicated Notification Center that provides timely, contextual updates within the platform itself.
In the Web3 API dashboard, users frequently top up balances, monitor usage, and manage integrations. Timely feedback is critical—especially for:
Network outages
Daily charges
Product updates
Previously, this information was delivered solely via email. But this created gaps in communication—especially for users actively working inside the dashboard.
To solve this, we introduced a dedicated Notification Center that provides timely, contextual updates within the platform itself.
problem
problem
problem
Users had no in-dashboard visibility of critical updates.
Relying on email created friction—users had to leave the product to stay informed.
Engagement dropped, and marketing/product announcements were easily missed.
solution
solution
solution
We designed an in-app notification system that aligned with both user goals and business objectives. Our approach included:
Real-time event-based triggers
Actionable CTAs (e.g., “Top Up Now”)
Clear categorization (System, Marketing, Product)
Personalized preferences via Settings
Designing the System
Designing the System
Designing
the System
Designing the System
Core element
At the heart of the Notifications Center is the notification itself—a concise piece of information designed to convey meaningful details about a specific event. Each notification includes key attributes: theme, content, category, and, if applicable, a call to action (CTA) for any follow-up actions.
Core element
At the heart of the Notifications Center is the notification itself—a concise piece of information designed to convey meaningful details about a specific event. Each notification includes key attributes: theme, content, category, and, if applicable, a call to action (CTA) for any follow-up actions.
Core element
At the heart of the Notifications Center is the notification itself—a concise piece of information designed to convey meaningful details about a specific event. Each notification includes key attributes: theme, content, category, and, if applicable, a call to action (CTA) for any follow-up actions.
Interconnected system
We mapped how notifications are:
Triggered: Events like balance drops, network outages, or manual product launches.
Actioned: Users can act instantly—top up, explore new integrations, or dismiss.
Interconnected system
We mapped how notifications are:
Triggered: Events like balance drops, network outages, or manual product launches.
Actioned: Users can act instantly—top up, explore new integrations, or dismiss.
Interconnected system
We mapped how notifications are:
Triggered: Events like balance drops, network outages, or manual product launches.
Actioned: Users can act instantly—top up, explore new integrations, or dismiss.
process
process
process
Before designing the feature, I kicked off discovery sessions with all relevant stakeholders to gather requirements and understand their unique perspectives. By aligning early with cross-functional teams, I ensured the Notifications Center would not only meet user needs but also serve strategic product and marketing goals.
Stakeholder collaboration
Product Team: Needed a consistent, visible way to announce new features and improvements.
Marketing: Sought an embedded channel to promote new network integrations without relying solely on email.
We co-defined notification categories, structured content standards, and aligned on advanced formatting capabilities (e.g., images, video embeds, rich text).
Before designing the feature, I kicked off discovery sessions with all relevant stakeholders to gather requirements and understand their unique perspectives. By aligning early with cross-functional teams, I ensured the Notifications Center would not only meet user needs but also serve strategic product and marketing goals.
Stakeholder collaboration
Product Team: Needed a consistent, visible way to announce new features and improvements.
Marketing: Sought an embedded channel to promote new network integrations without relying solely on email.
We co-defined notification categories, structured content standards, and aligned on advanced formatting capabilities (e.g., images, video embeds, rich text).
Before designing the feature, I kicked off discovery sessions with all relevant stakeholders to gather requirements and understand their unique perspectives. By aligning early with cross-functional teams, I ensured the Notifications Center would not only meet user needs but also serve strategic product and marketing goals.
Stakeholder collaboration
Product Team: Needed a consistent, visible way to announce new features and improvements.
Marketing: Sought an embedded channel to promote new network integrations without relying solely on email.
We co-defined notification categories, structured content standards, and aligned on advanced formatting capabilities (e.g., images, video embeds, rich text).
Automation vs. manual inputs
A key decision was balancing automation for real-time events (e.g., balance alerts, system incidents) with manual control for high-impact announcements (e.g., feature releases).
To enable this, we planned for a future back-office tool but chose a temporary backend workflow for immediate launch—ensuring we shipped value without delays.
Automation vs. manual inputs
A key decision was balancing automation for real-time events (e.g., balance alerts, system incidents) with manual control for high-impact announcements (e.g., feature releases).
To enable this, we planned for a future back-office tool but chose a temporary backend workflow for immediate launch—ensuring we shipped value without delays.
Automation vs. manual inputs
A key decision was balancing automation for real-time events (e.g., balance alerts, system incidents) with manual control for high-impact announcements (e.g., feature releases).
To enable this, we planned for a future back-office tool but chose a temporary backend workflow for immediate launch—ensuring we shipped value without delays.
Onboarding experience
To introduce the feature, we launched with a Welcome Notification. It outlined the benefits and reduced onboarding effort—no need for a separate tutorial.
Onboarding experience
To introduce the feature, we launched with a Welcome Notification. It outlined the benefits and reduced onboarding effort—no need for a separate tutorial.
Onboarding experience
To introduce the feature, we launched with a Welcome Notification. It outlined the benefits and reduced onboarding effort—no need for a separate tutorial.
results
results
results
Launched: November 2024
Launched: November 2024
Launched: November 2024
6.4 of 7
6.4 of 7
6.4 of 7
satisfaction score
satisfaction score
satisfaction score
User feedback:
Survey via Hotjar yielded a 6.4 out of 7 satisfaction score
Users appreciated reduced friction and real-time visibility
Impact highlights:
Decreased bounce rate during key events
Higher engagement with product announcements
Faster adoption of new network integrations
User feedback:
Survey via Hotjar yielded a 6.4 out of 7 satisfaction score
Users appreciated reduced friction and real-time visibility
Impact highlights:
Decreased bounce rate during key events
Higher engagement with product announcements
Faster adoption of new network integrations
User feedback:
Survey via Hotjar yielded a 6.4 out of 7 satisfaction score
Users appreciated reduced friction and real-time visibility
Impact highlights:
Decreased bounce rate during key events
Higher engagement with product announcements
Faster adoption of new network integrations
"I get updates the moment they happen. Way better than checking my inbox all the time."
"I get updates the moment they happen. Way better than checking my inbox all the time."
"I get updates the moment they happen. Way better than checking my inbox all the time."
— user feedback
— user feedback
— user feedback
Outcomes
Outcomes
Outcomes
Reduced context switching by embedding communication inside the platform
Created a new channel for marketing and feature announcements
Enabled users to act in real time, improving workflow efficiency and trust
This enhancement not only served users’ real-time needs, but also helped the business respond faster to user behavior and market changes.
learnings
learnings
learnings
Designing systems, not features
Thinking holistically uncovered dependencies, ensured alignment, and reduced future risk.
Mapping interconnections reduces blind spots
We avoided missed use cases and created a more robust solution by anticipating both user flows and business needs.
