Tom Reinert

Tom Reinert

UX Designer at milkmonkey Joined almost 6 years ago via an invitation from John K.

  • 9 stories
  • 80 comments
  • 20 upvotes
  • Posted to Design Tools: When do we get stateful components?, in reply to Andrew C , Sep 21, 2018

    It's important because that's how digital products behave. You have elements that can take various states. A website is not an array of artboards, but ONE interactive page.

    Also, I'm talking primarily about prototyping. I think it's very important to present your work as a prototype, and producing them by duplicating and linking 10+ artboards for a single interaction is not they way it should work.

    2 points
  • Posted to Design Tools: When do we get stateful components?, in reply to Or Arbel , Sep 20, 2018

    I‘ll give that a try :)

    0 points
  • Posted to Design Tools: When do we get stateful components?, in reply to Jared C , Sep 20, 2018

    Yep. See my other comment ;)

    0 points
  • Posted to Design Tools: When do we get stateful components?, in reply to Steve O'Connor , Sep 20, 2018

    Sure, I tried all the tools ;)

    But then again we face the reality that there are certain industry standards (sketch, figma, etc). And I somehow hope that they all will abandon the paradigm of linking whole artboards, which in my opinion is not suited for most product design work.

    There will always be tools that do that one thing right. My point is that I think that stateful components should be a fundamental feature, just as drawing rectangles or entering type.

    0 points
  • Posted to Design Tools: When do we get stateful components?, in reply to Chris Cubellis , Sep 20, 2018

    Yes, you can design states as components. But they are not available in prototyping.

    3 points
  • Posted to Design Tools: When do we get stateful components?, in reply to Larry Brown , Sep 20, 2018

    Yes, Framer is closest. I really hope they'll introduce a UI-based solution for states.

    0 points
  • Posted to Lobe | Deep Learning Made Simple, in reply to Adam Menges , May 03, 2018

    this is brilliant – can't wait to try it out.

    0 points
  • Posted to PixelSnap — Measure every pixel on your screen with ease, Feb 07, 2018

    works very nicely! will there be a screenshot feature anytime?

    1 point
  • Posted to Ask DN—CSS Grid Framework?, Dec 20, 2017

    Check out this talk:

    https://www.youtube.com/watch?v=N5Lt1SLqBmQ

    Around the 29min mark"We don't need a Grid Layout based grid framework. It is a grid framework."

    3 points
  • Posted to Design tools are missing the point, Dec 12, 2017

    I agree – not only because I wrote the same thing a little while ago ;)

    In my opinion, the flow of such a design tool is quite simple and not that different from what we have now.

    From the top of my head:

    1. Create a "symbol" of some element
    2. Go into that symbol
    3. Create a new "state" of that symbol
    4. Name the state (e.g. "hover") and modify accordingly
    5. Switch to prototyping mode
    6. Click on symbol to add new interaction (as we do now to set links to other artboards)
    7. Set: On hover: Change to state: "Hover"
    8. Done

    Of course, there are some details to be worked out and maybe there's an even simpler solution. But for now, this would solve a lot of pain with creating duplicate artboards where one element changes it's state.

    I'm pretty close to mocking up the complete tool now. But I'm also sure, that Framer, Sketch, Figma, XD, etc. will get there eventually.

    0 points
Load more comments