![]() It also has the benefit that it needs to be tested once, as it supports modern testing frameworks.Īfter some preliminary investigation work and a long discussion of potential pros and cons with the client, our team decided to take on the challenge of trying to implement the desired survey feature using Flutter. This means that code has to be written only once to be used across multiple platforms, including the Web. Its speed and performance is similar, but it has a true cross-platform nature. In a Grid Dynamics blog post about Flutter, it has some very cool advantages over taking a more traditional native approach. ![]() It is possible to create a new module, and implant it into existing applications without much effort. ![]() With Flutter, only a single development team is required, and there is no need to throw away the legacy Android and iOS code. Traditionally, we would require assigning two developers (one for iOS and one for Android), as well as a QA engineer to cover both platforms with tests. It will also need to contain a screen that rewards the user for taking the survey. All it essentially requires is to add a new item in the main menu that leads the user to a set of new screens containing blocks of questions, and a large “Submit” button. ![]() The task to add a survey appears to be pretty straightforward. The new features would need to be tested carefully, and the updated version would need to be delivered to users in a very short timeframe. They initially started out using Objective-C and Java, but the majority of the more recent code was written with Swift and Kotlin. The iOS and Android apps had massive code bases with mixed technology stacks. This would require adding a whole new user flow into both the iOS and Android versions of the application. One of our clients came to us with a request we see often - to add a customer satisfaction survey into an app that had a long history. Flutter as an incremental approach - a case study In the remainder of this whitepaper, we will present a technical case study where we did just that. You can use all of your existing native-language code, while writing your new features in Flutter. Well, Flutter should still be your choice. You have two apps written in their native languages, which don't need replacements or major upgrades yet - you just want to add a feature. From that point forward, all development and maintenance has the advantages of a true cross-platform. The look and feel of both apps will also match. In the next refresh, your development time will be near zero. You may elect to replace your existing app immediately, or wait until the next refresh. If your newly developed app uses Flutter, you will have more options for the future. Should you consider Flutter, or should you use a Native app language, like Swift or Kotlin? Even if you only built a single app, Flutter is still an excellent choice. In the second case, you have an app for both Android and iOS and you need to redesign one of the apps. It is best to plan on 50% resource savings for the first development cycle. It is easy to learn but nonetheless could somewhat cut into your 55% resource savings for your first Flutter endeavor. The only downside is the requirement to learn a new programming language, Dart. Runtime performance and code size are on par with native language apps. This amounts to a 55% savings in resources over using the traditional native language approach. ![]() Additionally, development resources are generally about 10% more efficient than using a native language development platform. This can free up your second resource team for other projects. Using this cross-platform development tool, you can cut your development resources in half, since you only need one development and QA team, instead of two. This is an ideal time to incorporate Flutter. You have both an Android and iOS app and it is time for a major update or a complete redesign.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |