10 comments

  • Joseph BarrientosJoseph Barrientos, 10 days ago

    Hopefully it has everything we need and my team can ditch Abstract. Slimming down to just sketch and zeplin would be amazing

    4 points
    • Dexter W, 9 days ago

      I still think the Abstract git workflow to separate iteration with production is what makes it useful for teams, not the ability to simply share files. Although I find it slower than other approaches, it really makes projects smooth.

      1 point
      • Joseph BarrientosJoseph Barrientos, 9 days ago

        I can totally see your point, and maybe our team just isn't efficient but Abstract is only used by my design team and used for sharing with eachother and version history. From there we export to zeplin and hand off Zep links to the dev team.

        0 points
        • Musavvir Ahmed, 5 days ago

          Abstract can be super powerful and can replace Zeplin entirely but, also in my case, it's usually just me or maybe 2 designers in total collab-ing in a single abstract project.

          It'd be super nice If I can ditch Abstract altogether for native sketch version controlling.

          1 point
      • Matthew O'ConnorMatthew O'Connor, 8 days ago

        Could you explain your "separate iteration with production" workflow in abstract or have any decent articles about it?

        0 points
        • Musavvir Ahmed, 5 days ago

          Mattew O'Connor, I'm pretty certain Dexter W is referring to the standard 'git workflow'. Just google the last two words.

          Interestingly seldom us designers will follow that or any standardized branching format and we'll just create branches and sub-branches as we seem fit. We usually wing it in Abstract, don't we?

          0 points
          • Dexter W, 3 days ago

            Hey Musavvir,

            I get ya. It’s really easy to get a little messy in Abstract, especially if no one is in charge of maintenance if component libraries. A lot of designers also find it too complicated. But once you realize the power of the git flow, it’s hard to go back.

            0 points
        • Dexter W, 3 days ago

          Hi Matthew, somehow I had missed this message. My flow works like this:

          I work closely with product managers and designers to iterate different designs through commits. Exploratory work stays in that phase. We work in short iterative cycles.

          Developers and other stakeholders who are mainly focused on the deliverables are only are trained to look at Master designs for production work, which means they don’t need to fuss with all our messy creative work behind the scenes in the commit cycle.

          I have all my designs validated through the commit phase with the active stakeholders who shape the product, and then when we’re ready with designs that we have thought through, we push those changes to the Master file.

          This is not the perfect workflow, but one I found works pretty well.

          1 point
    • James Young, 9 days ago

      I couldnt agree more!

      1 point
    • Rhys MerrittRhys Merritt, 8 days ago

      Always nice to downsize the toolset. We recently moved from Sketch / Abstract / Zeplin to just using Figma and I'm pretty happy so far... I'd love it if Sketch introduced a way to add dev handoff as well

      2 points