William Riley

William Riley

Omaha, Nebraska Principal Engineer at Split Infinities Joined over 5 years ago

  • 8 stories
  • 26 comments
  • 34 upvotes
  • Posted to Arby's made a font, so..., May 17, 2018

    It's not a great font for programming FYI

    https://twitter.com/nicknisi/status/997124598411026433

    10 points
  • Posted to Lottie animations as a web component, in reply to Fernando Comet , Mar 25, 2018

    Yeah!! In hindsight, embedding a Codepen would have been so much better. good work!!

    0 points
  • Posted to Lottie animations as a web component, in reply to Nattu Adnan , Mar 25, 2018

    Yeah for sure! Let me know if you need anything.

    0 points
  • Posted to Lottie animations as a web component, in reply to Yitong Zhang , Mar 25, 2018

    Yes!! https://github.com/splitinfinities/lottie-wc

    Thank you so much, I hope you enjoy it!

    2 points
  • Posted to 2018 Design Trends – A free course by Flywheel!, in reply to Joshua Turner , Feb 08, 2018

    Thank you for the feedback - we’re sure we tried to find super interesting subjects, but it doesn’t hit the mark for everyone. And, the internet is a big place! My design trend are design systems, and it’s my big focus throughout 2018. That existed in 2017, but it’s getting better and more well defined. There’s value in repetition - it shows the genre has more inside it to explore.

    0 points
  • Posted to 2018 Design Trends – A free course by Flywheel!, in reply to Vinicius Coelho , Feb 08, 2018

    It was high effort by a good team :) I hope you give it another chance!

    0 points
  • Posted to 2018 Design Trends – A free course by Flywheel!, in reply to Oliver Swig , Feb 08, 2018

    I agree that style doesn’t equal substance. And trends by definition do have short lives.

    Arguing trends are for weak designers is false, and does harm to good design. Using a trending motif in a new and fresh way helps you differentiate from others designing in the trend - and that’s our goal here. To help inspire designers to use the trends to differentiate.

    Another goal is to help educate emerging designers on how to do these things. It’s kind of tough to find inspiration that’s catered, and we wanted to do that. Google wouldn’t help you find something catered.

    And they may feel corny, but it’s our quirk. We want you to do serious work, but not be too serious about it. Learning should be fun, if there wasn’t quirk in the wordplay, it would be challenging to stay engaged and remember what you’ve learned.

    0 points
  • Posted to Code with Design — How we Built a Tool to Export React Prototypes from Sketch, Jan 15, 2018

    This is a fantastically documented article. I'm really excited for more presentational components to be done in tools like these.

    1 point
  • Posted to Why design systems fail, Dec 14, 2017

    Una is my hero. This is a really mindful piece.

    0 points
  • Posted to AMA: What’s Next for Adobe XD?, in reply to Kyle Galle , Nov 29, 2017

    Hey Kyle,

    For plugins, I'm mostly speaking to the idea of opening up the platform to third parties so that can add integrations. I'm not sure right off the top of my head what Adobe have historically used for this. But letting the community build around XD is a great direction because it's what makes sketch such a powerful design platform for product.

    Exactly what Hamish has mentioned. There are different strategies, but as a product tool, it would be sublime to render a component library in the editor - this can make a design system simpler to create and iterate on. Compositor's Lab (https://compositor.io/lab/) is also a great inspiration. The goal should be not to create code for handoff to the developer or engineer, but to create the UI components that are to be collaborated on with the developer or engineer. It's a fidelity issue. Hard to solve through people or process, but reliable once you design for components - like much of the industry has.

    Yesterday, Invision released a great book on design systems that I believe work very well with sketch, but XD and your tooling make it very tough to collaborate as tightly on a design system. https://designbetter.co/design-systems-handbook in this, it details the responsibility of engineering and design teams. Engineers use components to implement the design. So my recommendation here is coming from trying to get your product to bring design and code closer - make the component the source of truth, make it a symbol, make it reusable.

    The other file format issues are because moving between XD and Sketch could be a boon if you don't want to go in this direction. If you make the format interchangable, then Sketch can be design systems, and XD can be the place where the components come to life.

    Making them web renderable is the idea of not converting it to code - but using the code as the source file to render and edit the designs. The difference is nuanced, so I'm sorry I don't know how to make it clearer. It's this idea of hopping to different products in order to get UI completed. If we don't have to hop, that helps design and engineering collaborate together better.

    Thank you for the time, Kyle and XD team - I really appreciate what you're working on. We use XD at Flywheel.

    2 points
Load more comments