Summary
Navigation between two screens via code works, but there's a desire to instead run/initiate an entire App that lives on a remote screen — one containing a lot of logic that would be difficult to move — rather than just routing to it.
AI Response
Rather than relocating the app's code, the recommended approach is to package that reusable logic and its components as a Module, which can then be embedded and run within any other app or screen without duplicating or moving the underlying code. Modules can pass data to and from the parent app, so the embedded logic behaves like it's part of the screen while remaining centrally maintained. An existing app that already contains many queries can be converted into a module so that its logic is reused in place instead of rebuilt.
Sources
Turning app into a module (transfer components and queries to module)
A solved thread addressing exactly how to turn an existing app that has a lot of queries into a reusable module without manually rebuilding or moving all the code.
Official guide confirming that modules let you build logic and components once and embed/run them within other apps, reducing maintenance by centralizing updates.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a 
, 
, or 
. Or by marking this post as the "Solution"! Let us know if you have any feedback here. 