-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Document best practice for developing add-to-app module integrated and standalone #7774
Copy link
Copy link
Closed
Labels
closed (obsolete)Too old or too vagueToo old or too vaguedev.best-practicesRelates to exemplars of process, code, or writingRelates to exemplars of process, code, or writingdev.existing-appsRelates to integrating Flutter into existing appsRelates to integrating Flutter into existing appsfix.code-sampleNeeds new or updated code sampleNeeds new or updated code samplefrom.flutter-sdkReported via move from flutter/flutterReported via move from flutter/flutterp3-lowValid but not urgent concern. Resolve when possible. Encourage upvote to surface.Valid but not urgent concern. Resolve when possible. Encourage upvote to surface.t.add-to-appRelates to adding Flutter components to native appRelates to adding Flutter components to native appt.dev-toolsRelates to DevTools and CLIRelates to DevTools and CLI
Description
Metadata
Metadata
Assignees
Labels
closed (obsolete)Too old or too vagueToo old or too vaguedev.best-practicesRelates to exemplars of process, code, or writingRelates to exemplars of process, code, or writingdev.existing-appsRelates to integrating Flutter into existing appsRelates to integrating Flutter into existing appsfix.code-sampleNeeds new or updated code sampleNeeds new or updated code samplefrom.flutter-sdkReported via move from flutter/flutterReported via move from flutter/flutterp3-lowValid but not urgent concern. Resolve when possible. Encourage upvote to surface.Valid but not urgent concern. Resolve when possible. Encourage upvote to surface.t.add-to-appRelates to adding Flutter components to native appRelates to adding Flutter components to native appt.dev-toolsRelates to DevTools and CLIRelates to DevTools and CLI
@blasten called this out last year. This was also extensively worked on by our China customers https://www.infoq.cn/article/iYGyKQowuiUN_Gi2hHDo.
For lightweight "detached" development, it makes sense for Flutter module developers to be able to bootstrap their module and launch/test their module both in a standalone fashion and also in normal 'production' mode integrated into their bigger host app.
Document the best practices for this approach.
Relates to flutter/flutter#32989 and http://flutter.dev/go/everything-builds-from-a-module as well.
I'm of the opinion that the standalone run shell should be another (albeit simpler) add-to-app host app that wraps the same Flutter module and that supplies it with upstream dependencies, data etc.