@julia_isachenkova Thank you, Julia! Can’t wait to hear what you think—let me know if you have any feedback or run into anything exciting while trying it out!

@artyshatilov Thanks, Arty! Supporting other frameworks is definitely something we’re considering for the future. For now, we’re focusing on perfecting the experience for Tailwind and React users. Are there any frameworks in particular you’d like to see supported?

@denis_smetnev thank you :)

@esvitaly Thank you for the kind words, Vitaly! A page showcasing all the components is a fantastic idea—we’re already exploring how to make discovery and browsing even easier for users. It’s definitely on the roadmap! Regarding monetization, we’re focused on providing value first, but we’re developing marketplace now. Are there specific features you’d like to see on such a page?

@serafimcloud I'm sure you'll succeed! I don't think anything specific is required. The main thing is that it should be easy for user to stay up to date with the latest component updates.

@serafimcloud @esvitaly actually you can already discover latest components by sorting by "newest". But we will definitely make it easier

@iurii_dorofeev Thanks for the feedback! Integration with IDEs is a great point and definitely something we’re planning. Right now, we’ve already optimized for AI code editors like Lovable.dev, bolt.new, and Vercel v0. We’re building CLI for sync components with our library. Is there a specific IDE you use often where this would make the most impact for you?

@iurii_dorofeev No judgment at all, Iurii! In fact, we’re working on a CLI and possibly an extension that will allow you to sync, install, and remove components easily—making it seamless to integrate with tools like JetBrains products. Stay tuned, it’s coming soon!

@levan_kvirkvelia Thanks, Levan! We’re already using vector search with Supabase to make finding components easier based on their names, descriptions, and tags. Are you thinking about a more advanced semantic search, like using AI to understand broader queries or related concepts? Would love to hear your ideas!

@williamrobertscott Thank you so much, William! That means a lot. Bridging the gap between discovering design-engineering gems and making them accessible has been a big motivation behind 21st.dev. Are there any particular challenges or gaps you think we should focus on solving next? Your input would be incredibly valuable!

@georgiy_savchenko Yeap, using components from our registry with Lovable.dev makes it super easy for backend devs to ship frontend

@a_6 Thank you! That was one of the key ideas—to make it easy for developers to build great UIs without needing a designer. I hope it can become a GitHub for UI components and become big. Regarding the market, there’s a huge demand for ready-to-use components in the Tailwind ecosystem, especially ones that are highly customizable. What else do you think could make this tool even more useful for you?

@a_6 We’re publishing new components every day, and design engineers are also contributing through a self-serve ‘Publish Component’ feature. The library is constantly growing with high-quality additions. Is there a specific type of content or component you’d like to see more of?

@dineshan_sithamparanathan thank you 🙏🏻

@oleksii_sidorov1 Thanks, Oleksii! I’d love feedback on how intuitive the setup process feels and whether the components fit seamlessly into your workflow. If you have ideas for new features or specific components, that would be amazing to hear as well. What kind of projects do you plan to try it with?

@william_jin Thank you! Really glad you see the potential for AI projects. My favorite? Probably the evervault card components—they’re simple but endlessly flexible for showcasing data or designs. What about you? Is there a specific component or UI pattern you often look for to speed up your work?

@artyom_zhuravlev Thank you, Artyom! Early on, our community grew organically through sharing updates on Twitter and engaging with other developers in the Tailwind ecosystem. The first users came from people who were already following shadcn/ui and saw the value in extending that concept. As for attracting more developers, we focused on consistently publishing high-quality components and making the experience as seamless as possible. Do you have any suggestions on how we could expand the community further?

@artyom_zhuravlev Beyond social media, we’ve seen great results from participating in a few awesome lists on GitHub, which have helped drive organic interest. Additionally, we’ve been fortunate to get reposts from popular design engineers whose components we’ve featured, as well as mentions in three prominent developer newsletters—tldr.tech, bytes.dev, and daily.dev. Moving forward, we’re looking to explore more collaborations with open-source projects and continue building relationships within the developer community. Have you seen any other strategies or platforms that work particularly well for engaging developers?

@korzhov_dm Thank you!

@bumblebee6548 Thank you for the kind words! It’s always great to hear when our work is appreciated.

Great question! Developers can publish their own components directly to the library, making them available for others. Additionally, ‘hunters’ can discover great components made by others and publish them to the library as well. This way, the collection constantly grows with high-quality contributions from the community. Does that sound like something you’d be interested in contributing to?