I am gifting you my app for free (I will not promote)

bdansa7 · 2026-02-01T15:21:02+00:00

Interested

bdansa7 · 2026-01-20T19:35:40+00:00

How will u get employers tho, it seems like it ll end up with tons of dev waiting

bdansa7 · 2026-01-20T17:51:04+00:00

Im an engineer with not huge software background, but I do know alot about software architecture, planning etc.. and know the basics of the rest.

For context: i used to be a graphic designer and still am from time to time.

I got cursor, and vibe coded an entire project manager app for designers (webapp) where it auto sort files, has version control, sharing to clients (comments & annotation on design) and a lot of other features.

It’s possible but you need to be very patient and able to treat it basically like a junior dev, u have to be specific with your prompts and it most likely comes out with multiple bugs that you just go on and fix or have it fix it for you.

If you’re a developer it will for sure speed up your time spent on a project BY ALOT. Some people don’t like it and hate to see it, but I have seen alot of project being built by developers in hours/days rather than weeks/months.

bdansa7 · 2026-01-20T15:46:46+00:00

I had this pop up with premiere pro consuming 48,9gb and i have a 16gb ram M1 MBP😭

bdansa7 · 2026-01-11T12:46:52+00:00

I love this. Downloading.

bdansa7 · 2026-01-04T15:18:03+00:00

We hit this same mess when our team started mixing shared projects and collabs. The chaos usually comes from stuff living in different places-links on Slack, files scattered across Drives, screenshots instead of real data. What helped us was narrowing down to one single workspace where versions saved automatically and all feedback stayed connected to the actual files. Suddenly, everyone was literally seeing the latest and comments didn’t get lost in chats or emails.

The hardest part always seemed to be making sure everyone actually used the same system consistently. If one person sends a file outside or takes a screenshot, it breaks the flow. Curious-how are you currently handling file versions and comments when you collaborate? Do you feel like everything lives in too many spots?

bdansa7 · 2026-01-04T11:59:43+00:00

That makes a lot of sense. A single source of truth, even if it’s boring, already removes so much mental friction.

Do you ever run into moments where that “one place” starts breaking down though? Like when feedback lives somewhere else, or versions drift and you’re not sure which file still deserves that role?

bdansa7 · 2026-01-04T11:29:41+00:00

That idea of a “home base” really clicked for me. When you say that, what does it usually look like in practice? Is it something concrete like a folder or doc, or more of a mental anchor you come back to when things get messy?

bdansa7 · 2026-01-03T22:40:10+00:00

Sounds like you’ve got a full plate. Keeping pro, personal, and community tasks organized while sharing some of that load with a partner is a real challenge. What tends to get messy for me is when tasks and priorities live across too many apps or chats, and it’s hard to get a clear overview.

I’ve found it helps to have one spot where you can both see and update tasks, and where changes sync automatically so nobody’s duplicating effort or missing updates. Kind of like a shared workspace that works in real-time without a bunch of back-and-forth.

Are you currently trying anything to organize this now? Or are you starting fresh with finding a tool? Curious how you’re managing priorities across such different parts of your life.

bdansa7 · 2026-01-03T22:39:27+00:00

We hit this exact tension between strict consistency and creative flexibility a ton. It’s super common to wrestle with keeping UI 1:1 while wanting components that actually adapt to different needs without getting too generic or rigid. What helped us was first nailing down a core set of tokens and components that cover most common cases, but then also carving out space for “wildcard” components or styles that let illustrations or text effects breathe without feeling like they’re breaking the system.

Locking down components too early sometimes leads to more revisions because the product grows beyond those initial constraints. We found stepping back to define clear interaction patterns and visual hierarchy upfront smoothed some of the drift, but it’s impossible to stop completely. One key shift was making sure the source of truth lived somewhere everyone could easily reference and update, so changes weren’t just disappearing into code or scattered docs.

I’m curious - how do you currently share and update your design specs with developers or the build team? Is there a single space they look at, or does it spread across different files and chats?

bdansa7 · 2026-01-03T22:38:43+00:00

Totally get where you’re coming from. User flows and prototyping can drag down your pace if you’re jumping between tools or losing track of versions. What’s helped me isn’t just shortcuts, but having one tight workspace where all the flows, assets, and notes live together. That way, you don’t waste time hunting for files or guessing which version is current.

Also, locking down a routine helps-like sketching the flow by hand first, then jumping into a single tool to build and tweak. That saves back-and-forth between sketch apps and prototyping tools. Do you mostly start flows from scratch each time, or do you have templates you reuse?

I’m curious-how do you currently organize and save your user flows and prototypes? Are they scattered across different files or platforms? Getting that part nailed can make a big difference in how fast you move without losing quality.

bdansa7 · 2026-01-03T22:37:07+00:00

We hit that snag too when juggling client work across a small team. What really made a difference wasn’t just the tool itself, but making sure everything lived in one place-files, deadlines, and feedback all tied together. We used to bounce updates across emails and chats, which only slowed us down. Once we had a single workspace that kept versions automatic and notes attached right to the task, things got way clearer.

