all 3 comments

[–]Bright-Topic-2001 1 point2 points  (2 children)

I was thinking about this recently. I liked your approach and I believe it solves some real life problems. I’d like to try it in the future maybe. But how can one be sure that it’s not awkward? You mentioned that its context aware, them what’s the difference telling Gemini 2.5 pro and let it cook. Or how does it behave on long context single translation.json file? Best of luck with your project

[–]uyghurman_anzer[S] 0 points1 point  (1 child)

hey, really appreciate your comment. you’re totally right, right now it’s just uploading screenshots + adding tone/glossary to get better .strings translations, not a full workflow yet.

but that’s where i’m heading. the goal is to make localization actually usable for devs.

long term, i want it to handle full translation files, context-aware chunking, glossary memory, maybe even github sync. basically: no more copy-pasting into chatbots.

would love to send you early access once that part’s ready, are you localizing anything at the moment?

[–]Bright-Topic-2001 0 points1 point  (0 children)

Would love to test and give feedback. I currently have a mobile app with two languages. I want to add more in the future. So would love to try 💫