<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Prudhvi Raj</title>
    <description>The latest articles on DEV Community by Prudhvi Raj (@prudhvi_raj).</description>
    <link>https://dev.to/prudhvi_raj</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3800156%2Ff7308fbf-885a-470a-946e-8d3635440cb7.jpg</url>
      <title>DEV Community: Prudhvi Raj</title>
      <link>https://dev.to/prudhvi_raj</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/prudhvi_raj"/>
    <language>en</language>
    <item>
      <title>I built a React library for Material 3 “Expressive” (with motion) — demos + docs</title>
      <dc:creator>Prudhvi Raj</dc:creator>
      <pubDate>Sun, 01 Mar 2026 16:49:14 +0000</pubDate>
      <link>https://dev.to/prudhvi_raj/i-built-a-react-library-for-material-3-expressive-with-motion-demos-docs-mb1</link>
      <guid>https://dev.to/prudhvi_raj/i-built-a-react-library-for-material-3-expressive-with-motion-demos-docs-mb1</guid>
      <description>&lt;p&gt;Hey &lt;a href="https://Dev.to" rel="noopener noreferrer"&gt;DEV&lt;/a&gt; — I’m publishing a small React component library that aims to bring the Material 3 “Expressive” visual language to React apps today.&lt;/p&gt;

&lt;p&gt;The core idea: use Google’s Material Web components under the hood, but expose ergonomic, typed React components and add the extra styling + motion needed to better match the Expressive direction and Android-like component animations.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Links&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/prudhviraj5/material-expressive-react" rel="noopener noreferrer"&gt;Github project&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://prudhviraj5.github.io/material-expressive-react/storybook/" rel="noopener noreferrer"&gt;Storybook for interactive demos&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://prudhviraj5.github.io/material-expressive-react/docs/" rel="noopener noreferrer"&gt;API docs of all components&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;What you get&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;React-friendly wrappers around Material Web components (props/events that feel like React)&lt;/li&gt;
&lt;li&gt;Bundle-friendly import paths&lt;/li&gt;
&lt;li&gt;Docs-first workflow (Storybook + API docs)&lt;/li&gt;
&lt;li&gt;Extras beyond the base web components (for example, React-first date/time pickers)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Notes&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;This is not affiliated with Google.&lt;/li&gt;
&lt;li&gt;Since these are wrappers over Custom Elements, SSR frameworks generally need a client-only boundary for rendering/registration.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Why I’m posting&lt;/strong&gt;&lt;br&gt;
If you’ve tried to adopt Material 3 Expressive in a React codebase and hit friction around Custom Elements integration, event wiring, typing, or docs, I’d love feedback on the API surface and any gaps you’d want filled next. Please leave a star on the Github if you like my project and raise issues for any bugs.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>react</category>
      <category>webdev</category>
      <category>ui</category>
    </item>
  </channel>
</rss>
