Post

Tomorrow, I'll conclude #FlutterInProduction when I'm joined by 5 guests to discuss their journeys delivering mobile experiences for some of the world's biggest brands with @flutter.dev. Use the hashtag #AskFlutter to share questions you'd like me to ask! www.youtube.com/watch?v=saeh...

1) Have they found good ways of automated testing with native features (BLE, camera, payments, deep links) eg using maestro, browserstack etc? Or just go with manual QA? #AskFlutter

2) How do they maintain contracts between mobile app and backend? Do they use API versioning, contract generation, grpc, protobuf? #AskFlutter

3) Are their apps offline-first or at least offline-capable? What strategies do they use to synchronize the data, maintain schema migrations, queue actions and expose failures to the users? #AskFlutter

5) When working in multiple regions how do they handle various legal requirements that can differ across jurisdictions? At which point the app knows in what country it's operating and exposes features. Is it account-based, or maybe known at startup of the app? #AskFlutter

6) How do they do logging and remote troubleshooting? Do they collect logs from every user or just selectively? Do they have ways to enable tracing or debug-level logging remotely? If yes, what kind of tools do they use? #AskFlutter

7) Do they use server-driven dynamic layouts? If yes, what strategy do they use - e.g. some custom representation of layout driven by CMS, or maybe remote flutter widgets, or maybe plain HTML in a webview? #AskFlutter