Change ANY website directly in the browser with prompts (incl your own during dev ofc!) Yes, that's GPT-5! Yes, ANY website! Yes, it's THAT fast 🤯 YES, it's available in ~6 days with Tailscan 3 launch!

September 2022. The start of Tailscan. The first revenue. And the start of the /open page, where financial metrics were visible for all to see 📈👀 Super nervous, because it's a vulnerable spot to put yourself in. The days after, lots of people voiced their support and this is what kept me going all this time. However.. nothing is forever. Today, I am removing the financial metrics again from the /open page. The only thing that I will continue to publish and write are the build-in-public blog articles. Also because this is a great way to reflect back for myself. The reason I'm deciding to close the open page is simple: I see that competitors are taking advantage of the financial metrics and website statistics. There is no benefit in it anymore for me. It is slowly only starting to hurt, and that's of course not good. It genuinely makes me sad, because I know a lot of people checked in periodically and derived their own strategy, tactics and lessons from it. A real-time class of how to build a startup, if you will. I might do some proper write-up about the entire ride of being an open startup, but for now, this is it. By the way, I'm also considering making a closed group of 5 to 10 vetted, promising founders that are building, nearly launching or have freshly launched and could use some guidance (all free, of course). LMK via dm if you're interested.

🚀✨ Launching TailwindCssColors.com Simple cheatsheet for Tailwind colors. Also lets you copy hex/hsl/rgb. Perfect bookmark if you keep searching "tailwind colors" to go to documentation and find the hex code you need ;) More functionality coming soon!

The current version of Tailscan is much more than just a class editor, by the way. There is an auto complete feature, WYSIWYG editor, html to tailwind convertor, guidelines / measuring tools, support for custom configs and much more. Couldn't fit everything in a screenshot tho

Over the last 18 months, I've built 18 versions of Tailscan 🤯 1️⃣ Left side is the very first live version of Tailscan. 2️⃣ Center is how Tailscan has evolved in 2023. 3️⃣ Right side is the current UI version (since Tailscan 2). What do you think? Did it change for the better?

It's been sooo long since I've started working on this but I can finally say: Tailscan 2.1 will have an integration with Chrome Devtools 👀 👇Check the demo below. LMK what you think. Anything I can improve?

Tailscan now has an affiliate program! Who's interested? Send me a DM! (or if closed, msg below first) 30% commission forever on the subscriptions ~$60 commission on the one-time license.

Tailscan is getting a proper element navigator that highlights all elements just like Chrome Devtools would 🙌

Tailscan 2 brought a new UI that lets you edit any website live without having to remember all Tailwind CSS class names (great for product managers and designers). Just added a whole bunch of options, like box shadows, interactivity, scrolling adjustments, etc!

🎂 Today is my birthday, turning 31! And I want to celebrate with you all! (@arvidkahl gave me this idea 😁) I've added 31 discounts for the Tailscan perpetual license, valid for the next 3 days and 1 hour. Discount is not $31, but $50 off 😂! tailscan.com/#pricing

Which one will run out first? The 15 available slots, or the ~1.5 days left? Place your bets below 👇😂

My product is currently broken in front of thousands of visitors and hundreds of customers, while there is nothing I can do about it. This is going to be a different Product Hunt post-launch report than I anticipated 😅 Here's the full, uncensored story. Monday afternoon, 3pm. 1 hour to go until launch (4pm local time). I receive an email from a customer that mentions Tailscan has not been working for him after the v2.0.0 update that was pushed out just minutes before. The bug: no element is shown when hovering over any website. I check myself and not seem to have any problem. Strange.. After a few minutes, I decide to sanity check the version that is distributed through the Chrome Webstore (Tailscan is a chrome extension). After installing, I immediately encounter the bug. Crap.. would this be a bug affecting ALL users?! My heart skips a beat and my stomach starts to feel heavy. Diving into the console errors, I conclude that the problem indeed affects all customers. How could this bug have happened?!?! <technical, skip ahead if not interested> Turns out, for SOME reason, Vue Pinia (store/state management package) has a function called $subscribe, and one of the parameters ('mutations') is null. I figure out that when setting the node env to production, all of a sudden this happens. With node env set to development, it all works perfectly normal. I check the package.json build scripts and find out that I only set node env to production when building/packaging the chrome extension with a script. </technical> So I've never had the chance to encounter this bug. Now what? The Product Hunt launch is in less than 20 minutes and the entire product is not working. I come up with a fix, package a v2.0.1 and submit it to the Google Chrome store in a matter of minutes. Normally, the review process takes anywhere between 5 minutes to 1 hour. Unlikely in time before the launch, but soon enough to not completely panic. And v2.0.0, with thousands of lines of code changed, got through the review in less than half an hour too. I was very hopeful that this v2.0.1 bugfix, with 4 lines of code commented out, would also be a breeze. Absolute disaster avoided.... I thought. As the first few hours go past.. I start to worry. Why isn't this review accepted and the bugfix published? The first one-time licenses ($199) are sold, and I realize I have to email these customers right away to tell them that Tailscan is encountering a problem right now, but everything should be resolved very soon. I decide to not send out my newsletter announcing Tailscan v2.0 yet. I'd rather hold off and wait for the bugfix to go live. Limiting traffic right now seems like a good call. After 8 hours, around midnight, I start to panic. Probably because of fatigue building this new release for the last weeks without any days off, lack of sleep and a continuous rush of adrenaline. I decide to ask a Chrome Webstore developer advocate in Twitter DMs. Is there a way to expedite this review? Or roll-back to a previous version so Tailscan is at least functional? Or get an ETA on the review time? The answer: Nothing can be done. I cannot rollback, reviews can't be fast-tracked under any circumstances, the only thing I can do is.. wait. The official support of chrome webstore takes another day to get back to me with the same answer: nothing can be done, just wait. Right now, we're 45 hours further. The review is still pending. I did not do any of the things I planned during launch day (scheduled tweets, scheduled posts on reddit, newsletter, nothing). I've sent out more than one hundred handwritten emails to customers at this point and handled lots of refunds. I also slept for a total of 4 hours thus far (apologies if my writing is bad, I blame it on the lack of sleep). I feel ashamed to all my customers, new and existing, because they are paying for something that does not work. I also feel upset for working hard for a launch that turned into an absolute nightmare. Sincerely hoping that the review goes through at any time now.. but realistically, I know it can take many more days, who knows even weeks. If you are a Tailscan user and you're reading this now, please know that I'm incredibly sorry and I am trying to figure out how to set this right. If anyone from Google is reading this and might be able to help: Please. Reach out to me here or on [email protected]. I will send my full source-code and proof of changes in this new version, if that is what it takes to have this review go through and resolve this situation. And I sincerely hope that in the future, there will be either a fast-track option for emergencies, a way to rollback to a previous version or really anything that can help prevent a situation like this. For now.. I'll continue waiting, try to keep my sanity and continue working on a solution.

Tailscan 2 is live and on Product Hunt today 🚀🔥! This update contains lots of new features and an improved UI, designed to give your workflow a serious boost🙌! Read on here 👉 producthunt.com/posts/tailsc… PS: there's a limited amount of launch discounts available but be fast!

Every single time I land on the @TailwindCSS repository on Github, I notice the # of issues open versus # of stars🤯 Tailwind CSS is almost 6 years old now and I really hope it'll stay the gold standard for many more years. Thank you @Adamwathan and @Tailwindcss team🙇