4
1 Comment

The #1 Growth Feature You (Probably) Haven't Implemented

A few years ago I went to a talk by one of the early growth PMs at Facebook.

For context, the early Facebook growth team is considered to be one of the best in Silicon Valley history.

He stated that out of all the features they launched in the early days of Facebook, only 1 truly out-performed user growth expectations...

The feature was localization.

On the surface, this feels like an obvious growth feature. Yet, the vast majority of indie + startup founders are still not taking the time to translate their apps.

(Despite often having 30-80% of their traffic coming from countries where English is not the primary language)

My friend Jordan had this same intuition, and confirmed this while working as the founding engineer at his last startup (Phantom wallet). Where localization was their top growth feature.

However, he also realized that the process was extremely painful to set up and manage. Not to mention they spent thousands of dollars on 3rd party tools and manual translations.

For this reason, we decided to launch the first localization tool aimed at developers called Blendin:

https://blendin.ai/

We believe that our approach will be the future of localization.

But the purpose of this post isn't to promote our product.

Even if you don't use Blendin, I HIGHLY recommend everyone on here localize their app sooner rather than later.

Not only will you provide a better experience for a portion of your users, but it very well may be the top growth feature you launch this year.

on September 10, 2024
  1. 1

    The cost/complexity barrier is much lower with open-source CLI tools:

    i18n-pseudo — test your app's localization readiness in minutes without real translations. It generates pseudo-localized files that reveal hardcoded strings and layout issues: npx @i18n-agent/i18n-pseudo en.json --out pseudo.json

    i18n-validate — add to CI to catch missing translations automatically: i18n-validate --min-coverage 90 --fail-on-error

    i18n-convert — convert between formats (JSON, YAML, PO, XLIFF) so you're not locked to any TMS: i18n-convert en.json --to po -o en.pot

    All free, all offline, no vendor lock-in.