Flutter is the primary UI SDK for Google’s Fuschia operating system, which many consider a future competitor to Android (and it seems to have created messy internal politics at Google as well). Additionally, Facebook has no developer-focused business (no cloud services, no frontend products, etc). Facebook offers no guarantee of support or maintenance on any of it and if developers have issues they need to file an issue just like anyone else (currently ~2k open issues). Flutter is built by Google, React Native by Facebook, and Ionic by…Ionic.įacebook notoriously built React and React Native for itself, and they are the only “customer” they design for, and all other users have to fit into what works for Facebook. That brings us to Flutter, React Native, and Ionic/Capacitor as the cross-platform leaders. Teams going pure native know what they are getting into and are willing to spend the time and money to go that route. The dynamics of building pure native are well understood and Apple and Google have a long history of being almost completely hands off with users of their SDKs (Apple doesn’t even have an official public bug tracker). In the mobile ecosystem, the most popular technologies for building apps are “pure native,” Flutter, React Native, and Ionic (including Capacitor and Cordova). I find that developers often aren’t thinking about what happens when the rubber meets the road and the project is running into problems with the chosen technology stack and the team needs help. It’s easy to just follow hype or perceived popularity when it comes to making those decisions. These days developers are making a lot of choices when it comes to the technologies their company will use. This got me thinking about a question I see too many developers and teams forgetting to ask until it’s too late: who is going to support the mobile platform and framework you choose to build your next app? The author was running into bugs with the Flutter core and with community extensions, and was stuck because their Flutter issue received no fix nor was it prioritized by the team, and many of the community extensions the developer explored were not adequately maintained. Over the weekend there was a post circulating online about challenges finding support for a mobile app built with Flutter.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |