You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This checklist is to implement Hubble Bridge V2, as the existing bridge card components in Hubble Bridge need to be upgraded to V2 to enhance the user experience and accommodate improved features and functionality.
Goals:
Improve the visual design and layout of the bridge card for a more intuitive and user-friendly experience.
Adding interactive states to components for improved visual experiences.
Enhance the usability of the bridge card by optimizing the information hierarchy and providing more context on fees, refund features etc.
Address any existing usability issues and pain points reported by users through user testing and feedback.
Please ensure we use proper naming conventions, if naming conventions could be improved within the figma files, please do not hesitate to comment directly within the figma file.
We should establish guidelines for categorizing components as global or local, ensuring that our UI kits are lean, scalable, and robust for better management.
The text was updated successfully, but these errors were encountered:
Overview:
This checklist is to implement Hubble Bridge V2, as the existing bridge card components in Hubble Bridge need to be upgraded to V2 to enhance the user experience and accommodate improved features and functionality.
Goals:
Checklist
Adjustor
component for fixed amounts input to UI Kit #1399Toggle Card
component to UI Kit #1403Status Indicator
component to UI Kit #1407Chain Connection
component #1411Wallet Address
component & add to UI Kit #1414Loading Pill
component for tx status #1456Fee Details
component #1408Selector
component #1406Token List
to include added properties #1412Relayer List
(add radio button) #1413Shielded Pool List
to display network #1457Address Input
component #1410Transaction Input Card
component #1405Switch
component #1415Stepped Progressor
component #1420Transaction Progressor
component #1421Notes
Please ensure we use proper naming conventions, if naming conventions could be improved within the figma files, please do not hesitate to comment directly within the figma file.
We should establish guidelines for categorizing components as global or local, ensuring that our UI kits are lean, scalable, and robust for better management.
The text was updated successfully, but these errors were encountered: