Button System Design – Libby Mobile App

Hi Nat,

Thanks for sharing your Button System design for the Libby mobile app! You've clearly put some effort into this. I’ve taken some time to review your work in detail and wanted to share a few thoughts and constructive feedback points that I hope will be helpful:

• Platform Alignment (Mobile UX): Since the design is for mobile (iOS/Android), hover states aren't applicable. Instead, mobile interfaces rely on default, focus, pressed, and disabled states — it would be great to see these reflected in your system.
• Destructive Button Colour: The use of burgundy (Libby’s brand colour) for destructive buttons might not be ideal. Destructive actions are typically represented in red, to match platform conventions and signal urgency more clearly to users.
• Primary vs Secondary Contrast: The visual difference between primary and secondary buttons is quite subtle at the moment. Consider using fill vs outline, or more distinct colour contrasts to make the priority clearer at a glance.
• Tertiary vs Link Buttons: The "Tertiary Buttons" look more like link-style buttons. In mobile UI systems, there’s usually a difference between text buttons (which resemble standard buttons without fill) and link buttons (often underlined and blue). Clarifying this distinction would improve consistency.
• Too Many Button Examples: Displaying “Borrow”, “Play Audiobook”, and “Place Hold” separately feels a bit redundant unless you're showing them in context. For a system overview, one generic label (e.g., "Button") per style would suffice — or better yet, include a UI mockup to show them in use.
• Icon and Icon-only Buttons Missing: Mobile UI's often include buttons with icons and icon-only buttons (e.g., arrows, close icons). Adding these variations would round out the system nicely and reflect more realistic scenarios.
• State Completeness: Again, for mobile apps, it's essential to show all expected interaction states: Default / Focus / Pressed / Disabled. Replacing hover with these would better support touch interactions.

Thanks again for sharing this! I’d love to see how these buttons look in actual context, maybe consider adding a few usage examples or mock screens. That would help bring the system to life and highlight how your components support the broader UI.

Keep up the great work!