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
I work in gamedev as a UI/UX lead and I'm trying to move my team away from figma after the recent Adobe acquisition news. However, there seems to be a key feature missing that would really cause havoc with our process which is simply that you can't seem to choose an export path when saving out assets. They just end up in the default download directory.
A process that happens multiple times a day for one of our designers in figma is that they:
Go in and make updates to a set of asset files (like a bunch of icons)
Once they're edited, they select the group of updated files and hit export
They select the location on the disk (e.g. "F://Repos/ProjectName/Assets/Icons") where the previous versions of the files that need to be updated are stored
Export the updated files to that location and overwrite the existing files
Unless I'm missing something, Penpot's only option when exporting a file is to have it go through the normal download path which seems small but, in practice, completely breaks our workflow.
The main reason for this is that it's really important for our files to live in very specific locations in the file structure for our projects in order for the engine to handle auto-reimporting those assets to the project.
Adding in the step of needing to manually move the exported assets introduces a ton of room for human error -- especially when many of those files are probably going to get auto-renamed by the browser to "filename (1).png" if you forgot to go in and manually delete the previous versions of the file.
In figma, there's the additional benefit of it respecting the artboard name and it will automatically sort them into the correct folders. So for example, if you have two artboards named:
Icons / FrontEnd / T_Icon_MenuBtn
Icons / HUD / T_Icon_HitMarker
And then you just select the "/Assets/" directory when exporting, it will automatically sort those files into the "Icons / FrontEnd" and "Icons / HUD" subdirectories that already exist there which is a huge time save for us.
It seems like a small thing but it's honestly one of the only things that would prevent me from swapping over to penpot for production work!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I work in gamedev as a UI/UX lead and I'm trying to move my team away from figma after the recent Adobe acquisition news. However, there seems to be a key feature missing that would really cause havoc with our process which is simply that you can't seem to choose an export path when saving out assets. They just end up in the default download directory.
A process that happens multiple times a day for one of our designers in figma is that they:
Unless I'm missing something, Penpot's only option when exporting a file is to have it go through the normal download path which seems small but, in practice, completely breaks our workflow.
The main reason for this is that it's really important for our files to live in very specific locations in the file structure for our projects in order for the engine to handle auto-reimporting those assets to the project.
Adding in the step of needing to manually move the exported assets introduces a ton of room for human error -- especially when many of those files are probably going to get auto-renamed by the browser to "filename (1).png" if you forgot to go in and manually delete the previous versions of the file.
In figma, there's the additional benefit of it respecting the artboard name and it will automatically sort them into the correct folders. So for example, if you have two artboards named:
And then you just select the "/Assets/" directory when exporting, it will automatically sort those files into the "Icons / FrontEnd" and "Icons / HUD" subdirectories that already exist there which is a huge time save for us.
It seems like a small thing but it's honestly one of the only things that would prevent me from swapping over to penpot for production work!
Beta Was this translation helpful? Give feedback.
All reactions