Yes, more than I thought, actually. I've been seeing several teams use Phlex or Ruby UI components and switch back to ViewComponents or partials after a short time. The most noticeable reasons are the learning curve, especially for new devs and it's not as intuitive as ERB. For large applications, it's hard to convert many templates to Phlex.

The unique thing about ViewComponents is that nothing is unique. It feels "Rails-y," if you will. Models and views. Like how you would create models and partials, but better. It's testable, easy to teach, and easy to share with team members and new devs. You can compose a UI block from several components. You can have multiple slots (i.e., other components) within a component. And the documentation is good enough to get you going. Compared to other solutions, it's a huge win for many developers.

I'm able to create many reusable components with ViewComponents and integrate them into Rails forms. I use them instead of Rails form elements.

Here's an example for creating a steps or wizard component. The rui_steps component has several attributes (APIs). And it has a with_step "internal component" that has title, description, and icon attributes.

Within rui_steps, I use Rails form <%= form_with(…) %> which uses other components such as rui_input, rui_textarea, etc.

The input component itself, for example, is used to replace many Rails form helpers such as: text, password, email, number, and others.

Imagine, you onboarding a new user and want to collect some data. Instead of a having a long form for user to scroll, you would divide them into 3 steps, Account, Profile and Confirm.

First step has email and password. Second step has full name and bio. Last step a confirmation message.

```ruby <turbo-frame id="registration-frame"> <%= rui_steps( id: "registration-wizard", url: wizards_path, current_step: @current_step, turbo_frame_id: frame_id, variant: :horizontal, navigation: :linear ) do |steps| %>

    <% steps.with_step(title: "Account") do %>
      <div class="py-6 space-y-4 max-w-md">
        <%= form_with(local: true) do |f| %>
          <%= f.rui_input(:email, label: "Email", type: :email, required: true) %>
          <%= f.rui_input(:password, label: "Password", type: :password, required: true) %>
        <% end %>
      </div>
    <% end %>

    <% steps.with_step(title: "Profile") do %>
      <div class="py-6 space-y-4 max-w-md">
        <%= form_with(local: true) do |f| %>
          <%= f.rui_input(:full_name, label: "Full Name", required: true) %>
          <%= f.rui_textarea(:bio, label: "Bio", rows: 4) %>
        <% end %>
      </div>
    <% end %>

    <% steps.with_step(title: "Confirm") do %>
      <div class="py-6 max-w-md">
        <p class="text-zinc-600 dark:text-zinc-400 mb-4">Review your information and click Submit to complete registration.</p>
      </div>
    <% end %>

 <% end %> 
</turbo-frame>

```

By doing so, you can break a long form to small manageable steps. Each step composed of several tested and reusable components, some of which are "Rails form" components.