Converting Photoshop (or a similar tool) into TouchGFX automatically

[Lucas Galvanini]

Hello guys! We are building a new technology to speed up the job you currently do in TouchGFX. Basically it's a computer vision algorithm which automates the boring part of GUI implementation (components, assets and text positioning). It is still a minimum viable product, but we are asking for engineers to test and see how it can be useful for their job.

You can check in this link how it works for TouchGFX https://youtu.be/kJ1h-dJhaIE

And if you want to help us giving your honest feedback, please go to the KnowCode website and click in the "Request Early Access" button https://www.knowcode.app/

[Soren Myllerup MIKKELSEN]

Thank you @Lucas Galvanini​ for sharing this with the TouchGFX community. Looking forward to see the response.

[Romain DIELEMAN]

Looks nice, I'll try to have a look 👍

/Romain

[Michael K]

Interesting. I have a few questions:

• If I have to make the GUI in Photoshop or another image editor with the exact assets I wish to use on the embedded target, how does KnowCode save me time when compared to just making the elements directly in the designer?
• Is there planned support for having the project re-adapt to an updated photoshop image? E.g. I want to add more buttons to a project I already created in KnowCode. Can I rerun the system and have it apply my new changes?
• I assume the exported project is using a specific application template, correct? Do you have plans to support arbitrary platforms using the TouchGFX framework?
• How would I specify that a certain asset is a pushed button image or a non-pushed button image for example?
• What does the AI actually do other than find the position the assets you supply in the photoshop image?

For me, the "hard" part of using TouchGFX isn't importing or positioning my assets, it's actually building working elements and constructing an interactive application that uses those assets/elements. That is all done in the backend code and there really is no escaping that. If KnowCode is not meant for a user like me, who is it meant for?

[Lucas Galvanini]

Thank you for your questions, Michael and find here below the answers.

If I have to make the GUI in Photoshop or another image editor with the exact assets I wish to use on the embedded target, how does KnowCode save me time when compared to just making the elements directly in the designer?

For those who create the GUI directly on the TouchGFX there is no benefit. The real benefit comes when you are working with a UI/UX designers and want to convert the design into code in a faster way.

Is there planned support for having the project re-adapt to an updated photoshop image? E.g. I want to add more buttons to a project I already created in KnowCode. Can I rerun the system and have it apply my new changes?

Yes, it's in our plans for the future =)

I assume the exported project is using a specific application template, correct? Do you have plans to support arbitrary platforms using the TouchGFX framework?

Yes, we are using some templates. What kind of platform do you want to use?

How would I specify that a certain asset is a pushed button image or a non-pushed button image for example?

Not right now, but it's in our roadmap

What does the AI actually do other than find the position the assets you supply in the photoshop image?

The AI also detects the background, texts (written text, size, color), type of components (e.g. button, switch, progress bar, check box), besides placing assets in a faster way

For me, the "hard" part of using TouchGFX isn't importing or positioning my assets, it's actually building working elements and constructing an interactive application that uses those assets/elements. That is all done in the backend code and there really is no escaping that. If KnowCode is not meant for a user like me, who is it meant for?

The purpose of KnowCode AI is not to remove the hard part. The main objective is to automate the dull and time consuming part. Engineers are one of the most valuable resources in the companies and spending their time to make dull and boring tasks like choosing text size, colors or positioning for dozens screens is not efficient. We believe KnowCode is meant for guys like you to let you focus on the hard part (backend).

Be free to disagree. These feedback are important for us to see if we are in the right path

[Michael K]

Thanks for your reply.

"The purpose of KnowCode AI is not to remove the hard part. The main objective is to automate the dull and time consuming part. Engineers are one of the most valuable resources in the companies and spending their time to make dull and boring tasks like choosing text size, colors or positioning for dozens screens is not efficient."

This sentence made me realize I was thinking about it wrong. I work in a small team, so I am both the UI/UX designer and the software engineer on our product. Because I wear both hats, I didn't consider that the TouchGFX designer may be an unsuitable tool for UI/UX designers and that designing UI elements is an unsuitable task for engineers. Indeed, most of my "assets" are built from the primitives the designer provides. It suits the flat design style I'm going for, but I would definitely have more trouble if my company wanted a more skeuomorphic design for example.

What kind of platform do you want to use?

I use a custom board adapted from an application template, but others may have made projects from scratch in CubeMX so a one-size-fits all approach may not work for everyone.

[Lucas Galvanini]

It's really interesting, Michael.

And do you feel like most companies in the embedded systems market work like yours? I mean, engineers wearing both hats

Because I feel that working with an UI/UX specialist is one thing that will become more and more usual, but nowadays only few companies are doing that.

[Michael K]

I couldn't tell you for sure. Professionally I am new to the field. I work at a small company so we don't have a dedicated UX specialist. ​My skills and interests lined up with wearing both hats. I would suspect a more senior engineer would not have time/desire to do the same.

[hesam moshiri]

There is no access to the tool. I have also registered on the website, but I see no response in Email

[Lucas Galvanini]

Thanks for reaching us out, Hesam.

Please check if you have received your key now. This process is not automated yet, so it can take few hours.