• Kaboom@reddthat.com
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    Cuz most modern UIs are actually web uis in disguise, and it’s easier to modify a standard progress bar than to make a new one.

    • AnExerciseInFalling@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      I still think material design 1 (which came out in 2014) is good, which focused on clarity with limited space. The problem started with material design 2 in 2018, which pushed for increased whitespace and homogeny in design. (And Microsoft’s Metro… shudder)

      Material design 1 balanced clean and readable while maintaining depth (trying to emulate 3d space by “stacking cards of content” with shadows). But since most of MD1 was guidelines instead of, like, actual components developers could use, it was a double edged sword of forcing people to be a little creative in making their own UIs but cumbersome because you had to make it all yourself

      Material design 2 tried to “fix” this by making everything simpler and shipping a ton of premade components that developers could just slap together and call it a day. Good for speeding up development, unfortunate because everything now looks the same. It’s also because of this that material design started to “break containment” and appear all over desktop applications/websites. It’s never good when a mobile design language is applied to the larger desktop space

      That’s why I really don’t mind seeing material design 1 on either mobile or desktop, because it was designed to use space efficiently and interestingly. Material design 2 on the other hand favors whitespace and speed to the detriment of us all

  • slazer2au@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    They don’t.

    They are under so much pressure to have scrum meetings that they have to sacrifice development time in order for the scrum master to keep his meeting KPI on target.

    • Geth@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      What even is this? There’s no such thing as meeting KPIs in any agile framework.

      And Scrum does allow for long meeting in case of extreme situations but any self respecting team will not take more than 10% of their total time out of a sprint for this.