cvkmohan
When we create a new application - what is the meaning behind naming the naming convention? Specifically, I could not understand the rationale behind naming the namespace to be MyApp and MyAppWeb. Can we not call them Domain and Web? My observation has been - by using the application name in namespace - and using it at many places - it is getting difficult to develop and reuse application starter templates. Even when we clone an application starter - we need to run a rename script to make the application our own.
I agree that all serious application developers here would like to develop application from scratch. But, my question is - by making it easier for using templates - is there a possibility of entry barrier getting lower for new entrants?
May be tI asked question in a bit round about way. The simple way to ask probably is - Should the Application Name be prepended for directories, all namespaces etc. - Or will they be better without it.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
tomkonidas
I guess a benefit is that if you ever need to move them into an umbrella or separate the app, your not left with a project called
Web.MyAppWebon its own or in a with a bunch of mixed apps is clear what it does.phcurado
For module names there is a guideline: Library Guidelines — Elixir v1.12.3. This is for library but I think the same apply to other cases.
This way you avoid name conflicts and have a clear difference when using the code from a module of your app or a module from a library.
hauleth
There can be one, and only one, module with the given name within each instance of the VM. Sometimes it is feasible to run more than one Phoenix application within the same VM instance. In such case there would be module name conflicts.