Building a large-scale Flutter mobile banking application with 25 Flutter Devs
Building a large-scale Flutter mobile banking application with 25 Flutter Devs and 200 other team members has taught us many valuable lessons on how to set up such a project. We would like to give you our perspective on the organization of the project and challenges such as code ownership, communication, and design system, which are vital to ensure high productivity while keeping the team happy.
Reimagining Flutter UI tests with Patrol
Flutter UI integration testing can be really cumbersome, especially in a mobile app that depends also on the native side features. Unfortunately, Flutter integration test fail when a native permission dialog appears or we'd like to interact with some native platform view. We experienced the same blocking issues while testing apps that we develop at LeanCode.
That's why we created Patrol - an open-source framework for testing Flutter apps - developed by LeanCode. With Patrol you can write your UI tests in Dart (like you would with integration_test), but you are enabled to test interactions with native side - tap on native views, browse WebViews and even go interact with some other app on the device. The main goal of Patrol is to make running Flutter UI tests a piece of cake for QA teams and devs.
We’ll share with you the problems with existing solutions that prompted us to start Patrol, what differentiates it from others, and how it helps you write tests. We’ll also take a look under its hood and share the blockers that we encountered (and are still encountering) developing it, and what features we’re planning in the future.
Head of Mobile @ LeanCode.
In mobile development for 7 years. Went through Xamarin, React Native, native mobile to Flutter. Now we are only focused on doing mobile in Flutter 💙. Managing Flutter at Scale in Credit Agricole project.
Co-founder of Flutter Warsaw – one of the largest Flutter meetups in Europe.
