Matt Anderson

Freelance Desiger Joined almost 9 years ago

  • 0 stories
  • Posted to Startup Design Flow (Jira + Sketch + InVision + Zeplin), Oct 26, 2017

    Overall it looks like a pretty solid flow.

    I've found just sending a link to Zeplin or Invision leaves a lot open for interpretation. Instead I create design docs. Whilst it's a little more up front work I find it saves a lot of time if you can preemptively answer questions, document edge cases, detail animations etc.

    The content depending largely on the specific project, but typically include: An outline for the project goals, relevant research and then a deep dive into specs. This usually involves images (gifs or videos are even better), notes and links out to prototypes etc.

    4 points
  • Posted to Airbnb - "Don’t Go There. Live There.", in reply to Karri Saarinen , Apr 20, 2016

    Would love to see a write up for this! Definitely something we've bee struggling with at my work.

    0 points
  • Posted to Apple Reveals San Francisco Monospaced Font, in reply to ポール ウェッブ , Apr 19, 2016

    Looks like you're in luck. Further down the page they have 10:00 with the slashes

    5 points
  • Posted to Ask DN: What is your process for editing your mobile photos?, Feb 24, 2016

    I tend to find VSCO a little too much work for simple edits.

    More recently I've found really great!

    0 points
  • Posted to Pressure - JavaScript library that makes dealing with Apple's Force Touch and 3D Touch simple, in reply to David Darnes , Jan 25, 2016

    I can't even get it to work in Safari… :/

    0 points
  • Posted to How to write case studies for your design work?, Jan 17, 2016

    I've just recently gone through this process with my website.

    1. If you're comfortable with HTML and CSS i'd definitely recommend that over a PDf. If not maybe check out something like Semplice. Having your work showing on a website seems far more accessible than a PDF which people need to ask for.
    2. A good start is to treat it a little like a book i.e. with a beginning, middle and end.
      • Beginning - Introduce the project, problems, requirements etc
      • Middle - Describe the process you went through i.e. how you tackled said problems
      • End - Show the success of your work e.g. "Increased sales by x", show quotes + testimonials etc.
    3. Depends… Some projects may need to show a little more of the process while others may require less. Take it project by project and don't think you need to fill some arbitrary limit.
    11 points
  • Posted to Ask DN: How do you deploy and host websites today?, in reply to Alex Chan , Jan 05, 2016

    That sounds exactly what I'm after, thanks!

    p.s. You know any good resources for getting this set up correctly? e.g. error handling etc.

    1 point
  • Posted to Ask DN: How do you deploy and host websites today?, in reply to Jordan Koschei , Jan 05, 2016

    Ahh damn, that's currently what I do too though I'm getting sick of conflicting css files from the build process…

    0 points
  • Posted to Ask DN: How do you deploy and host websites today?, in reply to Jordan Koschei , Jan 05, 2016

    Similar to the setup I use!

    You had any luck compiling SCSS on the server (on deploy) by any chance?

    0 points
Load more comments