Platforms and projects: one shape that survives the second customer
Most tools give you a folder of files and let the naming collapse under its own weight. locoloop has exactly two levels, and they mean something.
Platform, then project
One app. The web app, the iOS app, the marketing site. It owns the key namespace, the default file format, the source language and the list of locales you ship. An API key can be pinned to one.
A variant of that app. One customer’s white label, one market’s regulated wording. It overrides the strings that differ and inherits every string it does not.
Inheritance is the point
Change a shared string once and every variant that never overrode it follows. That is the difference between five projects and five copies.
What a platform decides
Its file format
pull returns that format by default, so the build writes the file it already reads.
Its locales
Enable a language on the platform and every project under it gains that column.
Its access
Membership can be granted on the whole workspace, one platform, or a single project.
Model your apps in about ten minutes
Create a platform, import the English file, add a language. The structure is the first thing you will be glad of.