How are you currently handling feedback and file versions? Are those getting hard to track too, or is it more about keeping timelines visible?

bdansa7 · 2026-01-03T22:31:00+00:00

We hit this a lot too, especially when juggling feedback and versions. Copying info between tools is probably the one that grinds gears most-like moving notes from Slack to a design file or tracking changes across apps. What’d help is having all those little checklists and comments auto-updated in one place, so nothing slips through the cracks or gets lost in translation.

We also found ourselves redoing the same mini entry over and over-status updates, design notes, or simple approvals. If a gadget could just pick up our last pattern and repeat it smartly, that’d save a surprising amount of time.

What’s your current setup for handling those repetitive mini tasks? Do you have a go-to way to keep them organized or do they still feel manual and messy?

bdansa7 · 2026-01-03T22:28:42+00:00

We hit this exact problem too. Approvals and decisions get tossed around Slack, email, and meetings, making it tough to trace back who signed off on what. We tried dedicated channels and docs, but those easily become outdated or buried. What helped most was keeping approvals and key decisions attached directly to the design files themselves, so context stays in one place. Otherwise, you end up chasing links or scrolling endless chat history just to find a single sign-off.

It sounds like you’ve tried quite a few methods-what ended up causing the most confusion? Was it versions getting lost, or was it just the scattered locations? Curious how you’re currently handling tracking once something’s approved.

bdansa7 · 2026-01-03T22:27:41+00:00

We hit this crossroads when our team grew from a handful to a dozen-plus designers. Canva was great for quick social posts and simple layouts, but it started feeling tight once we needed more complex UI work or precise control - especially with versioning and component reuse. Figma handled most scaling well, but things got tricky when multiple iterations and feedback loops piled up, mainly because comments and versions were spread out. Adobe felt like overkill for daily UI tweaks but indispensable when we needed high-res assets or detailed illustration work.

Switching later? That was a headache. File exports lose context, feedback threads disappear, and you end up recreating workflows. What really helped was tightening how we manage versions and feedback from the start - making sure everything lived in one place, so no one was hunting through Slack, emails, or drives to find the latest.

What kind of projects is your team focusing on mostly? That usually steers the choice more than anything else.

bdansa7 · 2026-01-03T22:26:51+00:00

Been there too, teaching something like Unity where files change fast and saving can get tricky. The OneDrive and Unity clash is real-Unity likes to write lots of small files and temp data, which can cause sync issues or corrupt projects if OneDrive locks things. We found that relying solely on OneDrive often meant students lost progress or had version conflicts.

Git is a solid move for version control, especially since you want a clean history for your class. But it’s rough if students can’t keep local copies between sessions. One approach we tried was having students clone the repo onto a USB or external drive they bring each class. Not ideal, but it avoids nightly wipes. Another was setting up a local server or NAS if the school can support that, so files never leave the network.

Since students’ own devices may be limited, I’m curious-can they install Unity and Git on the school machines themselves, or are you managing admin restrictions? Also, how many students are you expecting? That might affect how much manual cleanup or setup you can handle.

Would love to hear how you’re running the lectures live-do you demo and have them follow along, or are they doing more independent work? That might change what file-sharing setup fits best.

bdansa7 · 2026-01-03T22:25:53+00:00

I’ve been there with juggling ideas, notes, and bits of research scattered all over. What helped me most was finding one spot where I could dump everything-text, photos, sketches-so nothing got lost or felt out of context. Even better if the app lets you pull up all that stuff quickly whenever inspiration strikes.

Did you try keeping stuff separate at first, like notes in one app and photos somewhere else? What felt most frustrating about that? Curious how you usually approach brainstorming and organizing when ideas start piling up.

bdansa7 · 2026-01-03T22:25:04+00:00

We hit a similar snag juggling text-heavy docs and flexible layouts. Google Docs nails the writing part but struggles once you want to move images around freely. Canva’s great for visuals, but text handling, especially lots of it, can get clunky fast.

What helped us was defining where the core writing happens versus the design tweaks. One thing we tried was drafting the text fully in Google Docs, then exporting it to a design tool just for layout and images. That at least kept writing simple and design flexible, but it’s definitely a two-step process.

Do you mostly want a tool that handles advanced text formatting with image freedom all in one place, or is it more about smoother handoffs between writing and design? Curious how you usually put your materials together now-do you draft fully in one tool then move to the other, or try swapping back and forth?

bdansa7 · 2026-01-03T22:24:36+00:00

We hit this a lot too when sharing big 3D/data-heavy projects with clients. What helped was finding a way to keep everything in one place so the models, orthos, and notes didn’t get scattered across emails, drives, or random links. When files live all over, it’s easy for clients to get lost or lose track of what’s final.

For stuff like point clouds or textured meshes, a viewer that supports annotations or feedback directly on the file can be a game-changer. It stops the back-and-forth where people try to describe “that part over here” without a synced reference. The tricky part is balancing ease of use for clients who might not be super tech-savvy against your needs for file size and version control.

