Melta
Features
Multilingual: prepared from day one
For anyone who starts in one language today and wants to keep the second one open. Every Melta product is built in the language of your concept, and built so that all visible texts live in a catalog instead of the code. Another language later is a translation of that catalog, not a rebuild.
What you get
Adding languages afterwards is an expensive project for most products, because the texts are scattered everywhere. At Melta the structure is there from the start:
One language, done properly
Your product speaks the language of your concept throughout: interface, error messages, emails, legal pages, date and currency formats.
All texts in the catalog
Every visible text lives in a language file, not in the code. The build checks this and rejects texts that try to sneak into the product past it.
A second language as a file
When a language is added, the catalog is translated and the language registered. Language switch, fallback to the first language and matching formats are already built in.
Emails included
Subject lines and texts your product sends come from the same catalog. A confirmation to a French-speaking customer arrives in French.
How it works
You decide on the first language at the concept stage, and later whether more should follow:
- Concept - The language you describe your product in becomes its product language. It is stated at the top of the concept and applies to everything users see.
- Build - Melta builds the product in that language and puts every visible text into the language catalog. That is not an option but a rule the build checks.
- Second language - You say by chat which language should be added. The catalog is translated, the language switch appears, visitors get their browser's language.
- Upkeep - Every later change to texts is made in all registered languages, and the build checks that no language has gaps.
What the catalog does not cover: content that you or your customers enter, such as course descriptions, product texts or posts. That is data, not product text. If it should be multilingual, that belongs in the concept, because it affects data storage and forms.
Who this matters to
For businesses in Switzerland with a booking system or a shop. German to start, French or Italian as soon as customers from another part of the country arrive. The structure is there, the translation is a small job.
For founders with a SaaS product. Test the home market first, then move into the next one with English. Without the second step rebuilding the first.
For coaches with a course platform. The interface in two languages, the course content in the language it is taught in. That is exactly the separation the catalog makes on its own.
What it costs
A concept uses only a few credits; after that your product runs on one plan per organisation that brings credits for building and changes every month. Another language is a change run paid from those credits. All the numbers are on the pricing page.
Frequently asked questions
Which language is my product built in?
The language of your concept. Describe your product in English and it speaks English: interface, emails, legal pages, date and number formats. One language is built on purpose, not several at once.
What does prepared for more languages mean?
All visible texts live in a language catalog from the start, not in the code. A second language is a translation of that catalog plus a language switch that already exists. That is a small change run, not a rebuild.
How do I order a second language?
By chat, like any other change: say which language should be added. The catalog is translated, the language switch appears, and visitors get their browser's language, with your first language as the fallback.
Are my own contents translated too, such as course descriptions?
Not automatically. The catalog covers the product's texts: menus, buttons, forms, notices, emails. Content that you or your customers enter is data; if it should be multilingual, that belongs in the concept, because it affects data storage.
Why not build multilingual right away?
Because it makes every build longer and doubles every later change, while most products do not need it. A studio in Zurich starts in German and orders French once customers from Lausanne arrive. The structure for that is already there.
One language today, two tomorrow, no rebuild.
A concept uses only a few credits. Your product starts in your language and is prepared for the next one.
Get early access