4 ms·

Don't make the same mistake as Twitter, putting status notifications above navigation or other crucial elements. Disabling functionality due to a temporary noti

• Kudos 15y ago
  The notifications are dismissable with a click, I don't think it's a big deal once you figure that out.
  • pixeloution 15y ago
    Very poor UX design then because there's nothing which indicates this would be the case, and no general understanding that clicking things makes them vanish.
    • a3camero 15y ago
      It would be better with at least a close button in the top right that indicates that you can close it.
      • lovskogen 15y ago
        That's not good enough. Not in my UX book at least.
  • lovskogen 15y ago
    + it's a waste of time, and clicks.
• Silhouette 15y ago
  Then again, neither is pushing the entire page down for a notice at the top of the screen, and then moving everything after a couple of seconds just as the user is about to click on a button/link/whatever. It's amazing how many sites (and browsers!) currently do this particular stupid thing.
  • leftnode 15y ago
    Yes, this 1000x over. I hate it when you have a huge DOM being pushed down by 20px for a notification, go to click on a button just as the notification is closing itself. I much prefer the notification to come down from the top, have slight transparency to show covered elements, and then a way to easily close it. Very similar to the demo.
    • lovskogen 15y ago
      Not pushing down DOM or obfuscating the navigation is not a hard design to make.