The problem with TalentLMS is that it has some bugs. If you need to upload an image, then it will cause trouble. It is not actually stable. Another drawback of the LMS systems is that they are not scalable. It is not able to handle more users or requests at a time. I checked it and have completed load testing for this application, and I see they cannot handle 1000 users at the same time. So, if 1000 users become online at a time, that will cause trouble. I restarted their solution, and I checked the features. I have tried to do something there, and in the beginning, I see the problem in the uploading issue. It is unstructured somehow. If I would build this software, then I would use distributed technology and architecture. Then this architecture would manage any type of request when necessary. I could actually make the interface simple and user-friendly. There should be a flow. Actually, these two LMS systems don’t have the proper flow. Suppose you already study your education journey. Then, of course, you complete your standard one, two, three, four. Then you go to complete the secondary and intermediate. So, whenever you are a user, then you should have a sequence in the dashboard. Then you can actually do better things, or you can use your system properly and easily without any headache, without more training.
Global SHEQ Director at a wholesaler/distributor with 201-500 employees
Real User
Top 5
2022-12-15T13:39:00Z
Dec 15, 2022
I have been using this solution for over four years. During this time, reviews from learners have been positive and welcome. My interaction with creating courses and posting on the platform has been a simple task that requires little training. The quality of the course content is impeccable and supports all media types, from animation to audio, video, etc. The Learners can also evaluate courses to rate the effectiveness of the content and suggestions for improvement. Regarding improvement areas, when I upload animated training packs in Microsoft PowerPoint format, the animation and transitions are lost. This makes it static.
I have very strong feelings about TalentLMS, most of which have to do with the limitations of the programming. The built-in builder has some rather serious limitations. If you are porting in SCORM files to build resources in Captivate or Articulate, their program is only compatible with SCORM 1.2, which is a really old SCORM packaging format. The output is kind of clunky. The learner experience and UI is really basic, and this is an out-of-the-box, bare bones, 'nothing fancy' UI. You do have the ability, like most learning management systems, to do some customization, and you'll need to work with developers to do that. The reporting is severely limited in that it only shows rules. You can't set up dependencies. You can't set up cyclical course, so you can't have equivalencies. The back end is kind of clunky. It's not as user-friendly as I would like it to be.
TalentLMS is an award-winning Learning Management System (LMS) ideal for delivering engaging online training. Create courses in a few clicks in a platform suitable for sophisticated as well as inexperienced, aspiring trainers. TalentLMS combines support for multiple file types and multimedia (presentations, videos, iFrame, SCORM, etc.) with simplicity, and an always eager-to-help support team. Be the driver of your team's potential.
The problem with TalentLMS is that it has some bugs. If you need to upload an image, then it will cause trouble. It is not actually stable. Another drawback of the LMS systems is that they are not scalable. It is not able to handle more users or requests at a time. I checked it and have completed load testing for this application, and I see they cannot handle 1000 users at the same time. So, if 1000 users become online at a time, that will cause trouble. I restarted their solution, and I checked the features. I have tried to do something there, and in the beginning, I see the problem in the uploading issue. It is unstructured somehow. If I would build this software, then I would use distributed technology and architecture. Then this architecture would manage any type of request when necessary. I could actually make the interface simple and user-friendly. There should be a flow. Actually, these two LMS systems don’t have the proper flow. Suppose you already study your education journey. Then, of course, you complete your standard one, two, three, four. Then you go to complete the secondary and intermediate. So, whenever you are a user, then you should have a sequence in the dashboard. Then you can actually do better things, or you can use your system properly and easily without any headache, without more training.
I have been using this solution for over four years. During this time, reviews from learners have been positive and welcome. My interaction with creating courses and posting on the platform has been a simple task that requires little training. The quality of the course content is impeccable and supports all media types, from animation to audio, video, etc. The Learners can also evaluate courses to rate the effectiveness of the content and suggestions for improvement. Regarding improvement areas, when I upload animated training packs in Microsoft PowerPoint format, the animation and transitions are lost. This makes it static.
I have very strong feelings about TalentLMS, most of which have to do with the limitations of the programming. The built-in builder has some rather serious limitations. If you are porting in SCORM files to build resources in Captivate or Articulate, their program is only compatible with SCORM 1.2, which is a really old SCORM packaging format. The output is kind of clunky. The learner experience and UI is really basic, and this is an out-of-the-box, bare bones, 'nothing fancy' UI. You do have the ability, like most learning management systems, to do some customization, and you'll need to work with developers to do that. The reporting is severely limited in that it only shows rules. You can't set up dependencies. You can't set up cyclical course, so you can't have equivalencies. The back end is kind of clunky. It's not as user-friendly as I would like it to be.