|
|
|
|
|
|
by jdhn
2826 days ago
|
|
|
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. [0] https://medium.com/@samthorne/using-the-spotify-web-api-in-f... |
|
|
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.