Dear developers,
We are doing a rework of our current software platform at our company. At this point, it is a Vue.js front-end client with a Laravel back-end REST API. There are three kind of users (defined by permissions).
At this moment, the Vue.js front-end is very big and messy. There is a lot of complexity and clutter. For example: we are having the functionalities of all the three user types in one view file. Lot's of components and conditional based on the permissions of the user. The thing is: the functionalities have nothing to do with each other really. We have been brainstorming and we came up with the following idea:
We make three separate clients for each type of user: normal users, companies and admins. They all use the same back-end with different REST API endpoints (normal user endpoints, company endpoints and admin endpoints). There won't be 'double' maintenance, since all the three clients are very different from one another. Also, it can happen that one client may be updated frequently based on business needs, while the other one (such as the admin panel) may remain the same for a while.
Is this a good decision and approach? Or are there risks or issues that we are missing here?
Thanks all.
submitted by /u/Larstw98
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/3vK5iUR