You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there! I just watched your preview video, covering the tool and your intentions for expending and later monetizing it. As you suggested, I will offer some thoughts here—
As an interaction designer with some technical skill and interests, the us / them thing between designers and developers has always annoyed me, but I realize I'm somewhat of a wildcard heh. My reaction upon seeing the video initially was excitement- like "yes! there will finally be a smooth, official way to bring my design files into lvgl projects, without having to fiddle and re-create them". Then the notice that figma integration would be paid / considered an 'advanced' feature was presented— I completely respect your need to sustain this work / make a living from it, but isn't putting up a barrier between these two parts of the creative process also limiting the potential exposure of the tool?
If there continues to be this friction in integrating design assets into lvgl projects, it seems to me that that fewer people will attempt it, resulting in fewer examples of notably well-designed projects created and made public. My 2 cents, is that this integration should be the high baseline that the tool becomes renowned for, rather than a privilege.
That said, when considering paying for the ability to work between figma and lvgl, it would only really make sense (for me personally) if they were deeply integrated—like being able to parse the states / labels and component variants setup in figma directly- meeting the tools halfway, so that the UI hierarchy and logic established in figma could be passed on, in addition to simple things like the color and size of individual UI elements. I would hope that there might be support for things like handling constraints, exporting flattened geometry from grouped boolean vector shapes, typefaces, masks and blending modes etc.
Naturally, the more complex a design, the longer it takes to transition/reimplement in another environment, so bypassing that extra work, by supporting that complex conversion would make it much easier to justify.
Sorry if that seemed too critical, I think you've created an extraordinary tool with lvgl and looking forward to trying this out!
The text was updated successfully, but these errors were encountered:
It's awesome to hear feedback from an interaction designer. 😊
I couldn't add all the details in the video, however it's quite likely that we will enable all features for open-source projects. It will allow creating examples and experimenting freely.
To put it simple, our goal is to ask a licence fee if you also make money with the tool.
Hi there! I just watched your preview video, covering the tool and your intentions for expending and later monetizing it. As you suggested, I will offer some thoughts here—
As an interaction designer with some technical skill and interests, the us / them thing between designers and developers has always annoyed me, but I realize I'm somewhat of a wildcard heh. My reaction upon seeing the video initially was excitement- like "yes! there will finally be a smooth, official way to bring my design files into lvgl projects, without having to fiddle and re-create them". Then the notice that figma integration would be paid / considered an 'advanced' feature was presented— I completely respect your need to sustain this work / make a living from it, but isn't putting up a barrier between these two parts of the creative process also limiting the potential exposure of the tool?
If there continues to be this friction in integrating design assets into lvgl projects, it seems to me that that fewer people will attempt it, resulting in fewer examples of notably well-designed projects created and made public. My 2 cents, is that this integration should be the high baseline that the tool becomes renowned for, rather than a privilege.
That said, when considering paying for the ability to work between figma and lvgl, it would only really make sense (for me personally) if they were deeply integrated—like being able to parse the states / labels and component variants setup in figma directly- meeting the tools halfway, so that the UI hierarchy and logic established in figma could be passed on, in addition to simple things like the color and size of individual UI elements. I would hope that there might be support for things like handling constraints, exporting flattened geometry from grouped boolean vector shapes, typefaces, masks and blending modes etc.
Naturally, the more complex a design, the longer it takes to transition/reimplement in another environment, so bypassing that extra work, by supporting that complex conversion would make it much easier to justify.
Sorry if that seemed too critical, I think you've created an extraordinary tool with lvgl and looking forward to trying this out!
The text was updated successfully, but these errors were encountered: