From a governance perspective, we ran into difficulty rapidly spinning up new dev capacity relative to RN (where you can have a web developer productive within a few days, as long as they've got a mobile dev running their pod to oversee integration and build). My former firm put a lot of effort into Flutter as a preferred alternative to RN or native app dev - including standing up a lot of onshore/nearshore/offshore experience - but we never were able to to make it a viable alternative on anything other than small or trivial apps, due generally to performance problems, weird iOS corner cases, hard-to-debug crashes arising from deep within the framework, and sharp edges on their emulated components. This has enabled libraries like Reanimated 2 ( ) and Gesture Handler 2, which take full advantage of this and get React Native apps tantalizingly close to "truly native"-feeling. React Native's story for native inter-op has recently become miles better with JSI, which allows nativeJS FFI at much better performance than the previous approach. the "fling" gestures from UIPageViewController, the native modal animations, overscroll, etc.), and these are extremely difficult to get right. if you can get Skia to run on it, it can probably run Flutter).īut particularly on iOS, the native components have some incredibly subtle behavior (eg. In a way, this is an amazing approach: it completely sidesteps a lot of the platform-specific woes that plague React Native, and makes it much easier to support completely new platforms (ie. it renders everything using Skia), and doesn't offer any escape hatches for native components. Flutter suffers on iOS because it completely takes over the render surface (ie.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |