Great stuff! Such a nice update.
When you animate a layer using the transition designer a tag appears. Now that tag shows a representation of the actual easing curve of your transition, so you can tell at a glance which layers have which easing curves applied to them.
This is an amazing update to Flinto (for Mac) for sure. Great going guys! Cheers!
Fabulous stuff! Any chance of documentation of exactly how the how the plug-in actually works out what to replace, add or remove? Most of the time it seems to just work but sometimes I get some unexpected duplicates.
Nothing written out, but that's a good idea. If you do run into a weird case, we'd love to hear about it. If you can send a test case Sketch file or screen recording to email@example.com, we'll try and improve it, or at least explain it :)
Thanks for the instant reply. I'll try and outline what I'm experiencing here in case anyone else has any ideas.
I have a bunch of sketch files, with a bunch of Artboards each, that I import into one large Flinto prototype. That works miraculously well most of the time. Occasionally layers or links can get confused but it happens so seldom that it's never frustrating. Understanding the logic behind the re-import of layers is probably more work than fixing the odd unintentional duplicate or deletion.
The problem is when Sketch Artboards and Flinto Screens fall out of sync.
Issue: Screen duplication on Import
Intention: I'm trying to have my sketch file's Artboard replace its equivalent Flinto screen, effectively "syncing" the two. Important as this will retain the other screens links to the screen I'm replacing.
I do: I open a sketch file and check that the names of the Sketch Artboard and Flinto Screen is the same* and send it over to Flinto**. Sometimes it's been a while since I last opened the sketch file. Someone else could have worked in it.
Result: Most of the time this works as expected, I just don't know exactly why. But sometimes my Sketch Artboard does not replace the equivalent Flinto Screen but makes a new Flinto screen. The old Flinto screen inevitably shares the same name as it's new sibling but with a "1-" prepended to it.
*The name can't be the underlying mechanic as I can update the name of Flinto by updating the name of the Sketch Artboard.
**I pretty much only use the export with "Export only selected Artboards". Would be neat to save the last used options or keep it pre-selected when an Artboard is selected. Accidentally sending 14 Artboards instead of the one I'm working is a very uncomfortable experience.
Yeah, it's not based on name, but rather an internal ID.
Flinto for Mac - Masks Please god.
We have a clip group feature that allows for rectangular masks with rounded corners.
That was the main reason I never used it in the first place. The trial has expired so I'll probably never get to use it. You guys should base your trial expiration off Daniel Hoopers model (principleformac.com). The countdown only starts when you have the app running. Really smart.
Send us an email firstname.lastname@example.org, we'll be happy to extend it.
Wow, thanks. Sent!
Well, giving Flinto another shot ended rather abruptly. I remembered the #2 reason for dismissing Flinto was the poor support for popovers, dropdowns, and modals.
The Flinto team explains their reasoning as an attempt to make sure "you can never reach a state that you didn't explicitly design."
What that means is if you want a modal or menu that appears in multiple screens, you have to build multiple versions for that modal or menu. The transitions you build also won't respect scroll state either.
The folks at Flinto insist that this "prevents any kind of programming logic and bugs from entering into your prototypes". Having used InVision's solution to this problem extensively, I haven't run into any of the "programming logic" or "bugs" mentioned. Which is why I'll be sticking with InVision for now.
To the team at Flinto: you've got an awesome looking product. I love the speed & stability that a native Mac app provides. The ability to quickly string together a number of screens feels great. I hope you keep on truckin, cause I think you're headed in the right direction.
Thanks for the feedback, we can improve in this area. Overlaid content is one thing, and the simple case can be solved, but there are always questions about whether a transition out of an overlay screen should behave the same regardless of the content underneath. Easy enough for completely modal views, but if they aren't, then often you want the content below to be part of the transition and that means your transition has to account for any number of combined screens (overlay + background).
Trouble also comes when you want to represent multiple "stateful" elements in one screen. Allowing that pretty much requires programming logic and the possibility of bugs.
We provide some great tools to make seamless transitions between separate screens that feel like they are all happening within one screen. For example, it is possible to share scroll position between screens as you mentioned, using our connected layer feature. Connected scroll groups will share scroll position through transitions. This allows for some transitions that really sell the illusion that they are happening within one screen, even though they aren't. It's the best of both worlds.
If you have a specific transition or interaction you are wondering about, let me know (email@example.com) and I'll show you how to do it.
This is pain killer for designers. Keep it up guys!
This was my #1 reason for dismissing Flinto in the first place. I'll have to give it another shot.
This was a major annoyance, great to see it getting attention.