Structure of Design

[swift lantern]

I have a question, namely I want to build a customer and admin panel is written for each now a separate backend or for everything simply in one backend? How do you do that because admins are allowed to see more than customers. Also related to routes etc.

[plucky sand]

@swift lantern - it depends on how complicated your apps will become. And, I'd suggest it is more about code management than about authorization, because if your apps are (going to become) complicated, and you know the clients will also become more sophisticated, then it is better to have the apps separate so making changes and enhancements is easier. If you are just starting off and don't have any idea about the future complications or complexity (which is usually the case), then start with a single app. Keep in mind which portions of your app need to be separate between the user types and make sure they are separate. In other words, don't put in logic that says, If admin, do this, or if user, do that. This separation will allow you to relatively easily break apart your single app into two smaller ones later, so they in tern can also scale to larger apps. In our system, for instance, although we are just starting, I know we want certain parts to even be "customer customizable", so we have three genearl app layers. Admin/Team/Global, Admin will not be customizable, Team will have some leeway for cusomtization and the global apps will be almost 100% customer created and/or customizable..:)

[swift lantern]

Yeah but why all users locate all dtos in one folder its messy to me...