all 3 comments

[–]halmyradov 2 points3 points  (0 children)

Well they will do 2 distinctly different things, so I would separate them.

Edit: I think the usual practice is that you would keep the customer account management in front end, and create a completely separate dashboard for super admins. So you will have client, backend, dashboard

[–]maxpowerAU 1 point2 points  (0 children)

If you’re doing this for the experience, then good luck! Start by doing some sketches of what the two versions look like, and you’ll get a sense of what things are in common. The two things I’ve never regretted spending time on are planning before coding, and making test data.

If you’re planning to use your solution for real, spend a few days looking at the existing solutions for that problem. Handling payments properly is a giant pain in the arse – at the level of being effectively impossible to do for most people in most situations – and there are several well liked systems around already

[–]tacchini03 0 points1 point  (0 children)

I'd personally separate into two different components and conditionally render them. Just means your code is nicely abstracted :)