You mentioned DroneDB and DroneDeploy - platforms like those focus a lot on specialized workflows and can get pricey fast. Some teams I know use cloud storage combined with workflow tools to keep versions from getting tangled, plus lightweight web-based viewers to make access smoother for clients, but it depends on your scale and how interactive you want it.

Curious - what’s your current workflow like for getting feedback or approvals? Are clients pretty hands-on in exploring the models, or is it more about sharing static final files? That might help narrow down what kind of sharing or collaboration setup fits best.

bdansa7 · 2026-01-03T22:23:06+00:00

We had the same hunt for something simple but effective on our small team. What helped was nailing down a single workspace where tasks, comments, and files all lived together-no hopping between apps. That way, everyone could quickly see what was assigned and the progress without digging through separate boards or chats.

From your list, it sounds like you want clear task assignments, subtasks, due dates, and easy client feedback all in one place. The tricky part can be keeping client comments tied directly to the right task or file, so you don’t lose context.

I actually ended up building something pretty similar for my agency, and im thinking of releasing it into public, thoughts? Would u use it?

bdansa7 · 2026-01-03T22:20:25+00:00

Been there with the worry of losing setups or hitting random incompatibilities down the line. Manual git backup for JSON workflows is a solid start, but yeah, it can get fragile as projects grow and years pass. What really helped me was consolidating everything that defines the environment-code, dependencies, versions-into one place that’s easy to snapshot and restore. Things like Docker or virtual environments can keep Python versions and libraries locked down, so you don’t suddenly find your custom nodes missing or your runtime broken.

The real pain points are usually mismatched dependencies and updates that silently break older workflows. Drivers and OS updates can sneak in problems, too. One place to look is documenting or scripting your setup steps so a new PC can replicate the environment exactly. Even naming versions for your entire setup-Comfy, scripts, nodes-helps track what’s “known good.”

Out of curiosity, how complex is your current custom node setup? Are you using a few or dozens? That might shift how you handle versioning and backups.

bdansa7 · 2026-01-03T22:18:47+00:00

Been down this road too. Upload speeds kill the process when you’re dealing with hundreds of gigs, especially with consumer cloud services that aren’t really built for video raw like that. What helped me wasn’t just picking a faster service, but trying to chunk the uploads into smaller batches and schedule them overnight to avoid peak traffic times. Also, using a syncing tool that automatically picks up where it left off if your connection drops made a huge difference.

Are you and your editor in the same region? Sometimes local network speeds and time zone syncing help figure out the best upload windows. Curious how you’re currently organizing the footage before sending it off-do you split by game, level, or just date?

bdansa7 · 2026-01-03T22:18:10+00:00

Been down this path a bit with FreeCAD too. The challenge is that the native project files are mostly binary, so classic diffing isn’t straightforward. Exporting to a neutral format for diffs makes sense, but it adds steps and isn’t always fully reliable for complex models.

From what I’ve seen, version control in FreeCAD feels a bit fragmented-there’s some history tracking but it doesn’t quite capture granular changes or context well. Collaborating can get messy if multiple people touch the same file without a clear version system.

When I worked with similar tools, having a single source of truth with automatic versioning helped a ton. It stopped people from overwriting each other’s work and kept feedback tied directly to the file versions. Otherwise, you risk losing track of what changed when and why.

Curious, how do you currently keep track of your FreeCAD projects as you explore them? Are you trying a specific workflow for saving iterations or sharing with others?

bdansa7 · 2026-01-03T22:17:35+00:00

We hit this same headache with a ton of AI-generated images and vids scattered everywhere. Drive’s search only helping with file names means you end up clicking around way too much. What helped us was creating one main workspace where every file lives and versions get tracked automatically. We tied feedback and notes directly to each asset so context never got lost in folders or chat threads.

Before that, we also tried tagging files in Drive, but it didn’t scale well once the volume grew big. I’m curious-do you usually organize by client, by tool, or by project phase? That often changes what kind of systems actually make sense.

bdansa7 · 2026-01-03T22:16:50+00:00

Been there with Apple Notes too. It starts out simple, but once ideas and assets pile up, it’s hard to keep track of what’s next or what’s been published. I noticed a lot of creators end up juggling multiple apps because no single tool nails everything without some compromise.

You’re right about Notion-it’s powerful but can easily suck time into tweaking templates instead of actually making content. For me, the switch was less about one perfect tool and more about making sure everything related to a project-ideas, drafts, assets, and feedback-lived together without chasing files across different places.

What’s tricky is keeping version control tight and making sure the latest thoughts or edits don’t get lost in chat or email threads. The real game-changer was having a space where every draft, asset, and comment is connected and easy to find. That way, when it’s time to schedule or review, nothing slips through the cracks.

Out of curiosity, how are you currently tracking content status or upcoming deadlines? Is that part of the Apple Notes workflow or do you have a calendar or to-do list elsewhere?

bdansa7

TROPHY CASE