James Futhey

James Futhey

Seattle, WA Product Design Consultant Joined over 3 years ago

  • 10 stories
  • Posted to What sucks about my website?, in reply to Nico Serdeir , Feb 25, 2018

    Another alternative is to just pick one of these fonts and stick with it. They're both robust enough to provide a good starting point for the main user task, which is essentially a blog post.

    0 points
  • Posted to Has anyone actually received early access to InVision Studio?, in reply to Corey Ginnivan , Feb 12, 2018

    Thanks for sharing.

    Without an official statement, there's a lot of negative to be read from this. The hype train seems to have already left the station, but they're gagging early users from talking about their experiences?

    Optimistic that eventually it will be amazing, but coupled with the tight-lipped delay, it sounds like there are some software quality issues holding up a release..

    3 points
  • Posted to Meet Phase — Digital Design Reinvented, in reply to Nick Budden , Feb 08, 2018

    Looks really good!

    Kind of wish people would stop reinventing things though.

    0 points
  • Posted to Intercom, in reply to Phil Rau , Feb 06, 2018

    1 point
  • Posted to New HTML 5.2 dialog element demo, Jan 15, 2018

    Huh, it doesn't have a close button by default.

    1 point
  • Posted to Protowire - Adds Prototyping to Sketch, Jan 03, 2018

    Looks neat!

    Would love to see a simple prototyping tool in Sketch.

    Developer here as well, might be a fun project to work on (since others have offered). futhey at gmail.

    0 points
  • Posted to Bootsketch: Design sites faster (looking for feedback), Dec 13, 2017

    This looks great. Grabbing a copy. Definitely worth $29 for a well-maintained set of Bootstrap symbols w/ overrides & good coverage of Bootstrap, especially if you're working on a UI kit from scratch.

    I've been through the process in the past, and honestly, if I do have to do it all over again (on bootstrap), this would save a ton of hours, and help kick off the process.

    Would advise, that you are going to need to keep this well maintained, and be responsive to feedback / bugs / sketch updates if you're going to scale this.

    This stops holding much value once it loses compatibility with the latest version of Sketch, or Bootstrap, etc.

    3 points
  • Posted to How to Export Sketch to HTML using Launchpad, Dec 08, 2017

    Was initially very impressed! It handles almost everything.

    But, unfortunately, this export turns every element into an absolutely positioned element. Code is too messy & unorganized for even an experienced dev to clean up, even when it's not obfuscated.

    Any plans to move toward human-usable HTML export?

    2 points
  • Posted to Marvel is better than InVision, in reply to Gokhun Guneyhan , Nov 28, 2017

    I contacted support about this, they're releasing it to everyone on December. Currently, it's beta.

    0 points
  • Posted to The only design tool product teams need right now— InVision Studio, in reply to Thomas Lowry , Nov 27, 2017

    Exactly. This is a solution to a contrived problem.

    Nobody's workflow today, regardless of platform, involves recreating a design from scratch three times, when moving from wireframes, to low-fidelity, to high-fidelity, to redlines.

    Modern design workflow on Sketch is:

    1. Wireframe fidelity in Sketch: Everything is created with symbols. You probably already have a UI kit, and if not, you're creating one using built-in tools. Pretty painless.
    2. Tweak symbols & move to Hi-fidelity: Adjust fonts, & colors. Minor updates to existing symbols. Everything syncs painlessly with built-in libraries.
    3. Create a click-through prototype: Pretty simple, Invision & Marvel offer advanced syncing with Sketch. Takes me about 10 minutes to create a large prototype. Nobody is spending more than a few seconds per artboard on this.
    4. Prototype interactions in Principle or Framer: Optional step, prototype individual micro-interactions (screen transitions, unique animations, etc) in Principle or Framer. No reason to prototype the entire app. This is only time consuming or complicated if you're doing extensive motion design.
    5. Export redlines (Zeplin, Avocode, or similar): Optional step. If you use Marvel or Invision, you've already done this when creating a click-through prototype (although you may not have realized it). Requires only minimal attention to naming conventions, grouping, and export settings when creating your initial design. Unless you have a lot of "design debt" (poorly structured sketch file) you don't have to do anything at this point.

    If you're happy with Photoshop or Adobe XD, but those products don't support a robust or time-saving workflow, complain to Adobe. Complain to Figma. Complain to whoever you're paying for your tools until your tools are awesome. Or buy Invision Studio, & complain until it's as good as the Sketch ecosystem is today.

    But, Invision Studio has got to solve a real problem if it's going to succeed in the market. Because today, "I wish I only had to pay for / use one tool because my workflow is so complicated / difficult / time consuming" is not a real problem experienced by UX designers.

    2 points
Load more comments