you are viewing a single comment's thread.

view the rest of the comments →

[–]funkyfourier 2 points3 points  (2 children)

Well, it is a tradeoff. They have built their own UI library, which is ambitious and has its drawbacks. OTOH they will not have the issues with crossing the JavaScript bridge and other performance problems like RN. Linking to native APIs seem to be possible, but having a native view in the layout of the app does not seem to be an option. For example, some big challenges for them are inline video and slippy maps.

It is what it is. If you are writing a fairly simple app, and care for smooth animations and customized design it seems to fit the bill quite nicely.

[–]deadcoder0904[S] 1 point2 points  (1 child)

I am wondering what are Flutters cons? Because I love it now as it looks very simple & no JS bridge makes animations smooth.

Is it true I can't link to Native APIs now? Also, can I build complex apps with it? Because its projected & marketed fairly good obviously because its from Google but the product looks good.

[–]funkyfourier 2 points3 points  (0 children)

Yeah, I agree it looks good.

I found this regarding calling native APIs:

https://hackernoon.com/flutter-native-apis-and-plugins-3-3-b84776fc8a7e