Infographic comparing two approaches for building web apps: building your own components and buying a third-party UI library

Let’s explore one of the interesting crossroads developers find themselves at when building a web application: the approach we take to building the UI components.

Considering the impact this decision will have on our ability to meet the deadline and how painful or smooth app maintenance will be afterwards, it’s worth looking into.

This decision can be boiled down to two main approaches: building your own components or buying a third-party UI library. We’ll explore the implications of each well-trodden path in eight reality-inspired categories:

  • Ticking off all project checkboxes 
  • UI library documentation 
  • Technical support
  • External dependencies 
  • Software updates 
  • Component reusability 
  • Money and return on investment 
  • The pleasure factor  

For an in-depth discussion on this subject, visit 8 Key Factors When Deciding Between Building In-House and Buying a UI Component Library (article).

Infographic comparing two approaches for building web apps: building your own components and buying a third-party UI library


nora-georgieva
About the Author

Nora Georgieva

Nora Georgieva is the Product Marketing Manager for KendoReact. She’s passionate about clear and effective communication - one of her goals is to make the marketing person that professional whom developers can count on for getting the right information at the right time to meet their challenges. In her free time, she does improv theater, goes to live music gigs and explores.

Related Posts

Comments

Comments are disabled in preview mode.