There are two aspects to how the stack may be structured. One is about how user interface elements are organized and the other is about where in the hierarchy of a stack you should place your code. The first addresses how to make the app understandable, logical, and easy to use. The second addresses how to minimize development time, subsequent maintenance effort, and how to maximize the resulting performance of the app.
When you imagine how a typical mobile application appears, it would be somewhat along these lines:
Sometimes, applications are entirely code-driven where every screen you see is created using code at the time that it's needed. Perhaps, it would already lay out the elements that are saved as resources and then the code would load these resources. In either case, the whole application could take place on the equivalent of one LiveCode card.
Another approach would be to lay out every possible screen combination as different...