Actually sending money to bank account (wire transfer) has again become a viable option in EU, even with cross-border customers — Transferwise and similar services make it fast. Otherwise PayPal.

Invoices should be sent with whatever tool you are managing your invoicing or tracking hours with. It doesn't have to be in sync with the payment system in case you are sending only a few dozen invoices per month.

Just as the post is saying — having a save interaction instead of autosaving is a growing UX liability anyway. Just imagine when the younger generation at some point doesn't understand the concept anymore. "Save? Huh? What do you mean?"

I understand now how it looks from where you are standing.

We were probably too eager to share the results of our research so we didn't pay enough attention to how it looks and what is the wider context in play here.

Well-manned marketing teams are running over sites like DN with their continuous content production so it doesn't make a difference that we are a small team of designers and developers, spun off from a design studio. All's the same if it looks and feels the same.

Thanks for shedding light, Thomas. We'll think out a better path of communication in case we have something interesting to tell next time.

No one in our team currently speaks Portugese, Finnish, Dutch or French, but these are the native languages for thousands of our users. They've often found us only because of the localisations that we've published in their native language.

In a rare case they need actual live human assistance, we either use translator's service or speak with them in English — if this is their secondary language and acceptable to them.

Spam? No teeth? Come on, Michael. You just don't want to listen to what I'm saying. Telling that one has to look each case individually is unhelpful basic truth. Then you move on to one such case but fail to notice that this actually is the core case where my argumentation is countering your opinion. Anyway — good luck.

Yes, sure. I used mainly Eurostat data. Start with this report: http://ec.europa.eu/public_opinion/archives/ebs/ebs_386_en.pdf

Yes, seeing the point behind generalizations requires a patient reader.

Anyway, about Bob's plumbing. That's actually my point — locality doesn't help. In my 50 km radius, 60% speak Estonian, 35% Russian and the rest are usually OK with English. As a rule of thumb, some level of multilingualism is true for most European urban areas. Especially here in the east.

Yes. It's a pain. We are balancing localizations so that some languages only have basic website content (eg our FAQ and developer section are only in the few main languages) and some texts are just translated — not thoroughly localized with the help of native speaking copywriters. Even with those omissions we are still only able to cover 8 languages on our site — out of the 23 official and more than 40 unofficial EU languages. As our team grows we are slowly adding more.

I found you another chart. Sweden is on par with Denmark. Sorry for not including it :P https://jakubmarian.com/wp-content/uploads/2014/05/english-eu.jpg

Johannes — thank you for pointing out the mistranslation.

About shamelessness and reaching opposite conclusion — I'm afraid you didn't focus on the conclusions of the research as you were busy opposing to the final part of the post where we are talking about our solution. All right, I understand and respect your stance.

But let's move on from there. The conclusion of the resarch is solid — you are losing traffic — and therefore business — in the small European nations if your site is only in one language, no matter if it's the state language or English. People prefer using web in their native language, no matter their location. Being able to speak a language doesn't help if they even don't see your site in search results.