Advertisement

A Guide to Component-based Architecture and Design Episode 1: What are the Benefits?

A Guide to Component-based Architecture and Design Episode 1: What are the Benefits? Read our 2019 Guide: Build, Understand, and Benefit from Component Libraries for Advanced Organizational Efficiency:

Watch our 2019 webinar: Improve Organizational Efficiency and UX with Component Libraries and Design Systems:

Read our 2019 Guide: Can Your Business Benefit from a Design System?

See our Component-based Architecture and Design vlog in its entirety:

This video blog series is a comprehensive guide to component-based architecture and design and how a business can benefit from it. Withing in our team of experts cover aspects such as the various business benefits, the definition of atomic design, how building a component-based experience affects design, technical considerations, and the cultural implications.

This episode focuses on the benefits of component-based architecture and design.

You have to be able to adopt things like component libraries to make sure that you can grow with the opportunities that are there for your business.

[inaudible]

What is the benefit of using component-based design and architecture? I think that that is the question that lies at the heart of why you should consider having a design system, which is a larger topic that we can, we'll get into in other pieces of content. But I think that your component library is something that's going to enable you to build experiences that don't just depend on understanding how one screen flows together and how things work together across a bunch of screens. You think in terms of systems. And so what it allows you to do is to create methods, create systems for how things fit together, and you create a system for your experience essentially. And so your functionality that comes from these components can be exported to anything that you need them to. They're reusable. It creates efficiency because developers aren't coding things over and over again.

Designers aren't designing things over and over again. You can have this problem on a small team, but you can actually have this problem on a large team to an even a greater detriment because when your team is large enough that your designers don't know what the other's working on you can actually get situations where they try to touch the same things or they do things over and over again and there are little differences between them. So when your customer experiences your product, they actually notice those inconsistencies, or it's something that doesn't feel right, or in maintenance, you notice the inconsistencies and you realize it's going to be a nightmare to clean it up. And so as you grow, this helps you to be able to have consistency in a way that doesn't cost you a ton of money and a ton of heartache in trying to do that retroactively. It's there from the beginning, just in the very way that you're working and that scales, that will always scale. And so you have to, you have to be able to adopt things like component libraries to make sure that you can grow with the opportunities that are there for your business.

So what are the benefits of component-based design and architecture? So Devin touched a little bit on it from a design perspective. I think when we think about specifically architecture and architecture design, this is nothing new. This has existed even in with infrastructure and today you actually see it with how modern browsers work with web components themselves. So think custom HTML elements. The focus here is on interoperability. So how data transfers from one system-isolated component to another and also encapsulations so that they are self-contained from a logic and a state perspective.

So as mentioned, interoperability and encapsulation enable scalability and scalability is also enabled by reuse of code. And essentially we can think of the reason that we want to do this is obviously with your businesses growing, you want your technology to grow with it in an easy way. And some ways to do this is essentially to think about how these things are built in isolation, and so that they can be reused across maybe the actual application you're only working on across multiple views, but also as you extend and you start building multiple applications, you can start reusing these components that way as well.

Continue reading at:

engineering,component libraries,design,code,design systems,technology,component-based architecture,

Post a Comment

0 Comments