Forum Discussion
Files On-Demand for macOS QA
Hello there!
2.24.22 UPDATE: We've been listening to your feedback, and we've made some design changes. We're releasing a new version that addresses the most common themes and makes it easier ...
A few bits of feedback:
- Updates on the blog are helpful knowing it is there.
- That said, no one is ever checking all of the blogs for updates. For what it is worth, reaching users is hard hence why breaking user experience really should be a last resort. Every time one of the plethora of programs I have upgrades, I am not checking blogs.
Example: Moving onedrive storage to under ~/Library seems really hard to justify what the pizaz and OMG look what we get functionality is from such a move. Absolute file paths are always going to be a problem and kinda once you set it, sorry you're stuck with it. Powershell has that all over the place. It isn't a new lesson and moving it wasn't fresh or new. We already had shortcuts on the left bar.
I would also argue that unless you can really say why moving to ~/Library just had to happen, it's another miss because I don't feel like as a user, I should have to care. Is this an Apple Library requirement? Great, still put in a workaround or fix to preserve what I had. You just made a system specific issue, a problem where my outcome is a need to reliably store / manage files and content I have lost faith in. I feel like this change seriously damaged your message.
I am not trying to sound like I am harping but I will also say that 'reinventing' things means also understanding where the technical debt can bite you. As users we feel bitten pretty bad.
- Updates on the blog are helpful knowing it is there.
- That said, no one is ever checking all of the blogs for updates. For what it is worth, reaching users is hard hence why breaking user experience really should be a last resort. Every time one of the plethora of programs I have upgrades, I am not checking blogs.
Example: Moving onedrive storage to under ~/Library seems really hard to justify what the pizaz and OMG look what we get functionality is from such a move. Absolute file paths are always going to be a problem and kinda once you set it, sorry you're stuck with it. Powershell has that all over the place. It isn't a new lesson and moving it wasn't fresh or new. We already had shortcuts on the left bar.
I would also argue that unless you can really say why moving to ~/Library just had to happen, it's another miss because I don't feel like as a user, I should have to care. Is this an Apple Library requirement? Great, still put in a workaround or fix to preserve what I had. You just made a system specific issue, a problem where my outcome is a need to reliably store / manage files and content I have lost faith in. I feel like this change seriously damaged your message.
I am not trying to sound like I am harping but I will also say that 'reinventing' things means also understanding where the technical debt can bite you. As users we feel bitten pretty bad.