Best Way to Structure Two Similar but Separate Phoenix Apps?

ream88
Thu, 20 Mar 2025 09:19:49 +0000
Questions / Help

I have developed a management app and now want to create a separate front-end app that interacts with the same data. This new app needs to remain lightweight, avoiding unnecessary dependencies and assets. I’m currently facing challenges with:

Separation: Keeping the apps independent while avoiding duplicated configurations, such as Tailwind and custom Plugs.

Code Reuse: Preventing dependencies and logic from becoming out of sync or duplicated.

Maintainability: Striking the right balance between separation and shared code.

I’ve tried umbrella apps, a single app with multiple endpoints, and fully separated apps. However, each approach has trade-offs—either too much coupling or too much duplication. I still struggle with keeping shared logic in sync while maintaining separation.

Would love to hear how others have tackled this. And yes, I know I asked a similar question before… Sharing code across apps Pretty sure ChatGPT just reused my own question. Thanks!

6 posts - 5 participants