Arthur Klepchukov

Joined about 2 years ago

  • 8 stories
  • Posted to Sponsor: Abstract enables you to track the who, what, why, and when of every design decision., in reply to Michael Rurka , Jul 26, 2019

    I'm an Abstract user on a team of 5 designers. Abstract simply asks for branch names or commit messages just like git does.

    Naming conventions also exist in git, where they are also often ignored or very easy to deviate from without penalty. Documenting your work is a conscious effort and harder to stick to with aggressive deadlines and other "real" work looming. Anecdotally, humans don't seem skilled at describing or characterizing things. Our tools should help us be better. But they don't.

    Abstract especially, unlike git, has almost no support for more granular commits (e.g. commits to some symbols but not others, these artboards but not those 3, etc.) leading to nearly useless commits like "cleanup" or "WIP" or "changes."

    0 points
  • Posted to Sponsor: Abstract enables you to track the who, what, why, and when of every design decision., Jul 24, 2019

    There is rarely a "why" provided because good branch names and commit comments are a persistent challenge. Abstract does nothing to help this.

    1 point
  • Posted to Sketch for Teams beta is out now, Jul 24, 2019

    I'm very curious if version control will be flexible enough to replace Abstract. The amount of merge conflicts, lost changes, and general usability headache makes me rarely trust Abstract. I hope a native Sketch solution can do much better even if it does much less.

    1 point
  • Posted to Learn UI Interactions with Framer Playground, in reply to Meng To , Jun 13, 2019

    He may have been talking about the landing page. I too was really confused about the static headings presented as buttons—from Layout all the way to API Data. Surprising pattern.

    0 points
  • Posted to The State of CSS 2019, Jun 13, 2019

    Consider adding a call to action on the home page. There's a lot of info, but I have to guess as to what you want me to do next.

    0 points
  • Posted to The humble receipt gets a redesign, May 20, 2019

    Fun example of real-world UX. Anyone else inspired to think of what other use cases aren't supported by existing receipts?

    For me, simply sorting things from most to least expensive, would help demystify where the money went.

    1 point
  • Posted to Designing for code and coding for design, May 20, 2019

    "Mirroring code structure in design files" doesn't make sense to me if you're designing and building cross-platform. Markup does not necessarily translate to native mobile or desktop code. Design tools should enable speed of ideas before consistency of execution, which rarely requires the rigor or structure of production code. This strikes me as too prescriptive of a requirement.

    0 points
  • Posted to What design tools get wrong, May 02, 2019

    Thanks for sharing Kilian. Do you find nested symbols in Sketch helpful? They seem to address your points—esp variants, states, and responsive variants. I find symbols make good spacers too. Sketch does seem to be moving toward more design tokens with text styles, layer styles, and document colors being available in libraries.

    Wholeheartedly agree on more constraints and built-in version control and a11y.

    0 points
  • Posted to Abstract changelogs leave a lot to be desired, in reply to Josh Sanders , Apr 16, 2019

    It's not just metadata like color profiles and symbol positions. All text styles and layer styles changes appear in this area. When you're maintaining and evolving a design system, those details are quite important.

    0 points
Load more comments