Not everything in Moodle’s raucous 15-year history has been smooth sailing.
For the fifth question in MoodleNews Founder Joe Thibault’s “Moodle 2032” survey, Moodlers were invited to acknowledge the areas that need a little more work:
What challenges have remained insufficiently dealt with or unaddressed by Moodle and other LMS?
“Complexity” tends to come to mind when discussing Moodle’s shortfall, at least until the arrival of the “Boost” theme and the focus on experience in Moodle 3.4 that is. The placement of a growing number of features across menu could feel patchwork-like. Once newer and flashier systems began to promote themselves towards faculties and users, the missing intuitiveness started to weigh on users, sometimes irreparably so. It is difficult to estimate the number of users who became permanently turned off of Moodle. Due to their preconceived notions, they are unwilling to give the platform’s new directions a chance.
For developers and Moodlers who interact with the LMS code, this collage of thinking, design, and styling seems to permeate under the hood, often approaching the dreaded “spaghetti code” status. It is still needlessly difficult to maintain, support, and optimize Moodle’s performance and resource usage. To boot, there are still plenty of unpopular bugs with years of tenure.
Another important, less common, complain involves integration and flexibility. While, for many reasons, Moodle is the standard for openness in learning technologies, there are still a few areas of friction with standards and other platforms. Perhaps most exemplary, Moodle can plug information from external sources in, but Moodle’s externally facing API, which would allow other systems to access Moodle’s features and data, is still a work in progress.