Skip to content

[Packages] Component/UI libraries? #12

@spen

Description

@spen

Let's use a set of components already built by the open source community.
This'll save us a bunch of time and let us spend that time on making our app awesome.
It'll also give us other benefits such as knowing the code is usually vetted and scrutinised by the community... a software package with an active community is often well tested and documented by the community itself, who will be contributing their efforts to maintaining and improving it. That would include things like accessibility, imagine a blind person digging our app because it's easy to play? Very cool 🤙

That said, we can totally iterate on this approach and even start building our own component sets and libraries and replace the 3rd party stuff with our own. This might be useful to do as we start needing more varied components for our needs.

Options

Here are some options that I've used in the past:

Also, feel free to do a bit of current research and make a suggestion! This is a field that moves constantly and the community is always improving its consensus on how UI should be (not that there are rules, of course).

Some relevant reading

https://www.getopensocial.com/blog/open-source/advantages-component-library#:~:text=Working%20with%20a%20component%20library,collaboration%20with%20front%2Dend%20development.
https://dev.to/domysee/benefits-of-a-component-library-2baa
https://dev.to/graphqleditor/5-react-ui-libraries-you-need-to-check-out-in-2020-2g6o
https://blog.bitsrc.io/13-top-react-component-libraries-for-2020-488cc810ca49

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions