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.
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:
- ScrollComponent, FlowComponent
- State, events, layers
- Importing from Sketch, Copying code from Sketch
Here is the link to the prototype https://framer.cloud/bOOVM
Here are some other articles that I referenced in my talk
How Zova is using Framer to reimagine their Apple TV fitness appblog.framer.com
Prototyping for VR was a key aspect of mine and Ben’s latest week-long project so here’s a summary of a couple things…blog.framer.com