App embedded within another App

[kefl]

Hello Beth,

I really like the “composable” approach of building little bricks and being able to use them in other apps. What I do not understand is your need to replicate everything.
If I create a single “reporting incident” app (building block) that is created in collaboration with multiple operators and in alignment with my “incident report” SOP, why would I need to copy paste it in all other new projects?
Why is it against your best practice to centralize key functions into single apps/blocks that can be used later in other projects (without the need to copy paste)?
How could we scale a project if every instructions/apps must be tailored made for each workstation?
How could we implement Data governance, App governance and always apply the latest best practice in Data integrity with hundreds of Apps built by different persons?

Thanks for the tutorial of Daniel, it is the workaround I was thinking about but it is just a workaround. I would still recommend to post this as Product Suggestion.

As @Sebme recommended in the comment flow of Daniel’s tutorial

@sebme

I hope Tulip will eventually provide native support for running other apps “on top” of a main app. This would make development much more efficient and less convoluted.

And each app should have access to the other apps last state after a jump has occurred and have access to or reference a copy in the log.

The completions could still be logged individually per app in addition to that.

That would open a new world because you could offload common tasks to dedicated apps or “modules” that together then build an entire app.

The “workaround” suggested in the video currently breaks the single trail record idea.

I am sure that a lot of your customers would be interested by this feature.

Kind Regards,
Kevin