![]() ![]() The introduction of Framer X marked a critical milestone that altered the underlying formula of the product. While messiness is problematic in a production environment, it invites creativity and a problem-solving mindset during early stages when a product aspires to find out what it wants to be.Ĭhoosing the right tool for the right stage of the product design life cycle matters. We constantly worry about the future and find solace by obsessing about scalability. We go to great lengths to eradicate inefficiencies. Our inherent tendency is to get rid of messiness and tidy things up. There isn’t a red console warning reminding you of your own incompetence before you even had a chance to finish typing your line of code. ![]() Unlike the soul-crushing experience of writing your first line of code in Java, JavaScript is way more forgiving. History going all the way back to the invention of the compiler shows that ease of use and accessibility predictably trumps efficiency. That didn’t stop it from becoming one of the world’s most used programming languages. Since its early days, JavaScript has been criticized for being incomplete, messy, and unstructured. Web technologies have always been a hot mess. Some crude logic was enough to make the difference between something that felt dumb, and something that felt like an actual product. Whereas click-dummy prototypes felt like zapping through a clunky piece of presentation software, Framer’s code-based architecture offered a way to go beyond screens and micro-interactions. All the above turned Framer into my prototyping tool of choice. Its sophisticated physics engine to simulate native behavior, the split view that displays code and visual output in real time, and the seamless import to instantly get started. When I played with Framer for the first time, it was love at first sight. Any static mock could come to life in no time. It gave us the messiness and familiarity of web technologies and code, combined with the simplicity of importing from Sketch. And that’s where Framer came in.įramer filled a gap that no other prototyping tool had offered at the time. No matter what the answer is (the answer is yes for god’s sake), basic understanding of code never hurt. We have stumbled upon this question so many times that it has become as obnoxious as listening to a designer rambling about the difference between UX and UI. Should designers learn how to code? If you feel like you want to stop reading right now, I don’t blame you. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |