Skip to content

Document best practice for developing add-to-app module integrated and standalone #7774

@xster

Description

@xster

@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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    dev.best-practicesRelates to exemplars of process, code, or writingdev.existing-appsRelates to integrating Flutter into existing appsfix.code-sampleNeeds new or updated code samplefrom.flutter-sdkReported via move from flutter/flutterp3-lowValid but not urgent concern. Resolve when possible. Encourage upvote to surface.t.add-to-appRelates to adding Flutter components to native appt.dev-toolsRelates to DevTools and CLI

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions