Anonymous

My feedback

  1. 7,900 votes
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)

      We’ll send you updates on this idea

      965 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
      planned  ·  Suphatra responded

      Hi everyone, thank you for your patience since the last update.

      We want to extend a huge thanks to all of you who have engaged with us on this topic of compact chat. Your input has been invaluable and helped inform our design and decision-making.

      As we look to 2019, we will be pursuing plans to continue to make the product more and more space efficient. We see this as a guiding design principle, as well as a backlog of requests from UserVoice that we catalogue, discuss, debate, brainstorm and problem solve.

      This principle is also why we will not be making a sharp design turn towards a permanently heavy dense design. Our user base is a wide range of people — such as high school students, the visually impaired, open source developers, and your every day knowledge worker. Because of our broad reach, we must maintain a standard of…

      Anonymous supported this idea  · 
    • 17 votes
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)

        We’ll send you updates on this idea

        3 comments  ·  Public » UX/Design  ·  Flag idea as inappropriate…  ·  Admin →
        Anonymous commented  · 

        This would be perfect if implemented on a per-channel basis, however, it would be even more awesome if the user on the end got the choice to enable it just for client side view.

        The amount of whitespace for simple things in Teams makes the client almost impossible to use in real world incident management.

        Anonymous supported this idea  · 

      Feedback and Knowledge Base