Dexter W

Designer Joined over 3 years ago

  • 2 stories
  • 80 comments
  • 145 upvotes
  • Posted to Any designers using Framer X? Why or why not?, in reply to Thomas Michael Semmler , Jun 22, 2019

    Wow. Can you tell me what kind of stuff you built? I assume you are proficient in React

    0 points
  • Posted to As a Product Designer, what are your essential tools?, in reply to Ruban Khalid , Jun 22, 2019

    You got it! Eagle is a Taiwanese software company. Pretty slick stuff that makes you miss dedicated Mac apps before saas took over the world.

    1 point
  • Posted to As a Product Designer, what are your essential tools?, Jun 19, 2019
    • Sketch - UI, wireframes
    • Abstract - staging, handoff
    • UX Pin - prototyping
    • Framer X - prototyping
    • Paper - ideas
    • Bear notes - ideas
    • Eagle - UI patterns
    • Air Table - research
    1 point
  • Posted to Any designers using Framer X? Why or why not?, Jun 19, 2019

    Framer X is the No Man’s Sky of the design world. Until the launch of Playgrounds, you pretty much had to be a React front end developer to build anything worthwhile. And its anti design spending that much time coding.

    Framer X is much better recently for these reasons.

    1. Overrides + Playgrounds make things easier and faster
    2. The React / ES6 guide explains all the technical stuff clearly to non developers
    3. The whole design code dream is starting to make sense. A lot of code is re-usable.

    BUT...

    There are not enough examples yet to handle common UI patterns. It’s not always clear when you should use a design vs code component. Almost any tool is easier to use than Framer.

    7 points
  • Posted to Sketch introduces collaboration & versioning , in reply to Musavvir Ahmed , Jun 12, 2019

    Hey Musavvir,

    I get ya. It’s really easy to get a little messy in Abstract, especially if no one is in charge of maintenance if component libraries. A lot of designers also find it too complicated. But once you realize the power of the git flow, it’s hard to go back.

    0 points
  • Posted to Sketch introduces collaboration & versioning , in reply to Matthew O'Connor , Jun 12, 2019

    Hi Matthew, somehow I had missed this message. My flow works like this:

    I work closely with product managers and designers to iterate different designs through commits. Exploratory work stays in that phase. We work in short iterative cycles.

    Developers and other stakeholders who are mainly focused on the deliverables are only are trained to look at Master designs for production work, which means they don’t need to fuss with all our messy creative work behind the scenes in the commit cycle.

    I have all my designs validated through the commit phase with the active stakeholders who shape the product, and then when we’re ready with designs that we have thought through, we push those changes to the Master file.

    This is not the perfect workflow, but one I found works pretty well.

    1 point
  • Posted to Sketch introduces collaboration & versioning , in reply to Joseph Barrientos , Jun 06, 2019

    I still think the Abstract git workflow to separate iteration with production is what makes it useful for teams, not the ability to simply share files. Although I find it slower than other approaches, it really makes projects smooth.

    1 point
  • Posted to Everyone Is A Designer, You're A Facilitator., in reply to Pascal Briod , May 29, 2019

    I see critical thinking has left DN.

    1 point
  • Posted to Introducing Framer Playground, in reply to Eric Chu , May 09, 2019

    Framer X was really popular until everyone found out how painfully hard it was to use. It was easier to learn real React than how to get React to work in Framer X. But I do expect Playgrounds to be a huge overhaul.

    0 points
  • Posted to Accenture sued over website redesign so bad it Hertz, Apr 25, 2019

    I am not in the consulting or agency space, but if you embark on a large product redesign, how could you not enforce some kind of design system for your own sanity?

    "The specs called for a common core of libraries to be "a fundamental principle of the design"... Accenture, well, completely ignored that, according to Hertz."

    "the defects in the front end development code were so pervasive that all of Accenture’s work on that component had to be scrapped." (It was using Angular 2.)"

    4 points
Load more comments