Basics

A guide to building Mybring and related properties with shared principles and code

Users’ interfaces, maintainable code

Our goal is to meet users’ needs and preferences.

That means:

• Design lead by reasoning and choices before aesthetics or style.
• We use browser defaults, interface conventions and native elements for what they are worth.
• We avoid inventing our own interface flavour.
• We aim to control as little as possible of people’s environment.
• We lean on the platform languages of the web and have a sober approach to making custom elements and using ephemeral dependencies, libraries and frameworks.
• When circumstances call for custom elements or deviation from certain principles, we still work from the native patterns.

That leads to:

• Offering usability and accessibility without having to overengineer or compensate for choices made elsewhere.
• Less code written.
• Easier maintainability for years to come.

This is for instance noticable in the form elements. They are made to not break with affordances and conventions. The default focus outline is kept so it works with people’s settings, whether that be different colours or extra contrast; whatever they need to perform their task.

System content

• Documentation with principles, guidelines and code reference
• Mybring Design System CSS
• Icons
• A handful of React components
• Chart.js config
• Mybring Prototype for prototyping new user interfaces
• Sandbox CSS for testing new features behind a canary flag
• GitHub repo