Blazor Best Practices Borrowed From ReactJS

Live Webinar
Webinar Agenda

Blazor took a lot of design decisions from React and other frontend frameworks and as a stateful component-based UI framework there is quite a bit of experience that can be transferred from one to the other.

With any new technology, there is going to be a learning period as we experiment and gain experience and learn from mistakes made. After having deployed production Blazor apps for two different clients, I realized I was able to avoid some costly mistakes and design decisions early on by leveraging my prior experience with React and other frontend frameworks. Now I want to pass that knowledge on to you.

In this talk, I'll share some Blazor best practices as well as common pitfalls to avoid and lessons learned from over 7 years of working with stateful component-based frameworks.

Takeaways:

  • How to decide where different bits of state should live
  • Error handling with Error Boundaries
  • Tips for designing reusable components
  • When is it appropriate to refactor markup into a reusable component
  • Tips for designing testable components
  • Handling cross-cutting concerns

Speaking to you

Brandon Pugh
Brandon has been in love with the web his whole adult life and has been building professional web applications for over 12 years in the .NET space. Being a consultant for the last 7 years has given him the opportunity to work with a variety of technologies and help transform organizations across various industries. He has a passion for all things related to web, UI/UX, accessibility, automation, and developer experience.