Loom — getting the story from the source
A picture says more than a 1000 words, right?
But as an engineer you might have experienced receiving a bunch of static images or animations on how to implement the UI features of a system.
I still recall receiving a bunch of JPGs exported from Photoshop as a design basis for mobile apps, which didn’t exactly give me the whole story on how to implement the flow in the app.
Today, we enjoy the benefits of platforms like Figma, InVision, and Sketch, which provide increased richness as well as functional prototypes that we can try out on mobile devices.
But all of these tools need the story behind the design. They need the rationale behind the design decisions that only the designer can convey to you.
But what if your team’s scattered time zones make scheduling a walkthrough impossible?
Or, what if you (like me) forget all the granular details that your designer shared in a meeting two weeks ago?
Enter Loom — a great way to do a video recording, where you, as a designer, can go through your designs and give explanations to your choices.
Your colleagues can decide when to view the recordings, saving everybody yet another meeting in their busy calendars.
It also saves designers a lot of time by avoiding detailed annotations and endless presentations to different stakeholders across the organization.
So, to prove the point, I will stop writing right now and let Tradeshift UX Designer, Felix Molonfalean do the talking.
Felix recently gave a talk on Loom at the CPH UX community virtual meetup and you can watch the recording below.
