Hi Hideto,

I get what you ask for but, should it not better to  be implemented in tools like Figma or Sketch, prior to spending time to develop the screens?

Regards,

Daniel

Hi Daniel,

Yes, as you said, it is also useful to realize this on design tools such as Figma and Sketch.

We are using fFgma to draw rough sketches, is Figma already equipped with a consistency check tool?

My thoughts are as follows.

Any of the following steps can be used to check design consistency.

step1:Rough sketch made with figma

step2:Mock by OutSystems

step3:Web application running in a browser

However, the end user will not see the rough sketch made with figma, but the web application made with Outsystems. Therefore, we believe that it is better to check consistency at a later step. If consistency was maintained in the rough sketch, but the developer made a mistake during the transition from Figma to OutSystems, consistency will not be guaranteed as a result.

Best Regards,

Hideto.

Hi,

You are not using the power of Figma, if you only use it for rough sketches. At Product League we use Figma up to the pixel perfect design, we do user experience validation fully with Figma, before even a coder spents his valuable time on creating a screen. Mocking, user validation, is way faster (and cheaper) doing it in Figma, than doing it by coding, and adjusting the code.

OutSystems also has a toolkit that easily maps your Figma design system to OutSystems UI, which makes it even easier and faster (and cheaper) to create screens that 100% match the design.

Right now, it looks like you are optimizing your workflow on the wrong spot ;)

Regards,

Daniel

Hi,

As you say, we have not yet fully mastered Figma.

We have no design team, only software engineers. I will try to figure out what software development process is appropriate in this context.

Thank you very much for your reply!