Guidance on choosing the right framework for your project and when to use React vs. Blazor with the Strongtie Design System.
Choosing the right framework is one of the most important decisions you'll make when starting a new project. This guide will help you make an informed decision based on your team's needs, technical requirements, and long-term maintainability.
TL;DR: For new applications, we strongly recommend React. The Strongtie Design System is built with React as a first-class citizen, offering the best developer experience, performance, and long-term support.
Our Primary Recommendation: React
For new applications and projects, we recommend using React with the Strongtie Design System. Here's why:
1. Native Integration
The Strongtie Design System is built from the ground up using React. This means:
Zero friction integration – Components work out of the box with no adapters or wrappers needed
Type-safe props – Full TypeScript support with intelligent autocomplete
React hooks support – Leverage modern React patterns and hooks throughout
Consistent updates – New features and components are developed for React first
2. Ecosystem Maturity
React has the largest and most mature ecosystem in the frontend world:
👥Community Size
Over 12 million developers use React worldwide, with extensive Stack Overflow support and community resources.
📦Package Ecosystem
Over 400,000 npm packages are compatible with React, solving virtually any problem you might encounter.
💼Talent Pool
React developers are abundant and easier to hire compared to specialized framework developers.
📚Learning Resources
Thousands of tutorials, courses, documentation, and examples available for every skill level.
Note: These design systems have their own design languages that differ from Strongtie Design System. You'll need to decide whether design consistency with Strongtie or having pre-built components is more important for your project.
Option 3: Partner with Our UX Team
If you need custom Blazor components that match the Strongtie Design System exactly, our UX team can help:
Initial Consultation
Meet with our UX team to discuss your project requirements, timeline, and component needs.
Design Specifications
We'll provide detailed design specifications, Figma files, and style guidelines for your Blazor components.
Style Guide Creation
Our team will create a comprehensive Blazor-specific style guide based on Strongtie Design System principles:
CSS custom properties for design tokens
Component-specific styles and layouts
Responsive breakpoint guidelines
Accessibility requirements
Development Support
We'll provide ongoing support during development:
Design reviews of your Blazor components
Feedback on implementation details
Accessibility audits
Performance recommendations
Quality Assurance
Final review to ensure design consistency and adherence to Strongtie Design System standards.
What We Can Provide
Design tokens in CSS format – Colors, typography, spacing mapped to CSS variables
Component specifications – Detailed design specs for each component you need
Figma files – Access to Strongtie Design System Figma library
Accessibility guidelines – WCAG compliance requirements for each component
Responsive design guidance – Mobile-first breakpoints and layout patterns
Code review – Review your Blazor markup and styles for design consistency
What We Cannot Provide
C# code implementation – We don't write Blazor component logic
Blazor-specific debugging – Technical Blazor issues should be handled by your dev team
Long-term component maintenance – You'll own the code and be responsible for updates
How to Get Started
Contact the UX team to discuss your Blazor project:
Migration Support: Schedule a consultation with our architecture team
Conclusion
While we respect that every project has unique requirements and constraints, we strongly recommend React for new applications due to its superior ecosystem, performance, and first-class support in the Strongtie Design System.
If you must use Blazor, we're here to help you succeed with CSS-only styles, design consultations, and architectural guidance. However, for the best long-term maintainability, developer experience, and integration with our design system, React remains our primary recommendation.
Still unsure? Reach out to our team for a consultation. We're happy to discuss your specific use case and help you make the best decision for your project.