@DougCollinsUX
Imagine working in your usual Figma'ish interface, but instead of manipulating vector graphics you'd be manipulating real code visually. This is what it's like working in
@HenosiaHQ
No more handoff gap! See more on
#designheartscode
#onesourceoftruth
Whew! What a rush it was to do a first public appearance with Henosia! 🤩 Thankfully the crowd at
@IDAdk
s Driving IT Aarhus conference were a super engaged audience with great questions. 🙋
We'll do it again: Henosia - coming to a venue near you! 😉💜💜
#IDA
#designheartscode
A thread from our Co-Founder
@Jannejuljensen
about the backstory of how Henosia came into being 💜💜. Tell us, what has been your biggest painpoint in the existing design/dev collaboration process?
#designheartscode
For about the sixth time in three days, I've drifted into architecting Figma component anatomy and properties (the COMPROMISED APPROXIMATION of the solution) instead of modeling design to identify how the code may work (the REAL solution).
Ugh, keep the eye on the prize!
@NegraAhmetspah1
@JanneJulJensen
Yup, that's what we do 🤩💜💜 We believe it is the right way and the only way to break down today's silos of design and development (and other silos too), and join us all together to become product builders 🙂
#designheartscode
@AEVolucion
@DougCollinsUX
Except this isn't an export or generated code :-) This is code while you work with it. No changing back and forth between data formats. The same format when you pull it in, work with it and push it back into the code repo. 💜💜
The upper limit of vector-based design is fast approaching.
Architecting the props of a vector-based component is another area that's become increasingly complex. A cost that's paid by design teams, without them getting the many benefits of code-based props back in return.
Vector-based
#UX
Design tools have reached a point where composing components has become more complicated than what's done in code.
In code you compose via trees (e.g. React children), and vector-graphics tools had to invent terms like instance swapping, overrides and detaching.
Design tool industry: *invests billions in vector graphics* 💸
@steveruizok
: "You're just faking everything, all the time" 🤷♂️
Steve, we hear you. We'll only ever feature real arrows 💜
Fantastic discussion on the lack of "developer and designer" tools by
@Mappletons
(who promised not to talk about tools but couldn't resist 😁) &
@steveruizok
:
That's why we're building
@HenosiaHQ
! Big update to share soon on in-medium real-time collab.
Was lucky enough to have a preview of the
@HenosiaHQ
design tool this morning. Wow!
This has the opportunity to revolutionise the design and build workflow for teams.
Watch this space 👀
@CoxDigitalcl
@DougCollinsUX
Actually, we don't export to or generate code. We work IN code meaning no loss of details going from one data format to another. Just pull it from the code repo, work with it on the canvas, and when happy with it, push it back to the code repo. No format change anywhere.💜💜
Code-native
#UX
Design tools are the successors to vector-based design tools. Here's why:
Nothing in the laws of physics says that code updates must be slower than vector-graphics updates on a design canvas.
But why should designers, developers, and product teams care about
@CoxDigitalcl
@DougCollinsUX
Yep, just checked and you're in the HUG 💜
We're keeping things simple for now and focusing our time on the product. But thanks for the heads up 😁
@krystiangebis
@jimmeyer
@shadcn
@radix_ui
@tailwindcss
@nextjs
It is for sure something we want to support, but you're right, it's not in the near future, as there are more pressing things to support first. But you can (if you can code) use the animation features in Tailwind or libraries like Framer Motion since that's just React components.
Design and Code met in 2020, introduced by
@jimmeyer
and
@JanneJulJensen
who felt the pains of them living apart: Handoff gap & keeping design and code synced. Well, no more: Design and Code just moved in together in Henosia!💜💑
#designheartscode
#Henosia
Want to shout from the rooftops how upcoming changes in
@HenosiaHQ
dramatically accelerates designer and developer collaboration, but it has to wait until we've presented at
@IDAdk
Driving IT in Copenhagen and
@BuildStuffConf
in Vilnius.
How do people do it?!😬😂
#UX
#ReactJS
@amrancz
Thanks Adam. We’ve prototyped how to blend creative freedom on the canvas with more structured approaches, and initial user feedback has been very positive. We’ll share more as soon as we can🙂
Imagine a new magic-wand like technology that would allow industrial designers to make gestures towards their work, and the materials would instantly bend, twist, and change shape based on their intent.
@HenosiaHQ
makes this a reality for code in digital products.