Great question, there are lots of multi lingual apps out there, and although localization isn't our main use case - We support multi lingual apps by identifying the resource files that contain the key-value pairs. From this point our platform continues to work as usual.
TinaCMS is great :) We differ from them and others in this space by taking the approach of making changes to code that the dev team manages (rather than markup like MDX). The tools are solving separate use cases, the one is managing content (which can be interactive but is mostly static), and the other is editing UX copy integral to the web app (which is usually inside react code for example)
We see a lot of opportunity in managing resource in git and are betting that the industry is going there, so shout out and love to the TinaCMS team and other players recognizing that git is where app resources should be managed.
Great note here - We see your point and need for playgrounds, we consider our solution complimenting Figma and other mock-up tools.
We'd like that other stakeholders in the company to actually be able to contribute to the codebase and make actual product edits, as well as creating mock-ups.
It's currently available as part of an early access program that you're welcome to join :)
You can contact us via the chat in the platform, or email hello[at]flycode.com
I remember how excited I was about a decade ago when Microsoft announced the Roslyn project, and how sad I was when switching my dev eco-system before it came out.
AOP wasn't a new concept, and code generation was available - but it was a hard task to get done, and not accessible to the general dev community.
Now, Roslyn ins't news anymore :) We have source generators in C#, and we not only have more main stream compiler plugins & annotation processor in Java and Kotlin (that spends a lot of time on their compiler API).
The same process has happened for the JavaScript ecosystem. The AST revolution has hit the frontend/JS ecosystem big-time. Tools like Babel (and derivatives like jscodeshift and recast) have democratized analysis and transformation of code bases. I urge you to play around with ASTExplorer to see how vast is the support for getting a proper AST for source-code.
Another big factor is the maturity GitHub marketplace. Today, smaller teams are able to ship production-ready apps for GitHub as the APIs have stabilized and are much documented than a few years ago.
All these together makes code-editing products much more feasible than a few years ago. It's not that AST and source editing novel ideas did not exist it's just they matured enough that you can actually build a product that targets a big enough segment of the market.
The scan is 100% automatic and performed live - There might have been a small config issue, once fixed your system would be up and running in minutes :)
CTO and co-founder here, I couldn’t be more proud of the team for shipping FlyCode’s open Beta so fast!
As a compilers enthusiast for more than a decade, it is marvelous how analyzing and manipulating code has become more accessible in recent years and the possibilities it unlocks... very excited to empower teams to make edits for real web apps and save their developers time.
Feel free to contact me as well at: etai[at]flycode.com
Next thing we develop would be a HN post editor XD