Ask DN: Creating personal UI Frameworks, advice please!

over 6 years ago from Sam Garson, Designer Developer in London

  • Nick MNick M, over 6 years ago

    Done something similar a couple of times. What I'd suggest is building your UI components AFTER you've done your design work (wireframing, etc).

    Do a pattern inventory first, after you know what your functionality and general screen design looks like, and you will be able to keep yourself honest as you move along. I'm a big fan of combining SMACSS for my code and Brad Frost's Atomic design for UI principles. It helps to categorize your patterns and then really look at them with a discerning eye to understand the differences in behavior (which should be very very low) and look and feel (which could be higher, but you should still aim to keep low) across contexts.

    1 point
    • Sam Garson, over 6 years ago

      Hey Nick, I have already mocked up a large number of the states of the app, with the idea in mind of keeping the behaviour and style consistent across them, although I will check out those resources as I think I could probably get a little more clinical with ensuring the differences stay low! Cheers

      1 point
    • Sam Pierce LollaSam Pierce Lolla, over 6 years ago (edited over 6 years ago )

      This is a good point. The whole idea of roll-your-own component libraries is to tailor your UI to the unique needs of your use case.

      My first time I followed this process:

      1. built a component library
      2. tried to use the components I built to make my app UI
      3. ignored the components and built what I needed when I hit a wall
      4. built the component set I actually needed by removing the ones I never used and modularizing the extra UI I had hacked together
      1 point