Live data from Hacker News

All you should know about Flutter development

github.com

21–30 of 101 posts

Re: All you should know about Flutter development

#21
post #17

Is there any Flutter-like alternative but using TypeScript? Dart feels too weird.

Why is Dart weird for you? I've seen people getting to know Dart from various backgrounds (be it from Java, JavaScript, C# or Python), and so far everybody got productive in a short amount of time.

Re: All you should know about Flutter development

#22
post #13

Some opinions about good choices here, over a year of app development: * Don't get confused by the myriads of state management solutions. Just use GetX, it's a sane solution that works as advertised. * There were a couple of storage plugins like hive that claimed to be better because they be native to the platform and not SQL. As with all platforms, that's bull. SQLite is available, so use that. * The routers are a c…

GetX is a very high-level API for Flutter, it works for simple things, but as you go on you will realize how restricting it is. It abstracts away details not meant to be abstracted away. It's just bad design, and it's anti-patterns will bite you. Just learn how to do things the proper way, because it's not that hard, and much more expressive and clean. If you go for Flutter job it's best to not mention GetX either.

It works perfectly for us - in a professional app nonetheless - and has not been restricting at all. No bad design or anti-pattern bit us, and it does not get cleaner or more expressive than Obx with a controller. This is unlikely to change, the process where our app got more and more complicated has already stopped.

> If you go for Flutter job it's best to not mention GetX either.

I wouldn't work for an employer that does not let me pick the right tool for the job, so there is no danger there.

Re: All you should know about Flutter development

#23

I think developers often want to find a “one true cross platform toolkit for all cases” and I don’t believe that will ever exist. It depends so much on both your app/market but also the skills and experience within your team. No 1 priority is move quickly. Flutter is brilliant, and probably the way to go, for some apps. A great example of a successful Flutter app is the Sonos app, relatively simple and responsive ui…

I personally prefer a set of libraries over an opinionated framework with integrated dev tools.

Re: All you should know about Flutter development

#27

I feel that Flutter raised very high interest but it has fallen behind its expectations. Not that trendy anymore.

What is the current go to solution for cross platform apps?

React Native + Expo.

Expo has been making unbelievably rapid progress with tooling, documentation, consistent, high quality API's and general improvements. Evan Bacon + team are really impressive to watch

Re: All you should know about Flutter development

#28
post #20

I think developers often want to find a “one true cross platform toolkit for all cases” and I don’t believe that will ever exist. It depends so much on both your app/market but also the skills and experience within your team. No 1 priority is move quickly. Flutter is brilliant, and probably the way to go, for some apps. A great example of a successful Flutter app is the Sonos app, relatively simple and responsive ui…

I've been wondering why webviews with native page transitions aren't a more commonly used thing. It improves the UX a lot by dealing with the abrupt navigation changes of regular web apps. There was a plugin for Cordova that did this ( https://github.com/Telerik-Verified-Plugins/NativePageTransi... ) but it's abandoned.

Same here, it’s something I wish Capacitor supported.

Last year I experimented with using NativeScript in a Capacior app to open native modals with a second webview. Since then Ionic have released “Capacitor Portals” which brings all the native apis available within the Capacitor webview to native apps, effectively allowing you to embed capacitor views in another app. I wander if there is the potential to combine the two to get the native view transitions.

Edit:

Just to elaborate a little further on my experiment. Effectively what you ended up with was the two webviews being able to communicate with each other as though you had used the window.open or frames JavaScript api in the browser.

Re: All you should know about Flutter development

#29
post #22

Earlier quoted context omitted.

GetX is a very high-level API for Flutter, it works for simple things, but as you go on you will realize how restricting it is. It abstracts away details not meant to be abstracted away. It's just bad design, and it's anti-patterns will bite you. Just learn how to do things the proper way, because it's not that hard, and much more expressive and clean. If you go for Flutter job it's best to not mention GetX either.

It works perfectly for us - in a professional app nonetheless - and has not been restricting at all. No bad design or anti-pattern bit us, and it does not get cleaner or more expressive than Obx with a controller. This is unlikely to change, the process where our app got more and more complicated has already stopped. > If you go for Flutter job it's best to not mention GetX either. I wouldn't work for an employer tha…

Not to get on your nerve, but GetX is basically a toy API, and the codebases that use it tend to evolve in the heap of spaghetti direction, but if your app is simple enough you can get away with it and save time, so who am I to knock it.

Re: All you should know about Flutter development

#30
post #23

I think developers often want to find a “one true cross platform toolkit for all cases” and I don’t believe that will ever exist. It depends so much on both your app/market but also the skills and experience within your team. No 1 priority is move quickly. Flutter is brilliant, and probably the way to go, for some apps. A great example of a successful Flutter app is the Sonos app, relatively simple and responsive ui…

I personally prefer a set of libraries over an opinionated framework with integrated dev tools.

There is obviously no correct answer here, very good arguments on both sides.

Personally I prefer an opinionated framework, I don’t have to research library’s and tooling. It all just works and I have a single set of docs for reference.

Post reply on HN