We are strong believers in the power and freedom that Transifex Native is bringing to localization industry! The radical way of addressing localization issues in a modern way can revolutionalize the adoption of localization by more applications and can drive the whole industry in uncharted territories, going beyond company gained benefits.
With this dynamic in place we want to involve as many people as possible into unlocking and exploring all the possible paths that Transifex Native can bring to the localization field. It would be a true waste and narrow-sighted potential for Transifex company to know and provide all the answers that are opened up because of Transifex Native. The Open Source community has been proved to be a true leader of change, innovation and creator of new markets.
Transifex Native is an initiative on a different way to store and serve localized, with no need for files and heavy dev. resources on localization related updates. More specifically Native consists of:
Language SDK, to wrap strings for localization. Each language has its own Native SDK implementing localization in the exact same way, supporting the exact same stuff (ICU syntax + metadata syntax)
A Content Delivery Service (CDS) that holds and serves latest global content between your app and your TMS or editor.
Using these two items enables Transifex Native in an application. For the time being the Content Delivery Service needs to speak with Transifex application in order to get back new translations, but we want to decouple this, so that CDS can be fed with new translations in other ways too (via file upload directly on the CDS, through an API that feeds translations to CDS from other services, etc.).
To come back to your question Transifex Core is not open sourced as it’s the core of Transifex business. Yet Transifex Native is evolving to a standalone open-source alternative narrowed down to hosting and serving real-time translations to an application. This means that Transifex Native takes localization as a given and works apart from that, so no TM, glossary, Editor, 3rd party integrations and in general TMS functionality.
As Native is an initiative in the making, we are still defining the next steps and want to work together with more people into shaping where Native will move to.