Material UI

I know it is very difficult for professional users to understand this, but from a design perspective this is actually very well done. These animations are really helpful for people who aren't spending their whole day in front of a computer and rely on cues to help their orientation.

I've done usability tests where these "issues" came up, whenever a dropdown or any other form of interaction suddenly popped up and the user had to spend valuable time to re-focus to find out what exactly happened and if this was indeed the right control. Additionally animations are also very useful for transition purposes. Guiding the user from one screen to another can be quite stressful when it's done in an instant and the user has to understand what's happened. This is why Apple's guidelines to transition the screens in a horizontal motion were so damn good, because they allowed users to spatially recognize their "position" in the UI. And I'm glad that the MD guidelines now also state that transitions have to be spatially correct and a screen transition isn't just a window jumping out from the center of the screen. [0]

Of course these animations are only temporary and can only help you so much, but they're very good for consumers when they are noticed. And that's all they really are: helpers, not the sole messenger of the meaning of the UI.

But of course I understand the plight of delayed interactions. UI lag that is caused by hardware aside, they're really annoying. But I see that more of a problem of customization. The OS should allow to switch off any animation.

[0] http://www.google.com/design/spec/animation/meaningful-trans...

"Best practices - Support spatial relationships through consistent motions for incoming and outgoing elements."

> Why the downvotes?

Who are 'we'? What do you do? Why should I care?

Your post contains no useful information, and thus contributes nothing to the discussion. Ergo, downvotes. The only way to work out what you're talking about is to go through your comments (which I did) and synthesise based on founder bios and a job posting. Even then there is little to no concrete information about empiric.al that I could find in the few minutes I spared for this.

Here's a post that might have worked better, and maybe even could have got you some marketing/interest. I didn't downvote you the first time, but I would be far less likely to downvote this:

--- I agree completely. File management is still an unsolved problem and existing solutions are not optimal by any stretch of the imagination. It's really only getting worse as more and more user data moves to various independent and unconnected online services. Even if you manage your local files in a satisfactory manner you can't use the same system everywhere.

I'm actually actually working on a product that should help alleviate that problem. It does $ACTUAL_DETAILS and works by $IMPLEMENTATION. Our site is barebones for now (empiric.al if you want to read more about founders or sign up for information), but we're really excited about what we've built so far and aim to launch next month. Hit me up on $EMAIL if you'd like to discuss it!

Don't know if the author pushed out a fix or the problem was with Firefox but the navigation links on the left now work after FF auto-updated to v33.1

Well the fundamental flaw is that the view presented to the user is rooted in the representation the filesystem implementor chose, the user should effortlessly be able to switch between different views and add additional ones, Apples' "All My Files" together with the ability to filter and save those filters is brilliant and very much in the right direction, although it should support some form of join operation.

One idea would be, that in addition it should be possible to execute computations on the current view of the filesystem and the possible computational primitives are selected by the "type" of the files (essentially find a way to lift a typed version of the unix shell with pipes to the GUI level).

Another idea would be to emphasise versioning and time based information more. For example with the current storage capability it makes little sense for the default save operation when working on a document to be "destructively replace the old one". Obviously as a programming one is aware of that and uses version control systems, but so far I had multiple occasions when working on a collaborative project not involving code, where the versioning was done by appending suffixes to folder names.

I tried Inbox in Chrome on OS X Yosemite on rMBP 13'' last year's model and it stutters and freezes when scrolling, and takes a minute to load all dependencies. I tried in Safari too, but it does not work with Safari yet, and in Chrome it's a disaster.