• laurelraven@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    0
    ·
    7 months ago

    That’s wild, flat out telling the community they’re going to refuse to implement something if they want it enough to ask for it

    I won’t presume how easy or hard implementing that would be, but I have a hard time believing it would be so significant that this stance makes any sense at all

      • laurelraven@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        0
        ·
        7 months ago

        Okay? Did I say anything about that being owed? They’re also not owed a community using their community project, so acting like that just makes no sense and seems counter to a goal of building or maintaining an active community of users

        I didn’t say they aren’t allowed to do that so maybe go have that argument with someone who did.

    • Fisch@discuss.tchncs.de
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      7 months ago

      The reasoning for only allowing predefined colors was that, apparently, developers need to be able to test against every color and that Android’s Material You is a total mess. I disagree with both of that, Material You seems to be working quite fine (I’ve also made apps myself) and I don’t get what developers would need to test with accent colors. I couldn’t voice my opinion tho cause then the whole thing would’ve been canned.

      • LainTrain@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        0
        ·
        6 months ago

        Android’s Material You is absolutely disgusting though with it’s bizarre theming choices and piss-like pastels and fucked notification shade and the dark mode circle jerk and it frankly seems to be an attempt to assassinate what material design ubiquitous and a defining tech aesthetic of the late 2010s