Frontend Toolkit

@damian_frizzi Congrats on the launch, here're my $0.02 New widgets: - JS prettifier - JS minimizer - App Icon generation for iOS and Android - Splash screen generation for iOS and Android - Base64 decode/encode - Color tones and swatches - JSON <-> YAML <-> XML - Gist creation for JS/TS/JSON - Linter - etc Here's how you make it big: - create GitHub repo - create template for a widget (document it really well) - publish call for contributions - let ISVs and SaaS generate their own widgets on top of your template - Collect number of usage per each widget (you play same role NPM does for its packages) - Let people build dashboards (layouts) and share them. FE engineer, iOS engineer, TS engineer, etc. - Add mobile clients - Rinse & Repeat You are basically creating a new version of jsfiddle + working environment (cloud9) + toolkit + dev networking + trello. Side note: I'd totally use preset dashboards for different engineers that we onboard for different projects. In a year you'll have 1M visitors easy.

Hey @eugenehp, thanks a lot for your awesome feedback! I added all your widget suggestions to my list (except JS prettifier, this is already on the website). Thank you for your helpful words regarding how to make it big. I've yet to decide if I want to make it open source or not. I'd really appreciate contributions from other devs but I'm afraid it would take a lot of maintenance time. But I absolutely see the advantage in letting people integrate their own ideas/presets. I was thinking about a customizable widget, directly accessible from the UI as a compromise.

@damian_frizzi Don't open source the whole thing, just the widget part, enough for folks to contribute their own updates. look at what vercel.com is doing with a similar approach. re: maintenance – write clean code, you'll learn a thing or two :) get maintainers, we (devs) are happy to contribute. also here's a fresh example, servers -> VPS -> serverless Just declare a single function with in and out, and eval JS file. Build a list of vetted widgets first, and have a pipeline for checking the rest. People will vote on GitHub issues and will let you know what's needed next. You own the website and real-estate of each widget, it's your IP and you control it.

@eugenehp this sounds like a very reasonable compromise. I'll think about how to make the widget part open source. Thanks again for your feedback!

@damian_frizzi i think that is an awesome idea. good luck, damian.

@justaashir Thank you for the feedback! It isn't open source right now. I will consider it, but need to do some cleanup first. ;) These are great suggestions! I added them on my list (along with a IBAN generator). There is also a button on the website to let me know directly what things you would like to see.

@justaashir I created a GitHub repository to track feature requests and added your idea there: https://github.com/damianfrizzi/...

Thank you for your feedback, @lorenzosigno_! I was considering your idea but de-prioritized it because of the sheer amount of CSS-in-JS solutions. Do you have a specific CSS-in-JS solution in mind?

@damian_frizzi I've used the style prop, emotion, styled components—I'm sure there are many others out there. The syntax, though, is always largely the same. You could start from here 👉 https://cssinjs.org/

@damian_frizzi @lorenzosigno_ I don't agree with this at all. There are so many ways to write JSS and it changes so often. Don't bother. I actually quite like the selection of tools you have. Keep it lean and mean.

@damian_frizzi @florian_martens I'm currently using the CSS-in-JS extension for VS (https://marketplace.visualstudio...) and I find it works pretty well 😅.

@aksakal thanks :)

@florian_martens I'm currently using Compressor.js (browser based canvas solution) which I assume comes nowhere near to what TinyPNG can achieve. I think it's fine for jpg/webp but I will try to improve the situation for png!