Loom Use Case: Design to developer hand-off
View Comments and ReplyTranscript
Show Transcript
Hey, all I'm Rajiv from loom. And today I just wanted to really quickly talk through the design to developer handoff and how you can use loom to make this process even smoother for you as a designer or just for your engineering partners too.
So the way loom really accelerates the handoff process for me is it allows me to spec out my files a lot less while still giving engineers all the context they need and a much more evergreen format that they can refer to much quicker.
So I'm going to walk through a first-time UX for loom HQ, the new product that we just launched. And so over here, we take our users through a couple of steps and for the engineer, a lot of things that I would talk through over here are the micro.
So I have the full flow set out. Like I'm guessing all of you would have a, but there are a couple of things that we wanted to keep in mind during this flow.
For example, if the user were to click out they would be able to immediately leave the modals, clicking the X we'll, let them leave.
I can also use the arrow keys to go back and forth instead of having to document all of this in text, I'm able to just talk through it get feedback in the comments of this video from my engineering partners.
And if there's anything that they do want in here, I'm able to just put that in. So as I scroll through the file there are a couple sections where I left a little bit of an extra note, but I don't really have to do that throughout.
It's only an areas where they said than you had more feedback. And yeah I just record a video walking through this stuff, and that is pretty much the handoff makes it much more collaborative and much easier for both sides.
I'm excited for y'all to use the Litchfield and trap the design to develop brand.
Transcript
Show Transcript
Hey, all I'm Rajiv from loom. And today I just wanted to really quickly talk through the design to developer handoff and how you can use loom to make this process even smoother for you as a designer or just for your engineering partners too.
So the way loom really accelerates the handoff process for me is it allows me to spec out my files a lot less while still giving engineers all the context they need and a much more evergreen format that they can refer to much quicker.
So I'm going to walk through a first-time UX for loom HQ, the new product that we just launched. And so over here, we take our users through a couple of steps and for the engineer, a lot of things that I would talk through over here are the micro.
So I have the full flow set out. Like I'm guessing all of you would have a, but there are a couple of things that we wanted to keep in mind during this flow.
For example, if the user were to click out they would be able to immediately leave the modals, clicking the X we'll, let them leave.
I can also use the arrow keys to go back and forth instead of having to document all of this in text, I'm able to just talk through it get feedback in the comments of this video from my engineering partners.
And if there's anything that they do want in here, I'm able to just put that in. So as I scroll through the file there are a couple sections where I left a little bit of an extra note, but I don't really have to do that throughout.
It's only an areas where they said than you had more feedback. And yeah I just record a video walking through this stuff, and that is pretty much the handoff makes it much more collaborative and much easier for both sides.
I'm excited for y'all to use the Litchfield and trap the design to develop brand.