framer for the win - using framer prototypes for your app project. (for melbourne cocoaheads 2016)
TRANSCRIPT
What we will cover
1. Prototyping: How did it start?
2. The tool: Why Framer?
3. Demos: What can we make?
My problems are:
1. Getting weird feedback from client.
2. I'm constantly making mistakes as well.
3. Missing lots of things that a dev need to build the screens.
4. It takes lots of time to create a “Spec guide”.
5. Too hard to keep the "Spec guide” up to date.
1. Failed to explain what’s important.
2. Failed to explain what’s NOT important.
Fundamental reasons
Designer will get lots of 💩 feedback.
…Because Everyone has their own ideas about how a thing should look.
Why is Framer awesome?
1. Using Gesture: Tap, Scroll, Pull, Drag.
2. Animation options, easy to reverse & reuse.
3. Easy to share without installing software.
4. Fast to build & run.
Some constraints though!
1. You need to know how to code (A little bit, CoffeeScript).
2. The code you write has no impact on actual code that a developer will be writing.
3. Doesn’t come with iOS or Android native transition effects, sometimes it can be labor intensive.
Getting feedback became fun
1. Instead of showcasing in front of people, you can let them play with the demo and get valuable feedback.
2. Instead of expensive A/B testing, you can plan casual user testing – as many as you want.
Seamless implementation
1. Most of the time, Framer prototype is based on the similar logic that developers also use.
2. Compare to GUI based prototyping tools, Framer tends to be more reliable as a design reference for developers.
You will save a lot of time
1. Interactive prototype is really intuitive, there is no room for wasting time on explaining same thing over and over!
2. Sometimes a good idea turns out as a failure. Better chance to test the design earlier.