Reminds me of https://github.com/GoogleChromeLabs/ProjectVisBug
Show HN: I made CSS Pro, a re-imagined Devtools for web design
41–50 of 299 posts
Re: Show HN: I made CSS Pro, a re-imagined Devtools for web design
#42This website makes my fans go brrrr.
Re: Show HN: I made CSS Pro, a re-imagined Devtools for web design
#43The killer feature here would be hooking this up to Netlify/Vercel etc. and having a 2-way-write. Every time you update something in the CSSPro editor, your codebase is actually updated and the site is rebuilt in the background. This would let you essentially design in the browser and avoid the tedious copy/paste, rebuild, reload cycle.
How would that work with VCS?
After you make changes, if you like them, you can commit them.
Re: Show HN: I made CSS Pro, a re-imagined Devtools for web design
#44I think if I did webdev full time, the price would be easily justified.
OP: Consider hobbyists and generalist who aren’t full time. There might be a market segment for short term access for hobbyists or generalists.
I would be easily willing to pay $2/day to have this while redoing my personal website, but $30 seems steep for a short term use. Doing a daily price could work to bring in users by serving as a low-cost demo.
Re: Show HN: I made CSS Pro, a re-imagined Devtools for web design
#45I think the comments criticising the pricing are wrong, you can't compare one generalist tool to another highly specialised tool. But on top of that comparing to Figma, Framer or other VC backed products is a mistake, these products are priced to capture market share and grow rabidly. They are clearly underpriced. I may be wrong but CSS Pro looks like a small bootstrapped product, pricing for market growth doesn't ne…
On the subscription side, I think it's an issue as it moves the control away from the consumer when doing those upgrades. With the older, one-time purchase upgrade model, which has since fallen out of favour; I could evaluate once a year whether the updated product was worth the additional cost. With a subscription model, there's a chance I could end up funding the development of features that I neither want nor need…
And CSS will almost always be backwards-compatible. If you want to keep using older CSS, that should be allowed.
Re: Show HN: I made CSS Pro, a re-imagined Devtools for web design
#46I was reading the uprising against the pricing, was expecting who knows what, these people are ridiculous to say the least, pitiful at average, you get paid who knows how much, but then 30dollars to do your job quicker are a nono, from a indie developer? Remembers me of the uprising of millions-dollars companies against docker, some people have no shame
Re: Show HN: I made CSS Pro, a re-imagined Devtools for web design
#47I think if I did webdev full time, the price would be easily justified. OP: Consider hobbyists and generalist who aren’t full time. There might be a market segment for short term access for hobbyists or generalists. I would be easily willing to pay $2/day to have this while redoing my personal website, but $30 seems steep for a short term use. Doing a daily price could work to bring in users by serving as a low-cost…
As someone with very little front end experience, mostly chugging through with chatgpt since blogspam is impossible to parse through, $30 bucks to make my site look good over the course of a month is a bargain if I just pay for the months I need.
Re: Show HN: I made CSS Pro, a re-imagined Devtools for web design
#48Yet another subscription, for a novelty item to boot. Hell, no!
Re: Show HN: I made CSS Pro, a re-imagined Devtools for web design
#49Is it just me or does the site perform horribly?
PS: have h/w acceleration disabled.
Re: Show HN: I made CSS Pro, a re-imagined Devtools for web design
#50The killer feature here would be hooking this up to Netlify/Vercel etc. and having a 2-way-write. Every time you update something in the CSSPro editor, your codebase is actually updated and the site is rebuilt in the background. This would let you essentially design in the browser and avoid the tedious copy/paste, rebuild, reload cycle.
How would that work with VCS?
The changes exist in the file system of wherever the server runs. Presumably in the repo if code. Run your git commands to see what is changed and select what to commit.