Notes from “Prototyping with Framer”

Photo courtesy of @pkralle (https://twitter.com/pkralle/status/864315119781552128)

On May 16th I gave a talk at the Tech Talk Meetup hosted by Pivotal Labs in Sydney on “Prototyping with Framer”. (Slides here).

I will also be running a workshop for those wanting to learn how to use Framer in Sydney on July 12, 2017, please sign up here.


Showtime! (Photo courtesy of Nicola Rushton)

We prototype so that we can make an idea tangible. With a tangible artifact we can have discussions about whether or not we are building the right thing. Once we start moving away from lower fidelity prototypes and towards higher fidelity prototypes we can start to ask if we are building the thing right.

Learnings enable decisions

The quicker we can loop between question, concept and validation is how we can get learnings quicker. Learnings enable us to make product decisions. There are times when you need to have higher fidelity prototypes to help you test better by avoiding having to get users to imagine what a screen might do. You could code some of these interactions in code but that could take more time (setup of environments, licenses, etc). Sometimes you need something that doesn’t come out of the box and you need to validate that it has customer value to dedicate engineering time towards it.

Slide deck (https://www.slideshare.net/lifeofmle/prototyping-with-framer)

For the presentation, I thought it would be a good idea to do some live coding and prototype a simple application with Framer. It could have been better if I prepared some more code snippets so that there would be less dead air and mistakes. We managed to cram a lot of concepts into one prototype:

Here is the link to the prototype https://framer.cloud/bOOVM

https://framer.cloud/bOOVM

Here are some other articles that I referenced in my talk

Show your support

Clapping shows how much you appreciated Michael Le’s story.