Lokalise is a translation management system, which is designed to make the process of localization faster and easier. Our platform reduces manual work and routine tasks that appear while translating web and mobile apps, games, and other software.
With Lokalise you can: ✓ Translate your localization files (.xml, .strings, .json, .xliff, etc). ✓ Collaborate and manage all your software localization projects in one platform. ✓ Integrate translation into the development and deployment process. ✓ Set up automated workflows via API, use webhooks or integrate with other services (GitHub, Slack, JIRA, Sketch, etc). ✓ Add screenshots for automatic recognition and matching with the text strings in your projects. ✓ Upload Sketch artboards to Lokalise and allow translators to work before development starts. ✓ Preview in real-time how the translations will look like in your web or mobile app (iOS and Android SDK). ✓ Order professional translations from Lokalise translators or use machine translation.
Based on our record, Hasura seems to be a lot more popular than Lokalise. While we know about 117 links to Hasura, we've tracked only 11 mentions of Lokalise. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
I'm pretty sure, you'll find companies like this one which provide a nice GUI for helping with l10n or this one which offers translation services or this page that offers to convert between different formats, one of which probably has a nice GUI tool. Found them by 20 secs of googling. Source: about 1 year ago
Localise has no problem reading the json files or export to json, we recently started using it in collaboration with external translators. Source: about 1 year ago
Actually I don't have "my" app. But in our app we use https://lokalise.com/ to localize it even to Norwegian. Our team is not the most expensive company in the world btw. And we don't have 1B+ users all over the world. Source: about 1 year ago
Internationalization (i18n) pain for a documentation project is a process problem, not a feature gap. Documentation frameworks are not meant to translate your developer docs for you into the language of your choice. Some frameworks might offer i18n support, like the Crowdin support in Docusauraus v2. With Jekyll, you have to pick a theme like this one. I doubt if the reST or adoc frameworks would differ much from... - Source: dev.to / over 1 year ago
I've been thinking about building a micro saas very similar to this after having so many issues coordinating the localization of several products I manage. The only robust options in the market are incredibly expensive (for example https://lokalise.com/). Source: almost 2 years ago
> 2. ORMs do not hide SQL nastiness. This is certainly true! I mean: ORMs are now well known to "make the easy queries slightly more easy, while making intermediate queries really hard and complex queries impossible". I think the are of ORMs is over. It simply did not deliver. If a book on SQL is --say-- 100 pages, a book on Hibernate is 400 pages. So much to learn just to make the easy queries slightly easier to... - Source: Hacker News / 2 months ago
Another strategy is to model access control declaratively and enforce it in the application layer. ZenStack (built above Prisma ORM) and Hasura are good examples of this approach. The following code shows how access policies are defined with ZenStack and how a secured CRUD API can be derived automatically. - Source: dev.to / 3 months ago
Today, this ecosystem is going strong with new providers like Hasura, AppWrite and Supabase powering millions of projects. There are a few reasons people choose this style of hosting, especially if they are more comfortable with frontend development. BaaS lets them set up a database in a secure way, expose some business logic on top of the data, and connect via a dev-friendly SDK from their app or website code to... - Source: dev.to / 4 months ago
Hi! If you’ve ever thought about something like using GraphQL for something like this.. You might like Hasura. (Obligatory I work for Hasura) We’ve got an OpenAPI import and you can setup cron-jobs or one-off jobs and do things like load in headers from the environment variables to pass through. There isn’t currently an easy journey for chaining multiple calls together without writing any code at all, but you can... - Source: Hacker News / 4 months ago
Hasura.io — Hasura extends your existing databases wherever it is hosted and provides an instant GraphQL API that can be securely accessed for web, mobile, and data integration workloads. Free for 1GB/month of data pass-through. - Source: dev.to / 5 months ago
Transifex - Transifex makes it easy to collect, translate and deliver digital content, web and mobile apps in multiple languages. Localization for agile teams.
Supabase - An open source Firebase alternative
Phrase - A platform offering AI-powered translation tools for localization at scale.
GraphQL Playground - GraphQL IDE for better development workflows
POEditor - The translation and localization management platform that's easy to use *and* affordable!
GraphQl Editor - Editor for GraphQL that lets you draw GraphQL schemas using visual nodes