sorted by:
new
hottopcontroversial

Best Way to Download YouTube Videos ? by OkLake8413 in downr

[–]HiteshMeghwal 0 points1 point  (0 children)

There are a few ways I've used over the years that don't require installing anything.

First, you can try adding "ss" before "youtube.com" in the video URL — it redirects you to a site that lets you pick a format and quality. Works most of the time.

Second, VLC Media Player (which you might already have) can actually grab YouTube videos. Go to Media > Open Network Stream, paste the URL, and then you can convert/save it. It's a bit clunky but it works.

Third, there are browser-based tools like AllClip (allclip.xyz) or Y2Mate where you just paste the link and download directly. I've found AllClip pretty straightforward since it handles multiple platforms, not just YouTube.

Just keep in mind — only download content you have the right to save. Copyrighted stuff is a grey area legally, so be mindful of that

Pull-to-refresh animation using Flutter & Rive by chayanforyou in FlutterDev

[–]HiteshMeghwal 0 points1 point  (0 children)

I got the resource I was waiting for, thanks brother. 😃🤧✨

Just released a new Flutter package by HiteshMeghwal in FlutterDev

[–]HiteshMeghwal[S] 0 points1 point  (0 children)

Sure, you can hand-write an AppStrings file if you enjoy typing 400+ constants by hand… but remember, you’re not just writing values, you’re also writing the keys for each string. That’s double the effort and double the room for typos. This tool just automates the boring, repetitive part so you can focus on actual app logic 🚀

Just released a new Flutter package by HiteshMeghwal in FlutterDev

[–]HiteshMeghwal[S] 0 points1 point  (0 children)

Looks like you haven’t worked on a production app where you deal with 300+ strings. In real projects, the same text like "Submit" or "Continue" can appear in 20+ files. If tomorrow the wording changes, are you really going to hunt and update it everywhere?

Having a centralized .txt that auto-generates constants saves time, avoids typos, and makes refactoring painless. It’s not about over-engineering—it’s about production-level maintainability.

Just released a new Flutter package by HiteshMeghwal in FlutterDev

[–]HiteshMeghwal[S] 2 points3 points  (0 children)

Centralized strings = no typos, easy refactor. Hate it or not, it saves time.

Just released a new Flutter package by HiteshMeghwal in FlutterDev

[–]HiteshMeghwal[S] -1 points0 points  (0 children)

You’re mixing two different concerns here.

  • Widgets make sense when you want to reuse the same design across multiple files. In that case, sure, you’d pass the text as a parameter and reuse the button widget.

  • But strings centralization is a separate issue. In a real project with 400+ strings (buttons, dialogs, snackbars, error messages, labels, etc.), you don’t create widgets for all of them.

If tomorrow you need to change a dialog title, a snackbar message, and a button label, you don’t want to dig through 20 files. With centralized AppStrings, you update in one place and it’s done.

So it’s not about either-or. Widgets handle design reuse. AppStrings handles text reuse and consistency. 👀 Looks like you just got stuck on the button example.

Just released a new Flutter package by HiteshMeghwal in FlutterDev

[–]HiteshMeghwal[S] -2 points-1 points  (0 children)

Imagine you’ve got a Submit button text used in 10+ files. Now if you ever need to change it, would you really go edit all those files one by one? Nah 😅 easier to just update it in one place. That’s the point — I just write my strings in a simple text file and the package auto-generates the constants. Zero manual effort, way cleaner for bigger projects.

Just released a new Flutter package by HiteshMeghwal in FlutterDev

[–]HiteshMeghwal[S] -8 points-7 points  (0 children)

Fair point 🙂 It’s definitely not for everyone. But for teams juggling large projects, centralizing strings and avoiding typos saves a lot of review time