Web3 EdTech Platform — UX-Focused Frontend & API Co-Design
A 0-to-1 product build where the frontend role extended beyond implementation into UX alignment, API endpoint co-design, and data model coordination. The work was delivered as part of a small async team building an early-stage learning platform.
Overview
A 0-to-1 Web3 EdTech platform where I led the frontend while also helping shape API structure and data flow decisions. The project required making a technically complex flow, from wallet connection to certificate issuance, understandable and usable for non-technical users.
Context
This was the platform’s first public release, and it already included complex Web3 interactions and certificate issuance logic. Because the target users were not necessarily technically confident, the onboarding flow needed to feel clear, stable, and trustworthy despite the complexity of the underlying system.
Challenge
The core challenge was to keep a Web3-heavy onboarding journey understandable for non-technical users while working in a fast-moving async startup environment with evolving specifications.
- Keep wallet login and certificate issuance connected as one user journey
- Reduce friction for users unfamiliar with Web3 tools
- Handle failure states and re-entry points without breaking trust
- Align frontend behavior with evolving backend and product decisions
Contribution
- Built the frontend with reusable and scalable UI patterns
- Co-designed API endpoints and adjusted schema decisions to match frontend UX and data needs
- Integrated wallet connection and certificate issuance with a focus on trust and clarity
- Handled edge cases such as failed transactions, network mismatch, and user re-entry
- Used structured async documentation and flow diagrams to keep evolving decisions aligned
Outcome
- The onboarding flow from wallet connection to certificate issuance became more stable and easier to follow
- The frontend was structured for future feature expansion
- Cross-functional alignment remained workable despite time zones and evolving requirements
- Fallback UX and trade-off proposals helped the team keep momentum under uncertainty
Notes
- This project shows how frontend work in an early-stage product often extends into API design, data flow, and decision-making support
- A major part of the value was not only shipping UI, but turning moving requirements into a workable product flow