@anandpotukuchi You have a good idea!
One way I have imagined people learning Elixir, Phoenix, and the OTP is to have a version of Phoenix that allows devs to see:
All routes, modules, functions/actions, etc from the default mix phx.new as well as any that they create or modify thereafter - within the app eg phoenix app they are running.
A visual ‘nodal’ representation of code - similar to a visual sql editor - where a dev can see how modules are linked and even functions, and even layout architectures this way.
Exercises based on 1 (and perhaps 2) - eg how to transform data from module to another. The simplest approach would be for this to be multiple choice - with answers provided and results depending on successful choice, and the more complex, allowing devs to write code within the browser to see how it changes the codebase or app.
Perhaps they’re fanciful ideas, but I often feel it’s great to have the IEx on the command line, but this appears to feel to isolated to someone starting in Phoenix or with a mix app that’s focused on a web app, and I can see this approach working for accessing IEx via the browser too.
Some of the tools/packages exist to cobble the above ideas together, for example, there’s a debug bar somewhere and I’ve also seen reference in these forums to a package that allows a dev to see all controllers etc in an existing app.
I guess, if I had to sum up the idea, it would be a meta/learning version of phoenix/mix that allows exercises to be added to it, completed in a visual way, that teach basic functional and elixir concepts to, as you write, developing basic apps.