Tomorrow's Observable features a panel of tech leads from companies shipping big time Flutter apps. Anyone got a question they'd like to ask? Just post it with #AskFlutter!
Comments
Log in with your Bluesky account to leave a comment
What would THEY like to see from the flutter ecosystem in the next 2-4 years? What if any gaps have they identified and is there any interest in helping to find solutions for those issues? Feel free to just ask part of this if you want.
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?
2) How do they maintain contracts between mobile app and backend? Do they use API versioning, contract generation, grpc, protobuf?
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?
4) How quickly do they adapt the latest stable Flutter version? Have they migrated to Impeller?
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?
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?
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?
Comments
2) How do they maintain contracts between mobile app and backend? Do they use API versioning, contract generation, grpc, protobuf?
4) How quickly do they adapt the latest stable Flutter version? Have they migrated to Impeller?
2) What are the security standards they are following. #AskFlutter