Cover-photo-2015-08-15_01_06_45__0000-1271120150815-3-1vl9s3l
James Futhey

James Futhey

Seattle, WA Product Design Consultant Joined over 3 years ago

  • 10 stories
  • 77 comments
  • 27 upvotes
  • 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?

    1 point
  • 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
  • Posted to Failed to Grow a Side Project into a Business, Nov 24, 2017

    Interesting read. Thanks for sharing!

    1 point
  • Posted to Looking for logo feedback, Oct 28, 2017

    Too much space between Does & Good

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

    Exactly the same in theory, in practice I prefer:

    1. Anything but Jira
    2. Sketch
    3. Marvel
    4. Zeplin
    1 point
  • Posted to How do you recruit participants for usability tests?, Oct 12, 2017

    If your marketing team is already engaging with customers, go through them. It could be on social media or email, but I have had a lot of success with the following:

    1. Email blast to users (Help make x product better! Discount / offer for participating. Click here (typeform/google qualifying survey) to express interest.
    2. Qualifying survey (collect some demographic information as an added bonus)
    3. Reach out to your pool and cycle through them as participants. Can be an Excel spreadsheet. Note: Your pool will get stale over time.

    I've had colleagues successfully recruit w/ Craigslist, although I avoid it. It's a lot of work.

    There are recruitment"agencies" and services, but generally speaking, it drives your costs up. People who routinely do Usability Studies somewhat skew your data, and expect more and more compensation over time.

    Professionals usually budget about $250 per participant toward compensation. You can find better participants for less if you get your hands dirty, and know your users.

    Linkedin groups and in some cases facebook groups can be great places to advertise. If you're recruiting from the general public, try to match your potential user as much as possible (demographic > experience > product need).

    Then, just replace step one with "Post to a Linkedin group".

    1 point
  • Posted to What back-end language should I learn?, Oct 09, 2017

    Spent some time as a dev as well. Not going to make this a “which language is better?” post. Instead, I'll focus on other practical aspects of popular languages:


    Ruby is a wonderfully-designed language. The ecosystem is shrinking as developers seem to be moving to Go & Node. Fairly easy to learn, good ecosystem / plenty of libraries available. 2010 was probably the perfect year to learn Ruby & Rails, though. Prospects not as hot these days.


    PHP, on the other hand, is a terrible language. But, it can come in handy if you work on Wordpress websites. If you're not working on Wordpress sites, I would say “stay away”. It's not going to open doors for you. It's not going to teach you any best practices (although it's getting better!)


    Javascript / Node: Here is where I would place my bets.

    1. It's easy to get started, especially if you already have front-end Javascript experience.
    2. NPM is, hands down, the largest repository of packages and libraries you will find, anywhere. Given, there's some mediocre & unmaintained stuff as well, but you're going to have a really easy time finding libraries and packages for whatever project you want to work on.
    3. Hosting isn't the nightmare it was when Node was first released. Now.sh & similar make deployments & scaling a snap for beginners.
    4. Node adoption is currently growing. Pretty much every other ecosystem I can think of (excluding Golang) is shrinking or stagnating.
    5. JS has the biggest developer community. Plenty of tutorials and guides to get you started.

    Golang is becoming incredibly popular with developers right now. It's a great language, but it's probably a bit difficult for beginners. Library support / dependency management is a nightmare (even more so if you're a beginner). Lots of devs seem to be having fun re-inventing the wheel in a relatively-new ecosystem. Some basic things lack mature solutions. Golang will, however, probably emerge in 3-5 years as an incredible language with a great ecosystem & tons of support. Today, however, the learning curve is pretty steep.


    Hope this helps!

    2 points
  • Posted to Ask DN: What side project are you working on this weekend?, Oct 08, 2017

    My portfolio!

    Ulg :)

    7 points
Load more comments