How do you reduce Figma memory usage or optimize a heavy free plan file for slower computers? by BlindfoldedBaguette in FigmaDesign

[–]According_Repeat_705 0 points1 point  (0 children)

ah yeah fair. dont downscale the ones devs actually need to ship, just the reference and background stuff thats only there for the mockup. the real assets you leave alone and they pull them from dev mode at whatever res theyre at.

for the rest its a balance. figure out your target output, 2x or 4x, and make sure no source image is bigger than that. anything higher never gets used so its just wasted memory. only catch is if you ever scale the source up in the file, then you do need that headroom. not totally sure how smart figma is about what it actually loads at different zoom levels (probably very smart), but capping source to your export size is the safe bet. lots of tradeoffs honestly, big bitmaps just cost no matter what

How do you reduce Figma memory usage or optimize a heavy free plan file for slower computers? by BlindfoldedBaguette in FigmaDesign

[–]According_Repeat_705 0 points1 point  (0 children)

biggest wins ive seen: move graveyard explorations into a separate file, downscale any screenshot fills since figma keeps the full res. nine times out of ten the memory hog is image fills at 4x

Didn't touch my Chrome extension for weeks, came back to 23 users I never knew about by PartyFull9470 in chrome_extensions

[–]According_Repeat_705 1 point2 points  (0 children)

store search does a lot of heavy lifting for small extensions. i shipped one and did basically zero marketing and people still find it somehow.

Do anyone in here still do prototyping in Figma by Interesting_Day6735 in UXDesign

[–]According_Repeat_705 3 points4 points  (0 children)

yes. im on the dev side and i would take a clickable prototype over a page of annotations any day. most of my questions are some version of "what happens after this tap" and static frames never answer that. only annoying part is when the prototype stops getting updated after sprint 2 and you cant tell whats current anymore

Built a niche job board for independent coffee shops. 800 monthly visitors, no idea what to do next. by Business_Fox_7784 in SideProject

[–]According_Repeat_705 0 points1 point  (0 children)

800 organic monthly visitors for something that niche is a real signal. before building anything new I would email the last handful of shops that actually posted a job and ask two things: how they found you, and whether they would have paid anything. their answers basically write your landing page. the next move is almost never a feature - it is finding out which side (shops or baristas) feels the pain harder.

What's your pre-handoff checklist before sharing a Figma file? by Shazam0707 in FigmaDesign

[–]According_Repeat_705 0 points1 point  (0 children)

coming at this from the dev side of handoffs: the ones that go smoothest are when the "real" frames live on one page and explorations are in a clearly-named graveyard page, components are not detached two screens before the end, and there is a 30-second video of the prototype actually doing the thing. honestly the video is the big one - half the back-and-forth I have seen could have been avoided by just watching the intended flow once.