PLM solutions are mostly web-based nowadays. To access the main User Interface of these PLM solutions you need a web-browser. Web browers are eating 3 languages: HTML CSS...
Filter by Category
Filter by Author
PLM solutions are mostly web-based nowadays. To access the main User Interface of these PLM solutions you need a web-browser. Web browers are eating 3 languages:
User Interfaces and User Experiences (UI/UX) are key for a correct long terme usage of a PLM Platform. UI/UX is a whole area of expertise. And on a specific job basis, you can also have very specific UI/UX requirements. That’s why I believe the front-end framework should be a specific lego block to take into account when building a PLM stack. Let the configuration management specialist build a great API and then build or buy job-specific UI/UX.
If I lost you here is a great video about front-end development and frameworks
Some of the large customer I visited these last few month are looking into building job-specific UIs. And from the development teams, I see mainly requests to develop UIs with Angular. Here are the main front-end frameworks used these days:
There are others frameworks, but these days, these 3 are really the ones for which you will have lots of support on the web and a wide range of libraries and modules to build pretty much anything.
Sadly, I think none of the existing PLM solution on the market uses these frameworks. Some editor will tell you that these frameworks are moving too fast compared to the PLM industry where you need to design a solution for the next 10-15 years.
Again if you want a good and agile PLM stack. Split the concerns. Front-end development is a real job and expertise. make sure this is well split with other concerns like configuration management, database,…
What is the language your PLM solution has been built with? It is something that barely comes up in PLM evaluation. Does it matter? I think so, but in order to know why it matters...
Don’t miss any post by subscribing