While I welcome all this work put in favor of UX/UI designers (like me), am I the only one who thinks using AE for interaction design feels a bit like a hack? Just like using Photoshop to design interfaces: sure, it works, but it puts the user too far from the interface (at least in the early / mid stage of the development).
Animation in Interface design is directly linked to interactions. If the user performs an action, something "happens", and that transition between the user input and the result is what I would say 90% of animation is about in IXD. Now, if you start your wireframes in Sketch, then jump into AE to try some cool animations as a standalone thing, and once you're happy you move into a "living" prototype I think those are too many extra steps. Again, what I think is that the animation should be tested while interacting with the prototype, in real time.
That's why I think we don't need better ways to work in Sketch and AE, but instead we need better interaction-animation tools. I can't say much more cause I'm working on one possible solution right now, and hopefully will be ready soon :)
100% agree on your thoughts. I personally prefer doing animations in code because it's linked to user interactions and the animations are native. But I totally get that some designers work faster in AE than code. I still think the disconnection from animations + interactions is a big gap. Hopefully tools will continue to evolve and reduce that gap.
I use it for marketing reason, so i create videos out of the layouts. In combination with Element 3D and Devices. It was always a hazle to get the layout send over to AE. I don't create interactions, there you are right it makes no sense.
I am on Mac now, but when I was designing on windows, there weren't so many options for UI design or interaction design (no Sketch, no Principle). So I need to use photoshop and after effects. We need some design, prototyping and interaction tools available on all platforms.
I can agree with you here. Designing interactive animations with a tool that's meant for static video makes less sense.
That's one of the key ideas I had for creating Kite. Combining real-time animation with interaction. (kiteapp.co).
This is amazing!
Sweet! thanks for this guys. You just saved me tons of headaches.
This is a complete game changer. Saving lots of time and $. Thanks guys!
Great.. ! And also sad that we to resort to tools like AE to make decent prototypes.
The dozen or so prototyping tools out are either far too basic (Invision) or far too difficult (Framer, origami )
Introducing principle. I think im going to stick to Principle for now. But the ability to send variable to developers with inspector space time is very intriguing. I just find myself moving a lot faster in Principle.
I tried it sometime last year. It gets messy after a few screens and lately im working more on desktop applications (web based)
Just saw this and it looks awesome somebody already tried it, what are the downfalls?
Tried it. The only thing I could find so far was that type and elements that run off the canvas don't always come into AE correctly.
HELL YES! Can't wait to try this!!
This is huge
While importing sketch layers into AA, Is anyone getting an Error 1919?
Same issue here.
Same issue, any solution?
I had the same issue with layers import. But I tried to save layers with Sketch2AE plugin and after that opened file into AE в формате *.sketchae. Everything working well. Strange, but it's works.
Yes, sometimes after only changing text contents on an object that imported successfully before. Exporting/saving layers instead appears to also get hung up on something. Wish I could debug.
Same issue, Error 1717, it crash my Sketch every time, any solution?
I got the same issue, 'error on line: 1473'. by pasting and opening sketch codes both give the same error.