Random
Only logged in members can reply and interact with the post.
Join SimilarWorlds for FREE 禄

Has anyone here tried Google's Flutter?

Such a delight writing mobile apps with it 馃槍
This page is a permanent link to the reply below and its nested replies. See all post replies 禄
NorthwestM
I personally picked it and led a team to develop a major application, 4 years ago.

Great idea in principle, but would not do it today, as long as Apple is not party to the development effort, and they will never be.

Control over hardware functionality, especially VR, geosynch, gyrosynch, network and camera lags, making achieving true code portability impossible, as I learned the hard way.

I can longer use that code base today, and would recommend a mix of native/react to achieve a higher level of interoperability.
Elessar26-30, M
@Northwest That'll depend what you're trying to achieve, but from the perspective of my use case I haven't seen such limitations. But bear in mind, my apps mostly do QR-scanning, REST and local data processing/storage so I don't interact with hardware too much.

Working with XCode is painful as hell for me so I'll stay away from pure native as much as I can, and I've never tried React Native yet
NorthwestM
@Elessar If you want to do Android develop only, it's fine, but its write-once, run on both environment promise, is its Achilles heel. All Apple has to do, and they do it often, is change one or two things...
Elessar26-30, M
@Northwest I need to target both, were it for my I'd ship only for Android and suggest iOS users to get an actual phone 馃槣. So I'd rather at least not having two distinct codebases for the same app / features.
NorthwestM
@Elessar Having a single code base was my code, but at the end of the day, had to revert to two. If it's about QR-Scanning for restaurant/retail application, yes, it does work, but only for a single iOS iteration.