4 ms·
Adam, Steve, have you considered building a marketplace for Tailwind UI, and focus more on guidance and quality control on the design side instead of building o
by deltron3030 6y ago
Adam, Steve, have you considered building a marketplace for Tailwind UI, and focus more on guidance and quality control on the design side instead of building out all the components yourself?
It could help with the creation of interactive components for all ecosystems, like those that are tightly coupled to a specific ecosystem considering that it's not only frontend frameworks, but also backend frameworks that have their own LiveView version or way to do components now (e.g. Elixir Phoenix has Surface which is like writing backend React components, Rails has view components).
Supporting all those combination yourself seems daunting, and it would suck to see components for React or LiveWire/Alpine, but not other ecosystems that aren't covered by the skillset of your team.
- countername 6y ago+1 for the marketplace idea
- mariusmarais 6y agoI am personally very happy a company has come along to build something useful while charging a (fair?) price for it. So happy that we just bought a team license for Tailwind UI. Too many marketplaces exist where there is no value-add instead of sitting in the middle.
- deltron3030 6y agoSure, but imagine you've paid for it and they come out with more interactive components, but your language ecosystem then isn't part of that because they don't have the capacity to cover every environment. A curated marketplace would be a smart choice imo.
- lol768 6y ago>instead of building out all the components yourself One of the reasons I bought Tailwind UI is _because_ Adam & Steve knew what they were doing, had good attention to detail and because I'd already purchased Refactoring UI. I'd worry that with a marketplace the quality would drop, no matter how much guidance you give.
- deltron3030 6y agoThey could curate the submissions. But most of the stuff wouldn't be about visual design and the style of the components, but template and component level frontend stuff that's handled differently by each framework.
- dbbk 6y agoPersonally I prefer this approach. It's like with the Streamline icon set. I know I'm going to get icons with high quality and a consistent visual language throughout. That's what you're really paying for.
- adamwathan 6y agoWe've tossed it around, but ultimately we believe that our customers buy Tailwind UI because Steve and I designed/built it, and we've built a lot of trust in our community over the last 4-5 years. I wouldn't want to be a full-time QA person either. Hoping instead that we can find the right small team size that lets us do more of this in a first-party way, and selectively support the tools we find people ask for the most. Could definitely see a world where we work with experts in different technologies to port our stuff over and maintain it under some sort of retainer agreement though, just don't see us ever giving up any of the actual UI design or initial implementation work.
- deltron3030 6y agoThanks for replying, love your stuff. I bought into it because as a designer I got interested in SaaS, and my impression was/is that you have a perspective on design edgecases that most traditional or semantic html devs lack because they're more focused on content sites and blogs. Keep up the work, but don't forget smaller frameworks. Your last suggestion with the retainer agreement sounds good!