India is definitely a difficult one. I'm using it to represent Hindi, and that's the one that makes me the most uncomfortable, because there are so many languages. I think the intent is reasonably clear, but if all countries were that ambigious, I'd avoid flags.
Nuenki supports European Spanish (though now you mention it, I ought to make that clearer). If it were American Spanish, I'd probably use Mexico. I handle Portuguese that way.
Switzerland is easy, because I have no need to include their flag. German is covered by Germany (yes, I know of Austria), French by France, etc.
And I'm highly unlikely to add Romansh, if only because it'd be very difficult to translate with good quality. I would if I could though, I find it fascinating. For a flag, I'd find an online Romansh community and ask what flag people would find most respectful + representative, or if people would prefer I forgo it.
You argue that it's misleading. I see where you're coming from. It isn't perfectly explicit and unambiguous. However, I don't think it's misleading in practice.
Nobody looks at a Spanish flag and thinks it's denoting Catalan - I'd probably use a regional flag there - nor do people look at a Union Jack or an American flag and go "no idea what that's for". When looking to see if Nuenki supports Finnish, nobody looks for the Swedish flag. They look for the Finnish flag.
People know what the stereotypical flags are, particularly when they're learning that language.
So imo it's about absolute precision vs UX, and the UX of reading through a textual list of languages is awful. It's a complete pain to scan through without any kind of visual indicator. That's why, in practice, everyone uses flags.
I didn't previously use flags so widely. Adding them everywhere (e.g. the dropdowns on the demo) was a result of feedback from people who felt it would make it nicer to use. Also, they're generally alongside the full name (aside from the aforementioned cloud), to clear up any ambiguity.
Nuenki supports European Spanish (though now you mention it, I ought to make that clearer). If it were American Spanish, I'd probably use Mexico. I handle Portuguese that way.
Switzerland is easy, because I have no need to include their flag. German is covered by Germany (yes, I know of Austria), French by France, etc.
And I'm highly unlikely to add Romansh, if only because it'd be very difficult to translate with good quality. I would if I could though, I find it fascinating. For a flag, I'd find an online Romansh community and ask what flag people would find most respectful + representative, or if people would prefer I forgo it.
You argue that it's misleading. I see where you're coming from. It isn't perfectly explicit and unambiguous. However, I don't think it's misleading in practice.
Nobody looks at a Spanish flag and thinks it's denoting Catalan - I'd probably use a regional flag there - nor do people look at a Union Jack or an American flag and go "no idea what that's for". When looking to see if Nuenki supports Finnish, nobody looks for the Swedish flag. They look for the Finnish flag.
People know what the stereotypical flags are, particularly when they're learning that language.
So imo it's about absolute precision vs UX, and the UX of reading through a textual list of languages is awful. It's a complete pain to scan through without any kind of visual indicator. That's why, in practice, everyone uses flags.
I didn't previously use flags so widely. Adding them everywhere (e.g. the dropdowns on the demo) was a result of feedback from people who felt it would make it nicer to use. Also, they're generally alongside the full name (aside from the aforementioned cloud), to clear up any ambiguity.