Where the design community meets.
Not to answer on Ken's behalf, but I have the same feeling. The animation and "tweening" as I would describe it, just isn't as intuitive as I would like. It seems wasteful, in terms of duplicating artboards and the like.
I haven't had time to explore it much, but I will be playing with it over the weekend and report back!
Keep me posted, I'd love to hear your thoughts!
Ryan- I'd love to get your feedback and first take so to speak as well when you've had a chance to dig in and loop a few folks in from Studio team as well so you can directly chat with the folks pouring the blood and sweat into this each day. Def want to do right by you and hear your impressions- hit me up stephen[at]invisionapp.com.
I think it is just a start. For now you cannot build states with components, and when that is coming it will be cool.
Is there a software that you can compare it to that offers a similar set of features, but feels more intuitive?
Hey Andrew- not sure if you've played with the brand new Timeline experience yet or not. We literally just dropped that yesterday afternoon so it hasn't been in their long. Prior to that it was a bit more of a chore to do the animation setup work. Timeline is a more visual way to do this that feels a bit more natural. This us an example of early access tester input having a direct and major impact on development of this product. We had overwhelming feedback and requests for this and chose to speed up its development and priority.
We REALLY want that feedback and I'd love to keep chatting if you're up for it based on your experience. Our whole goal during early access phase is to listen intently, dig in deeply on nuance, and push builds as quickly as possible with that actionable feedback. For those who have been on early access longer, I hope you can attest to the speed at which we're moving here. For those of you that just joined, look forward to showing the pace of development real-world as you see those new builds hit quickly. Point is- you all have waited long enough, were looking to move at a pace of development measured in days/weeks not months/years.
Hit me at stephen[at]invisionapp.com if you're up for a quick call, it is so critically important that we learn from your feedback so we can make this the best it can be- thank you! Open door here!
Interesting to see this little screen shot Stephen. Really what I am looking more out of studio for is prototyping/animating. Is there any good tutorials or documentation on how to do timeline style animation? I think that might be what I am missing from the first peek I took at it and could be helpful to get up to speed faster.
Totally hear you Jason- thats something we're gearing up around as well. Honestly we should have had more tutorials like this ready from the get go- sorry about that!
Team has been working hard to bring you a whole series of videos and tutorial will hit soon (I saw them last week and they're shaping up real nice). Part of this whole early access thing is that its a bit more raw and wild west. We're looking to bring a little more structure and civility to that wild west town though very soon- thx for the understanding, passion and digging in with us!
I tried it before you guys released the timeline feature. I wasn't impressed (slow and lacking features) when I first tried it but I'll take another look. Looks useful
I have a question on that timeline. Why is it on the left hand side and not on the bottom? Every notable application video, animation, and editing applicatoin back to the Macromedia days has a vertically stacked timeline. What led to the decision to make it horizontally stacked?
I imagine it's because it's essentially a replication of your layer panel (not a library) but with the addition of keyframes, so makes sense to have an expanded view in the same place. You're only setting up a beginning and end keyframe, so a full-width timeline isn't as necessary.
Hey Joe! Corey actually hit this design decision logic square on the head. With microinteractions / rich motion animations the timing aspects end up being shorter (for the most part) than their video counterparts. Video timelines are optimized for time-based focus because your clip might be .001 seconds or 100 minutes long while having less layers and video elements vertically stacked.
In motion design for digital products we've chosen to optimize for layer stacks vertically; recognizing that more often than not, you're going to want the extra screen real estate optimized for seeing many different layers and a de-scoped length of time on the player vs fewer layers visible with a scoped up length of time on the playhead. Does that make sense?
Hope that helps sheds some light here. But again, thats the whole point of an early access- if you feel like any of these decisions are omitting use cases or neglecting any typical user behaviors please raise your voice in the form of feedback to the team. Goal is to root out as many of those as possible and optimize this platform for you and your team.
Thank you for getting back to me on this Stephen. I appreciate you taking the time to respond, and I'm looking forward to diving into the new version of Studio.
I'm actually going to get into it more this week, and I'll be sure to email you any feedback I may have along the way.
For the few minutes I had with it, the fact I can create some super smooth easing is pretty incredible, in and of itself.
In the example above, I assume you have the layers grouped and then "linked" together across multiple artboards, ex. all the text that eases in, if I'm not mistaken.
Either way, looking forward to practicing a bit more and playing with some of the tutorial files. Thanks again!
Right on, sounds great Andrew! Thanks so much for your passion and willingness here to help us improve. Looking forward to that feedback and getting a chance to action on it and help continue evolving this thing for you and your team.
Yeah, although, if you make heavy use of components it might be ok (in terms of duplicating artboards/content).
I actually liked the animation part the most in terms of Studio bringing s.th. new to the table, but all other aspects of the the app are just too weak. I'm seeing Figma as their main-competitor as it's the only other tool that does enable an e2e design workflow within the tool itself, but it's just so much more mature when it comes to the design editor tools or component handling. They have to do a lot of catching up.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.