I thought I'd give flutter a test, a simple list app lags on the following:
1. Scrolling the "Lazy Loaded" list
2. Tapping on a list item to change an icon color

I followed their "lesson" in creating that app

Now tell me, why should I invest time on this?

Because all the hipsters and geeks are hyped about flutter

Have you ever worked on a professional mobile dev shop?

Legit not trying to sound condescending. But I have noticed that most people that completely disregard such solutions have never had to maintain or develop new features for large mobile codebases.

Regardless of that. A lot of apps do pretty much the same shi, let the user log into an existing service(more than likely through an API) and a bunch of their info gets fetched and displayed on a screen from which they can interact with.

Swift kinda sucks for json manipulation and interaction, objC was somewhat nicer, but fuck it, its 2019 and Apple says swift is the future.
Therr are 30thousand different ways to do it in Android, and you have to do it while dealing with state and screen management and the overwhelming API that the Android monstrosity has(I love Java tho) and you can't hide from dealing with xml, wether you like it or not. Oh and Animations in Android? Recyclerview patterns?
I am feeling dizzy

@AleCx04 point is. A unified experience, with an easy to grasp syntax for those familiar with either C++, Java, C# etc etc(a large pool is my point) in Dart makes sense.

A programmatic way to build interface that is easy to grasp and follow with the Flutter API, easy to resd docs, with one point of contact mind you(instead of dealing with Google and IOS docs) and nice animations and transitions backed in? Well, it really is no wonder why people would like this solution.

Other than that I dunno what to tell you unless you have worked on a large Android shop before.

@AleCx04 I'm with you on this, having to maintain two code bases is a huge pain but I never reached a road block in native, while for example react native dealing with hardware most of the time means I either need 3rd part library or write my own native code. Even background fetch needed it's own native code in react native or it stops when app goes to background.

Not to forget bad performance...

Not sure about flutter but I done haven't hopes up high.

IMO both are yet not mature, and I don't like the fact using system features require bridging code between native and rn/flutter

@gitpush agreed 100% my dude. I am willing to compromise tho on the basis of the Android API being overwhelming and Xcode being fucky(sometimes it's great. Sometimes its shit)

There is one project called codenameone in which you can build for both in Java. Their approach to interfaces is similar to swing dev but feels fluttery.

There is another as well from Crom(I believe that is the name) which even creater their own language for it called Gravity.

There are some interesting solutions out there.

@AleCx04 also Kotlin now supports cross platform tho still in preview

Let's hope one solution gets it right in the end