Where the design community meets.
I've really wanted to use Sketch, I think ill introduce it into my workflow for personal projects. However, I think the biggest roadblock right now for me is using it in the office with a diverse staff. It wouldn't take too much to get the design team on board but a lot of our developers use our PSD's, telling them to use and learn Sketch is perhaps too much to ask, does anyone have any experience integrating the software into large multidisciplinary teams?
Yes, I've done so at my last two jobs, I've used Sketch professionally now for about 18 months. Whenever I show sketch to a developer they fall in love with it - it talks their language much better than photoshop, it talks in pixels and things that are closer to code. And because it's so dirt cheap I've been able to buy 10+ man engineering team a license with no pushback from finance departments. I've never had any real pushback once they see how easy it is to use and that there's essentially no learning curve for the average person.
+1 David M.
Sketches does speak the same language as developers. It uses the same properties for borders, colours, gradients, shadows, etc. It's also incredibly focused on those things alone whereas in Photoshop, people have to find them in a sea of options.
I don't think you'll find much resistance. on the contrary, people are more likely to want to learn design after they try out Sketch. :)
I've been asking developer-pals this lately. I think it is a matter of inquiring how developers actually use those assets.
For example, I asked a front end developer how he retrieves the assets and prefers that they are organized. He's not afraid of photoshop, but would rather stay in his IDE as much as possible.
I gathered that he simply uses Finder with Command+I for the file's properties. From there he's able to quickly assess what size the asset is and go to work.
I was able to think of three other work arounds while in a single chat session that would make his life a lot easier.
If you haven't already, just sit down and see what it is your team accesses, how they use it and chances are there is a way to provide them the same asset or content using whichever app you prefer.
I will say that working with Sketch will make going back to Illustrator and Photoshop more painful than the other way around.
When you've found out a work flow, let me know what works. And if this is helpful, do share.
Whenever I am pushing for changes internally (in the company, that is), I always find myself yelling "This is NOT [enter previous state here]".
Inertia is fine and all, but it's not change's best friend.
When I started pushing the team from AI and PS to Sketch they always compared it to working with the Adobe products.
That's the main bottleneck.
Sketch, in its own way, introduces a new way of doing things. One you have to be a bit patient and willing to experience.
Once you do, Sketch will be the go-to app for far more things than drawing stuff.
For me, it's the closest thing to working on paper. And that's amazing.
Thanks all for all the great feedback. We have quite a large site redesign project coming up soon, it would be a great time to sit down with the developers to see if sketch can help streamline a responsive design workflow. Cheers
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.