Title: Hi HN community, we are Jake, Tzachi and Etai, co-founders of FlyCode (<a href="https:&#x2F;&#x2F;www.flycode.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.flycode.com&#x2F;</a>). FlyCode makes it easy for product, UX, and marketing teams to edit web apps without coding, so they don’t have to wait on (or consume) developer time, and can iterate, test, and release faster. See a quick example here: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=jDL5oa2nEHo" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=jDL5oa2nEHo</a>.<p>Non-technical teams frequently need to edit the copy (text), images, and links that appear in a web app. How to manage these has long been a pain on software projects. You can keep them separate from the code, in some form that non-programmers can edit, but this adds a lot of complexity and is usually brittle, as it can bypass the regular development workflows (CI, staging envs, deploy previews). It’s simpler to keep them in the code, but then only programmers can easily edit them. Everyone else has to wait to get their changes in, plus the devs have to do a lot of edits that aren’t their main work. This slows projects down and is expensive. It also means that product&#x2F;marketing&#x2F;UX teams can’t do things that require rapid iteration, such as sophisticated forms of A&#x2F;B or usability testing. This limits their work and ultimately is bad for both quality and revenue.<p>There have been many approaches to solving this dilemma, including custom built admin tools that are limited in functionality and require maintenance, offloading to CMS that require heavy integration, are normally used for simple static apps, and bind your stack to their SDKs. Or wasting a developer’s time to do it for you…<p>We took a new approach by automatically analyzing a codebase’s structure, similar to a compiler. This allows us to automatically prepare a project-specific version of our platform which product&#x2F;UX&#x2F;marketing teams can easily use to edit their text and images. We programmatically turn those edits into code changes. Our GitHub bot then takes these code changes and creates a pull request just like a developer would—but without the latency (and boredom!). Developers retain codebase ownership, while non-developers become individual contributors to the dev process, just like others.<p>We use well-established practices for parsing and editing source code (like <a href="https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;jscodeshift" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;facebook&#x2F;jscodeshift</a>), covering most of the major technologies used for building web apps (React, Angular, Vue, and Ruby on Rails included).<p>Once our software has parsed your codebase, it generates an editing portal for your app that teams can easily use to find, manage, and edit product copy, images, and links, and then auto-generate PRs. You can edit product copy regardless of whether it is in resource files or hardcoded (fun fact: some of the largest and fastest-growing tech companies have most of their strings hardcoded!), and you can replace and upload new images and icons to your product.<p>The integration with GitHub (<a href="https:&#x2F;&#x2F;www.flycode.com&#x2F;developers" rel="nofollow">https:&#x2F;&#x2F;www.flycode.com&#x2F;developers</a>)  took us a long time to get right. There’s not a lot of documentation around integrating GitHub to platforms, and things like connecting an org or connection requests turned out to be non-trivial. We&#x27;re proud of the result because unlike with other tools, you don’t have to do any significant integration work.<p>Our GitHub app finds texts and images in the source code and sends them to our platform (you have full control of what and where we scan). Once a user requests a change it updates the texts and the images in the codebase and creates a pull request.<p>We did a Show HN earlier this year: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=31166924" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=31166924</a>, which helped us get some serious leads, which was awesome. Since then we’ve moved out of beta, added new content types (images!), launched a new UI and visual editor (EAP), and automated the onboarding of new repos.<p>We have a handful of companies paying for this and spent the last year focusing on making it extremely simple to use. It only takes 3 minutes to connect our GitHub app and configure the system for your team to start editing. It doesn’t require any changes to your code, or any special maintenance. You can get started here: <a href="https:&#x2F;&#x2F;app.flycode.com" rel="nofollow">https:&#x2F;&#x2F;app.flycode.com</a><p>We are hoping to use this launch to get some more feedback from you all! We are far from our vision to be a platform for everything front-end but are working hard every day to improve the user experience and feature requests from our early collaborators (editing links, themes, variables, JSON configuration, defining in-code A&#x2F;B tests, etc.).<p>We&#x27;re really happy to show this to you all and thank you for reading about it. For those that sign up, time yourself to check that our “3-minute connect + config” claim isn&#x27;t just a sales tactic! We look forward to further conversation in the comments.
Upvote: