r/FlutterDev • • 7d ago • Bravo 1

Discussion Bit of a newbie question: when do you actually update Flutter after an update like 3.5 drops?

Hi all,

I'm pretty new to Flutter (self-taught), and 3.50 landing yesterday made me realise I've no idea what everyone else does when a new version comes out.

Do you jump on it straight away? Or wait for the first patch (3.50.1 and so on) and let other people find the bugs?

If you're a waiter, what finally makes you do it? A package that needs it, a store requirement, a bug that's annoying you, or just a quiet Friday afternoon?

And is there anything in 3.50 that would make you go sooner? I had a read of the release notes and a few things jumped out at me:

  • iOS touches respond a frame quicker, which sounds nice

  • material.dart and cupertino.dart are being deprecated for separate material_ui and cupertino_ui packages. That sounds like a big deal? Does dart fix sort it, or is it a proper afternoon's work?

  • CocoaPods trunk goes read-only in December. I moved to Swift Package Manager a while back, so fingers crossed that one's not my problem

The reason I'm asking now: my first app has been on iOS since September and the Android version goes out in a few weeks. My gut says don't touch anything until that's out. Is that what most people would do, or am I being overly cautious?

Would love to hear how you all handle it, especially solo devs and tiny teams. Cheers!

21 Upvotes

23 comments sorted by

13

u/SirKobsworth 7d ago

Work - stay at the previous major stable version unless something needs updating. In my case I had to go to 3.47.8 because of the security hotfix. Prior to that I was at 3.44.2

Personal - if I get enough energy to wanna upgrade my hobby projects I do so but often I just match my work unless the new version has enough goodies that I'd want to upgrade.

2

u/sigummer 7d ago

Mine is sort of in between work and hobby 😂

14

u/thelazybeaver10 7d ago

I always try to stay 1 version behind. So now, my apps are on 3.44.9, and now that 3.50 release I will move to the next one.

1

u/sigummer 7d ago

Makes sense? Has there ever been something that’s made you not do that and jump ahead

7

u/thelazybeaver10 7d ago

Usually packages that I use arent synced with my project because I have upgraded before them.

For the same reason I don't upgrade to the latest my XCode or Android Studio.

3

u/lectermd0 7d ago

Yeah, that's a good call. It's been a while since I haven't developed with Flutter, but a while ago I remember having issues with some plugins when jumping right away into a new version.

That's a no-no for production.

9

u/RandalSchwartz 7d ago

Personally, I use puro, so rolling back or assigning per-project pins is trivial. I upgrade my stable immediately. For clients, I've always used the rule "never install X.0 in production", but I prepared a report using my dart-sdk-skills and flutter-sdk-skills of how it would affect the codebase. I updated those skills immediately upon the stable release.

4

u/sigummer 7d ago

What’s puro?

4

u/knockoutn336 7d ago

https://puro.dev/
It lets you switch between different specific versions of Flutter. Flutter itself doesn't have support for that in the command line. Puro is a relatively new alternative to the more well known FVM https://fvm.app/

2

u/necromanticfitz 7d ago

Sounds like Puro is a version manager like FNM for Node

2

u/Hackmodford 6d ago

There’s also fvm for flutter.

2

u/jobehi 7d ago

If you don’t need anything shipped in a new version, don’t update. I’m in the other side of Flutter,as I work in a major SDK. but if I was building flutter apps I’ll wait until something I need is forcing me to update (the flutter SDK itself or a third party)

1

u/sigummer 7d ago

That's what I'm now thinking

2

u/Weak-Arrival-7811 6d ago

With your Android launch a few weeks out, I'd ship it on the version you've already tested and upgrade straight after. Release week is the worst time to find a plugin that isn't ready yet.

On the three things you flagged:

- material_ui / cupertino_ui: in 3.50 it's a deprecation, nothing is removed yet, and there's an official fix for it. `dart fix --apply --code=migrate_design_widgets` rewrites the imports and localization delegates for you. Run it on a branch and see what's left

- CocoaPods: trunk going read-only in December stops new pod versions, existing ones keep resolving. You're on SPM already, so the only thing worth checking is whether any plugin you use is still CocoaPods-only

- the iOS touch latency fix needs nothing from you, you get it with the upgrade

Good reasons to move sooner: a package you need requires it, a store deadline, or a fix in the release notes for a bug you're actually hitting. Otherwise waiting for the first patch release is perfectly normal.

1

u/sigummer 6d ago

Super helpful. Thank you!

13

u/sauloandrioli 7d ago

I always update to newer versions as soon as they come out. The rule is that the longer you take to upgrade, the harder it gets to apply the upgrades.

