Thanks for your thoughts!
The complexity stems from the fact that, depending on the architecture, files will be in different locations and that some files might exist for every application in ./apps directory.
It's not that it is impossible to handle. It's just adding complexity for little gain, IMHO. And, let me say this again: perhaps there is more to it, perhaps i miss something. Also new to lotus.
Currently my undertanding of the app architecture is: it is the same as container architecture with just one app.
So instead of putting your application files in (container):
You need to put them in (app)
I don't think that is complexity that can not be understood and dealt with by a developer. If you want an app-like architecture, then just put one app in your container. If you want to move from container to app: just create several lotus applications, one for each directory in ./apps and you are done.
I'm not against multiple architectures, if they offer a real benefit. But the main deal breaker for lotus adoption is that it offers a different architecture already from rails, mainly offering the promise of less clutter in models/controllers.
Given that Lotus is very young and the community is small i'd restrain from adding complexity to the code. Concentrate on the real problems (deployment comes up often in the chat, i can not use lotus because it's missing a built in i18n solution, assets and so on).
Again, i'd be interested from someone who is actually using the app architecture and why it was chosen over container.