The history of the creation of the SkillzRun e-learning platform is closely tied to this question. That’s why we wanted to share some of what we learned, in case you are trying to choose an online solution or are currently developing one of your own.
Before creating SkillzRun, in 2014 we had the experience of creating a web platform (LMS) for a Parisian linguistic school as an external web studio.
The client’s goal was to create a web LMS system to use as a blended learning tool (a mix between online and offline education). They needed a traditional structure with topics and lessons which required the integration of h5p type exercises (https://h5p.org/) and Learndash.
The UI/UX was developed using the journey of a character Samy through different levels, topics and lessons.
During the development stage we have received new requests for features, so the platform became more functional, and the mobile version became more and more complex to support.
Initially, the visualisation of all e-learning platform features on a mobile phone screen is quite a challenge. Therefore, when it comes to an even more complex and dynamic functionality, which is displayed differently on the laptop and phone screen, usually the functionality is being cut, simplified or even hidden. Or, for example, the push notification feature may be completely unavailable in browsers (obviously a negative point compared to the possibilities of push messages sent from the mobile app).
Meanwhile, the number of students using the platform on their mobile phones constantly increased, exceeding 60% by 2016.
We must admit that neither we as developers nor the client saw the problems coming in the overloaded mobile version. Here we realized the clear need to create the mobile app, which would resolve all the issues associated with the web version and ensure user-friendly and ergonomic usage of the platform on mobile phones, instead of a limited version of the web platform.
Nevertheless, we understood that there were some functionalities that just couldn’t be fully adapted to the mobile app. For example, long documents or exercises that require long written answers, As well, some users would require a web version if they didn’t have a smartphone.
One more important point was the flexibility of the administration part of the platform. When the administration panel (which was not initially properly built) meets the increasing volume of functionality during the development process, which differs between the web and mobile visualisation, it creates a big mess in the management and analytics. So choosing the programming languages and designing accurate application architecture (particularly when the platform, content and number of users increases) are quite crucial.
Basically, there were not a lot of learning platforms with mobile apps in 2017, and even now, it’s still like this. That’s what inspired us to start SkillzRun.com.
In creating SkillzRun, we were trying to resolve some of the problems with the web platform, and make the administration ready to handle the features of the mobile and web versions. The goal was to create a platform simple in terms of administration, and user-friendly for the students, and which would be highly competitive in the market of online learning apps. At the same time, we needed to be able to add new functions without overloading the back office.
We started in 2017 by choosing the most flexible and quick programming languages: react / node.js for the back office and web version and java/swift for the apps. The back office was developed separately from the web display, but as a dedicated ergonomic panel for the administration of content, users and statistics.
Today, the apps and web platforms should take into account the up-to-date requirements of online products, including efficient UI/UX design, animation, ergonomics and many other features. If you feel ready to discover the platform, do it for free here:Registration
We will be more than happy to receive your feedback!