React Course for Designers Update: The Course Page

almost 3 years ago from Linton Ye, Founder at jimu Labs

  • Yannik Schweinzer, almost 3 years ago

    I disagree. We're usually designing for a goal or a certain outcome. If the goal is to put together a product with React and making use of it's benefits, it makes sense to keep the strengths & constraints of the system you're building with in mind and design accordingly.

    1 point
    • Andrew C, almost 3 years ago

      I see your point — but the role of user experience is to advocate for the user and decide what the best way to do something is (through user testing we can hopefully prove ourselves wrong quickly). The understanding phase of a project is, at its core, about a divergence in thought. Telling design not to do something because it doesn't adhere to React methodologies is already compromising that.

      If the right solution (in theory) doesn't adhere to React method standards then, by logic, you've just missed the best possible outcome for the end user and degraded your user experience.

      0 points
      • Yannik Schweinzer, almost 3 years ago

        Totally agree – if we're solely designing for the user I don't think we should limit ourselves to a certain set of technologies. But sometimes we also got to keep business, existing infrastructure etc... in mind.

        Just noticed, "contraints" might be also not quite the right wording in this case. While React gives you a way for doing things, possibilities for building solutions are close to endless.

        0 points