For the first few scrolls the animation is very disorienting, bleeding over to peripheral vision if your monitor is wide/near enough. It doesn't help if your eyes have different graduation.
Well, you've also got Affinity Designer, which is quite good if you prefer a desktop app with no subscription fees (i.e. proper dekstop app and not an electron app).
Also Adobe XD. I know people give Adobe crap for coming to the party late, but the new tool is quite good with prototyping and web sharing built in, plus they launched freemium model. Framer is great for more advanced prototyping needs w/ animations/transitions/etc, but the XD is pretty good and fast for many needs, and it's Mac + PC.
Somehow that page manages to be just as infuriating as the one for framer. Why do I have to wait for elements to be blended in so I can read them... They should at least make them keep being displayed once they were shown.
Being able to jump back and forth between the design tools and code looks like a big andvantage for more complicated interactive components. Is that the main selling point? That you're able to compare and match visual design and code easier with this tool?
All of the tools that you mentioned don't have any actual code behind them. When I say "actual code", I mean the ability to actually go in and write lines of code to modify your prototypes.
Sketch and InVision (not sure about Figma) have "interaction" abilities, such as being able to click on a back button in one screen in order to return to a previous screen, however it's reliant on the user going into the artboard, selecting or drawing a box around an element, and then choosing from predefined interactions (tap, swipe, double tap, click) that will then result in a new artboard showing. Things can be made to look amazing, but it's all a facade.
Since Framer is code based, you can do some things that are pretty amazing for a designer, but are incredibly trivial for a developer. Want to use the Spotify API to build out a new music player, and then test it? You can do that with Framer[0], but not any of the other tools that you've mentioned. Their newest version (Framer X) just dropped recently, and since it's based on React, designers can theoretically make a widget, and then hand it off to developers in order to hook up any back end services.
> designers can theoretically make a widget, and then hand it off to developers in order to hook up any back end services.
Ughhh that's a very naive view of what a UI developer does now-a-days. We've tried visual code editors before... countless times, it never turns out well, for maintainability.
As a ux designer I dare say this is quite an interesting tool if you design software. It gives a nice blend between design and code. Your prototypes can use actual data, you can create and use complete design systems, and it’s easy to use as a designer with little code experience. It’s a huge timesaver and very powerful tool even in this first iteration.
If you work together with a programmer this tool becomes a really cool platform to combine forces.
Pretty sure other tools will adjust to this way of working.
They picked it for the beat that they could sync showcase elements to. Not the worst I've seen, and definitely better than the twee ukulele with upbeat voiceover that is the default.
How can I trust the makers of a design tool when their website is literally nauseating?