For all my new projects I just use English only without any translations If it grows really big and I'll need it - it's easier to add it LATER than by wasting time on it NOW

@andrii_rom Unless you have good distribution in a specific non-English speaking language it’s not useful at early stage

@dagorenouf 100% agree, not worth it unless you already have users who'll benefit from it When adding it my logic was that it would help me get new users from these regions but it's the last feature they care about😂

@andrii_rom No Spanish? 🤷‍♂️🤣

@michael_kove don't have Spanish customers😅

@andrii_rom i18n is incredibly easy with ai, a single prompt can set it up for my entire app. Then adding another language is another single prompt. What issue did you run into adding i18n with ai? i18n was so easy to set it it blew my mind and made me double down with cursor

@richkuo7 It just consumes too much time maintaining the translations (they're all stored as .json, so when adding a new feature I've got to make sure I add it for all languages)

@andrii_rom it depends on what you're building. In native mobile it, and in certain sensitive topics (e.g. health), it makes a difference.

@Ysquanir I agree, for native apps it makes sense But browsers have built-in translators anyway

@andrii_rom Isn’t there a better solution to this?

@DavidBoros19 not doing i18n at all

@andrii_rom I have not seen a single person IRL who would ever use translations built into browsers. In the website analytics these people are also rare outliers

@egorka I think older generation relies on it more I've seen my parents use this feature, and it's enabled by default for many people Younger generation tends to know English better anyway

@andrii_rom I think i18n is mandatory always

@_julienbrdn I think mostly if you target people from foreign countries. Do you use i18n?

@andrii_rom the codebase should be i18n'd from the start. That doesn't mean you have to localise from the start. But having to backtrack later on down the road when you do need a translated ui and realise you didn't set yourself up to adapt to new markets is the far bigger time suck

@jennabrinning Maybe you're right Jenna But I hope that at least with better AIs and translation tools in browsers i18n won't be needed anymore

@andrii_rom Kind of agree, but for me, my Sober Tracker for some reason is rather popular in China... and I do think it is because localization of screenshots and so. But for sure, it takes time. And English should be first one choice... I'm trying to integrate this thought to my life.

@TerekhinIvan I think for native and mobile apps localisation makes sense, especially if you have users there But for webapps I feel like it's useless, since browsers can translate texts on it's own now and most people use this feature

@andrii_rom Was just talking to someone who is building a translation-extension earlier today. Said the same thing -- only enterprise needs to deal with it, and most people just use automatic browser translation anyway. That said ... if this builder could make it super easy, then i18n is

@kenahlstrom yep it would not hurt to have if someone figures out a pain-free way to do it but right now it's too much effort for too little gain

@andrii_rom not really, none of my friends know they can just install a browser extension to translate ofc friends who are into tech know, but the regular person dont

@bladeemaxxi i think it's not even a browser extension, this feature is integrated in the browser itself every time I open a non-English website, I get a popup if I want it to be transleted in English

@andrii_rom Yeap, I regret as well. If you have any updates, you will make sure to include them for all languages

@indiesoftwaredv True, and it's for changelog, blog posts, emails, updates everything To appease like 5 users 100% not worth it