Most apps start in one language and add others later, if a business case appears. We built Verahm differently, because the reason for multiple languages was never a business case. It's a picture given in Scripture of what worship actually looks like when it's finished.

Whatever else this vision tells us, it tells us that the final gathering around God is not monolingual. No single language is pictured as the "real" one that others are translated from. The multitude stands together, undiminished by their differences, each language fully present. That image shaped a decision early in building Verahm: French, Spanish, and Portuguese speakers would not be an afterthought bolted onto an English product. They would be built in from the first release.

Every verse a Verahm user reads is pulled from a real Bible translation in their own language (the Louis Segond for French readers, the Versión Biblia Libre for Spanish, the Bíblia Livre for Portuguese), not a mechanical translation of an English sentence. A meditation written for a Spanish-speaking user is composed in Spanish from the start, not translated after the fact and hoping nothing was lost. It costs more to build this way. We think it's the only honest way to build it.

Building this way is measurably slower. A feature that ships to English users in a week often takes three or four times as long once it is built to launch correctly in all four languages simultaneously, because a rushed translation is worse than no translation: a mistranslated verse reference or a meditation that reads like it passed through a machine erodes exactly the trust the app exists to build. We would rather delay a feature than ship it in a form that quietly tells three-quarters of our users they got the second-tier version.

It means native speakers reviewing content before it ships, not just after a complaint arrives. It means a Bible reference resolver that understands each translation's own verse numbering rather than assuming every language counts verses the same way: a real technical detail that has already caught real mistakes during this project's own content work. None of this is visible to a user opening the app. It is only visible in what does not go wrong.

We are not finished. Some content still defaults to English while we grow our library in each language, and we say so plainly rather than pretending otherwise. But the direction is set, and Revelation 7:9 is the reason: the multitude in that vision is not future decoration, it's the actual shape of the church, and Verahm is trying, in its small way, to build software that reflects it rather than flattens it.

Language features are easy to deprioritize when a deadline gets tight: they rarely show up in a demo the way a new button does. Naming the conviction behind this decision, in writing, is partly a way of holding ourselves to it later, when it would be simpler to let one language quietly lag behind the others. If you read this in French, Spanish, or Portuguese and something still feels unfinished, tell us. That feedback is part of how the picture gets built.

We would rather be corrected now, while the library is still small, than discover years from now that one language quietly became an afterthought after all. Revelation 7:9 does not describe a multitude that arrived gradually while everyone waited for the "real" version to catch up. It describes everyone standing there together. That is the target, even on the days we are still short of it.