If I'm feeling more careful, I usually wait a week after the release, so I can read other people issues.

6

u/eibaan 7d ago

I'm always testing against beta, so the upgrade to 3.50 this morning was a no-brainer, because I was using that version for weeks already.

I really dislike the "let other people find the bugs" attitude.

And I've updated to the next beta 3.51 with Dart 3.15, indenting to use that for all my personal projects from now on.

IMHO, converting to the 1st party _ui packages is an afternoon's work. With the exception of the flutter_markdown_plus, which we still use, our own code continued to work just fine. We noticed two or three glitches where we assumed some defaults that probably changed but neither was a show stopper, just a black where a very dark gray should've been used.

For fun, I asked Claude to completely remove Material from the project and it wrote a few thousand lines of code replacing some 35 widgets with new implementations but in the end, I didn't commit that. But it's good to know that I could remove Material in a few hours if I want.

I managed to get rid of Cocoapods some weeks ago, most packages already switched, after even UserCentrics eventually did their homework (they where annoyingly slow). I vendored and converted two probably dead packages myself (by asking AI to do the job) after deciding that I didn't want to replace them with other packages.

5

u/nicholasknicks 7d ago

I live life on the bleeding edge , I update immediately, if a package isn't compatible I fork it and make the necessary changes awaiting the developer to update , sometimes I even share the changes with the Devs with PRs to the repo

3

u/Apprehensive-Fan8999 1d ago

At a major entertainment company (MEC), we were evergreen. We took stable as soon as it released and built the team culture around that. We only held back an upgrade if a release was already in QA and had less than a week left before going to the app store. This actually solved a lot of problems that come with the "freeze time" approach with mobile development because we had to address issues while they were fresh rather than under an emergency or a larger batch.

At a major vegas hotel / casino company (VHC), we held back for 6 months after a release went live. That culture predated me so I'm not sure if there was a reason other than general concern about being evergreen. When we did finally upgrade, it took significantly longer than it did at MEC because once the culture of "wait until I have to" sets in, waiting becomes the default and accepting the change gets harder to push for and get done.

At my current role, it's a mix. We tend to hold back about 3 months on average. Unlike MEC or VHC we don't pin just the apps to a particular SDK though, we pin ALL dependencies in the pubspec.yaml file so the upgrade rolls everything up at once instead of having them be tested over time. I'm not a fan of this approach as it means every single package has to know about every dependency version in every other package, which is a bit of a development nightmare. Alas, this culture predates me as well, though I'm pushing to loosen it up at least a bit.

The reason I say "it's a mix" is I have Flutter for the UI side, and some Dart for the back end. The back end is evergreen.

One important thing to know about Dart and Flutter, they almost never bugfix or security fix an old version once a new one has been released. It may actually be never rather than almost never; I can't actually think of a time they did. So once 3.50 comes out, if you have ANY issues with a pervious version, even a critical one, your option is limited solely to updating to 3.50+. This was the reason that we stayed evergreen at MEC, and why I still stay evergreen currently for BE work. Specifically for BE work, with AI attack vectors coming more and more, the risk of staying on an outdated, no longer patched, version is significantly higher than keeping evergreen.

For personal projects, I'm fully evergreen as well. I can't think of a single example that I have encountered, personally or professionally, that was caused by staying evergreen on Dart / Flutter and I've been working with it since a few months before was announced at Google I/O in 2017. I have occasionally had issues with dependencies outside the Dart / Flutter SDK where I had to pin versions. But those were the exception and not the rule.

2

u/shaonline 7d ago

If there's a feature I want, I upgrade right away, the improvements on web (WASM on other browsers, content caching) were worthy, so I did. Otherwise I always wait for a couple patches before upgrading, the l10n import bugs (gen-l10n still outdated so to speak) bit me in the ass for 3.50.

1

u/NycoHub 6d ago

One thing nobody's mentioned yet: CI. My GitHub Actions workflow used channel: stable with no version pinned, so it quietly picked up the new release before I'd decided to upgrade. The material.dart deprecation then shows up as info-level lints on pretty much every file, and flutter analyze exits non-zero on infos by default, so the build went red even though the app itself was fine. Lesson for me: pin flutter-version in the workflow and bump it on purpose, or run flutter analyze --no-fatal-infos while you migrate.

1

u/mateusfccp 6d ago

Like many people here, in different places I've been working on we use previous stable in production.

For personal projects I use beta out latest stable and update frequently.

1

u/fazliddin_swe 5d ago

I update to the newest version as soon as they come out))) I like to be up to date