|
|
|
|
|
|
by rroose
899 days ago
|
|
|
I think (or hope) it's some combination between using real code (such as Storybook) in combination with a GUI. This has the following benefits:
- There is only source of truth and it's the code
- People who can't code (most designers) can still build prototypes with available components
- No (manual) synchronization between code a drawing tool (Figma, Penpot) needed At the moment it looks like UXPin is going in this direction. |
|
|
On the other hand, if by "writing code" we mean the literal act of writing something that both a human and a computer can understand, then that's a different question. Designers need to express nuance, and GUI tools are limited in their ability to handle complexity. There's a reason visual programming tools haven't overtaken code.
What I'm getting at is that there very well could be a "language" specifically tailored for UI/UX designers, that allows them to specify their design decisions for the presentational layer of the application. If you had such a language, you could create a toolchain on top of it, which produces real code for developers to consume however they wish.
I'm (slowly but steadily) working on this exact thing: https://matry.design