0

Any Flutter devs? I'm a new dev on this platform and going to release native a native app for iOS _and_ Android.

I'm kinda getting frustrated. It's a great concept (one codebase, multiple platforms, etc) but I didn't realize I have to watch out for changes in my java and/or, swift changes that might break my build. (ex. A dependency that's deprecated, requiring a newer java/jre only to break something else).

Should I scrap Flutter and learn something else?

Also, it's just a one-time build. Once I'm done, I'm planning to switch to PWA, maybe React or Svelte.

Comments
  • 1
    I wouldn't scrap it as it seems to have grown into a pretty nice cross platform solution with the exception of Flutter web which is useless, don't bother with that. Small learning curve for Dart coming from a web background is nice. React-Native is trash, so just stick with flutter if you want to do cross-platform. Haven't tried svelte.
  • 0
    Stick to it, it's by far the best way to write cross platform apps atm!

    If you are adding libraries to your project, make sure they are reasonably well maintained and accepted by checking the date of the last commit, issue/open PR and star count on GitHub. Obviously that is no catch 'em all trick but should filter out most packages that are likely to send you down the "help my native code is broken" rabbit hole.

    Aside from the occasional black sheep dev who adds breaking changes to native code in a patch version, I have had only one single case in a year of basically full-time flutter development where I had to fork and fiddle around in a native library to add support for Android <10.

    Yes, you might have to watch out for changes in the native code but in most cases, there is already a GitHub issue for it when you notice it and most likely people are already working on a fix, if it's just a deprecation notice.
  • 0
    The last app I completed with Flutter went to the Google Play Store with theoretical capability to run under Android 4.4; we never tested it but given that a wrapper app around an Angular project for example takes much more effort, has a need for writing native code and starts at Android 7 and has less performance because it's in essence a browser without URL bar and not a 60fps rendering engine drawing on the phone's screen, I know which of the options Flutter vs PWA / wrapper app I would chose any time of the day.
  • 0
    I'm fairly new to Flutter too. But I don't plan on meddling with swift where possible. I simply use Xcode to sort out the basics (adding the certificate stuff, versioning, including push notification settings, creating launcher images etc) then I use Visual Studio to do ALL the building, installing Cocoapods, testing locally etc. I haven't had to do anything major to Swift, but my apps are relatively straight forward.
    I'm sticking with Flutter - the support for it is only growing, and I'm impressed with the speed of the apps.
  • 0
    That's the bad side of Cross-Platform mobile development.. Flutter or any other framework..
  • 0
    Just a little context and update as to why the rant: I inherited the project and had to deal with adding App Tracking Transparency for iOS. After adding the Flutter package, that's where my problem started. Just today, I realized I had to convert the iOS part of Flutter from Objective C to Swift. How fun was that? Spent a few days digging Google/Stackoverflow/Apple Dev sites, getting XCode errors left and right. Good thing, rebuilding the Xcode from Objective C to Swift was kinda smooth. The iOS build was a success. The next step is to again add App Tracking Transparency.
  • 0
    @wackOverflow Wow, I thought React Native is a good choice, given how popular it is.
Add Comment