[1] https://blog.duolingo.com/ending-honoring-our-volunteer-cont...
Part of the reason that content is slower to produce now is just that the standards are much higher. Internally we draw a distinction between the old volunteer-contributed content and the new content which is aligned to CEFR guidelines for how languages should actually be taught. Aligning content like this is not only more expensive but also requires more coordination and oversight from domain experts compared to previous methods.
I love HN for little nuggets of explanation like this.
What made you as a company change your mind?
I honestly don't see the point of following CEFR for an app like Duolingo.
Professional and GOOD teachers, that love to teach and did that for several years, know how to teach a language. THey don't need to follow something such as CEFR to know if they do well and what is interesting to teach and in which order.
I find it more important to make interesting lectures which do not follow a standardized curriculum. When someone is learning a language in this way will naturally go toward a CEFR based courses if needed afterward, with a big head start and only when he feels ready.
Also, not allowing to see 'already seen' vocabulary is a very strange move for an app, I guess it's for preventing having the vocab in a app like anki which makes duolingo less useful, but still, even if I don't use such app, having to screenshot all the time to have my vocab is a total pain.
Finally, the app doesn't seem to understand which words/sentences you already know and master and clearly do not need to see for the 400time instead of new vocabulary. Even having maximum points all the time and very fast will usually result in the same vocab shown again and again. It seems like an almost basic statistical problem, so I don't get why it's not fixed.
Also, some vocab is very strange, for example using 'es tut mir leid' in German to just say 'I'm sorry' feels like the content is automatically generated instead of having a linguist or even a German behind.
Duolingo's goals are not the same as mine, and the best thing it does by far is to pretend (and make me believe) that I am learning a language.
I had the idea (I'm not saying it's original, it's just what I thought at the time) of course lessons consisting of a series of questions, and each question is defined as a JSON object.
There are built-in question-templates like multiple choice, free-form answer, or just true/false.
If a course needs something really specific, then it can implement a custom renderer for that new template type, so that a course isn't held back by the upstream project. If it's a template that might be useful for more people, then it can be integrated into the core project.
- You can add multiple question. - Each question can have some content, one image and multiple options users can select. - Each option can have a title, an image and a feedback displayed to users when they select/confirm that option.
I want to add an option to import/export JSON. It's actually on the roadmap for v1:
- https://github.com/zoonk/uneebee/issues/41 - https://github.com/zoonk/uneebee/issues/40
In the future, I also want to implement some kind of plugin system because certain subjects require a different learning style. But I'm not sure yet how this would work. I need to think about it.
Right. People say that HelloChinese is better for Chinese because some of the question types are drawing Hanzi, so I think this is a perfect use case for a plugin system where a course could add a plugin for Hanzi/Kanji drawing and not be slowed down by the core developers.
I think that while this might be useful for teachers, it might be more sustainable if courses were stored in a version controllable medium to facilitate multiple collaborators.
My initial thought was to actually use GitHub to store the content. Either on Markdown or JSON - to have some version control. I like how Exercism [1] does it. But I thought it would be hard for teachers - unfamiliar with Git - to update lessons.
Then, I thought about implementing a version control system for the project but I felt I was overcomplicating things for an MVP. But I like the idea of having some kind of version control to improve collaboration.
You could also have a cloud service to store the project files, and then the teachers can just login to the editor and click save to upload their latest copy of the course.
Personally, I think Duolingo shouldn't exist in its current form. The courses are all created by teams of volunteers and only able to be contributed to by those volunteers, which slow downs course creation and bug fixes to courses. Additionally the data is all held hostage by Duolingo, which prevents you from integrating it with Anki for example. I don't think Duolingo should be getting revenue when most of the work is done by volunteers. I think a decentralized open source version should exist, much like how anyone can modify and upload Anki decks, people should be able to modify and upload "Duolingo-like" courses.
Re: marketplace:
I think this is a great idea! There are Anki decks that are sold by creators too, like Spoonfed Chinese. I think this is an actually fair way to implement learning like this.