We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
When someone requests a file using your request a file tool, the person who uploads the file's name gets added to the file name eg janedoe_filea.pdf . This is really frustrating and I end up having t...
jonauz
4 years agoNew member | Level 2
It is such a lack of basic understanding from Dropbox team! They are so stuburn and clueless what we want. Product should be developed from customers perspective, not from what ever your engineers or product owners came up and their lack of capability to understand a bigger majority has to be pain for everyone. Why?! Absurd.
If I upload file, I don't want it to be modified! And there is nothing else to discuss here! but no, wait, Dropbox team is explaining how we supposed to want to use it, in pain and frustration, and again.. why? ..well, because they do see excuse to spend money and time to improve it, or rather fix underlying problem!
And the funny thing is, when Dropbox team gives such silly response "we can't do that now", all the rest of industry is laughing, because it can easily be done, when you want. So it's just a politely brushing all the heat into sink and flushing it down.
If your engineers can't do it, hire the ones which can, and there is plenty of them capable of making all of those improvements and missing features on Dropbox, seriously.
If I ask some one to upload photo of me, that they took, it's is very obvious I don't want other persons name on photo of me. That is so silly, that any responsible employee would say "NO" to this. My guess is that Dropbox either has an underlying technical debt problem, that is blocking them do things the right way, or maybe just poor managers, or even chiefs.
If file with same name is already uploaded, very basic thing to do, is to add an incremental number at the end of file. It's supper old solution. Do you have just junior engineers working at Dropbox?
At least make option should File Upload feature require or not some prefix for file name. It me, the requester, sets this as required, then require with clear intention why. Now, it's unclear to anybody, and in result creates even bigger frustration to everybody. Everybody! This would be no brainer issue to any self-respected team to spot it and solve it, and would be embarrassed and want to resolve it even more, if clients keeps complaining as they do here! Also, prefix, not required in most of the cases.. and yet, you decide it will be and you force everyone to obey your aggressive attitude towards providing poor product experience and ignoring customer needs.