# Using Rails Views, Web Components, React, and Rails ViewComponents Together

DevFeed: [Using Rails Views, Web Components, React, and Rails ViewComponents Together](<https://devfeed.tech/articles/rails-views-web-components-react-why-make-a-choice-33528.md>)

Original publisher: [Read original article](<https://www.aha.io/engineering/articles/rails-views-web-components-react>)

Published: 2025-03-03T00:00:00Z

Content type: opinion

Language: en

Sources: [Aha! Engineering Blog](<https://devfeed.tech/sources/aha-engineering-blog.md>)

Topics: [Rails](<https://devfeed.tech/topics/rails.md>), [React](<https://devfeed.tech/topics/react.md>), [Web Components](<https://devfeed.tech/topics/web-components.md>), [Server-side rendering](<https://devfeed.tech/topics/server-side-rendering.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [vendor lock-in](<https://devfeed.tech/topics/vendor-lock-in.md>)

Tags: [components](<https://devfeed.tech/tags/components.md>), [front-end](<https://devfeed.tech/tags/front-end.md>), [opinion](<https://devfeed.tech/tags/opinion.md>), [rails](<https://devfeed.tech/tags/rails.md>), [react](<https://devfeed.tech/tags/react.md>), [server-side-rendering](<https://devfeed.tech/tags/server-side-rendering.md>), [vendor-lock-in](<https://devfeed.tech/tags/vendor-lock-in.md>)

## AI overview

The article argues that Rails views, web components, React, and Rails ViewComponents are not mutually exclusive. It explains that each approach addresses different problems and can be combined thoughtfully, including server rendering for simpler data-display features and web components for avoiding vendor lock-in.

## Source excerpt

How many times have you heard or read statements like these in tech discussions?"Everything needs to be a single-page app these days. Server-rendered templates are holding you back.""Web components are the future. Why tie yourself to any framework?"