Why is it so hard to get all duolingo features in one place?
If I want to check on my ranking within a group I have to use my Android app, If I want to use the chatbots I have to borrow my wife's iPad, If I want to use labs I have to sign in on a computer, if there's a weekend XP target on Android then 200XP done on the computer apparently doesn't count :(
I could pick any device and stick to it but for the features I like I have to use multiple devices per day which isn't always possible, and also makes me wonder what I'm missing out on if I haven't e.g. used the iPad for a few months
When the likes of slack use technologies such as Electron etc to create native front ends that just interface with the web, I don't know why duolingo can't use something more universal for devices and have all features available on the website
It's just Duolingo has to program for many different applications. What's nice about iOS, or so I've heard, is that the operating system is similar on each phone, so it's easier to develop. Android has many versions, so they have to make sure it's compatible for each version. I should know as I notice in my older Android phones, some apps don't work right, such as YouTube. The web version has to be compatible with as many browsers as possible.
Not only are they developing for so many different systems/versions, they also have to consider the screen. With a web browser, they can make the app look like a regular web page, but on small screens, it has to be formatted to whatever people are using.
Anyways, those are some of the reasons why there are many different version. You also have to consider how many people are working on each version.
There are SDKs which cater for multiple devices though (I've created games for Android and iOS and only had to code once, then select the platform during compile, which means they might be writing native code for each implementation) and native clients which are basically just wrappers for web browsers such as Electron are what a lot of larger companies use.
As for my example of XP gained through the website not being registered to Android devices, that's just an API call, if anything it's harder to do wrong than right since somehow the source application (or other route, such as labs) of the XP has to be stored so that it can be filtered out
I see. You should tell Duolingo (and Google, as some of my Android devices have buggy apps now) about these SDKs so they can put these things on other devices easily. I wish you the best!
It is because monetizing the apps is easier than the web. iOS users are more likely to pay for something than Android users so iOS gets chatbots and health (which you can pay to refill*). iOS and Android get groups because apparently that keeps people engaged (and watching ads to get more lingots/gems) and the web version gets nothing because it is not very profitable.
* you don't pay to refill health, instead you pay for gems which you can use to get more health.
I don't think it's a question of being easy or hard but rather a conscious choice on their part. Between the Android app and the iOS app it's rather baffling I agree, but between the app and the web version I think it's just a matter of them wanting us to use both platforms for higher revenue.
if there's a weekend XP target on Android then 200XP done on the computer apparently doesn't count
It works for me... maybe you're having synchronization problems?
I agree, even the lingots are worth different amounts on different platforms. So on my ipad I get blue gems which are worth ~10x more then the red ones so it converts how many I have back and forth...I'm not sure why they did that.
Also I wish all the features would get implemented on the computer so I dont have to download the app on 3 different devices to get all the features :/
That's a question I asked myself for quite some time. My girlfriend has an Android phone and she has all the nice stuff I really want to have on iOS too, like looking into the sentence discussion threads , turning off the motivational owl, having weekend-challenges, and so on... And it seems to take ages to get some of these on iOS as well or not getting them at all like the sentence discussions. On iOS you just get non-descriptive updates (all are labeled as "bug fixes and increased performance") and the heart-system, yaay (which I often bypass by doing new lessons on the webpage) . And what really bothers me, as alickg1 said, there are ways to ensure you have the same feature set on different platforms, it's not really hard from a software engineering point of view.