TL;DR
1444% growth over the past 12 months for the inlang SDK
using the next 4 weeks to iterate on lix positioning for third-party developers
the ai markdown editor as lix change control showcase is on its way
Introduction
Awesome month.
Now iterating fast on the lix positioning towards third-party devs.
is in San Francisco till the beginning of April to have in-person conversations around lix.Hit Samuel up if you’re in SF.
Growth
1444% weekly download growth for inlang SDK over the past 12 months
Every inlang growth is lix growth.
Lix itself is being prepped to grow by itself via third-party developers.
The weekly downloads for the lix SDK are going up as well. Users are updating their inlang apps, which leads to growth for lix.
Iterating on lix SDK positioning
The next weeks will be used to iterate quickly on the lix SDK positioning to start lix growth independent of inlang.
What is hooking third-party developers?
Provide examples of good fit use cases for lix.
Make the getting started simple, etc.
Reply to this email to provide feedback on the snippet below.
Lix is a change control system that runs in the browser and an SDK to build web apps.
A change control system allows storing, tracking, querying, and reviewing changes in different file formats, e.g., `.xlsx`, `.sqlite`, or `.inlang`. Compared to a version control system, a change control system understands “what” changed in a file, e.g., cell C43 in the financials spreadsheet changed.
Lix is not a git replacement, nor is it designed for software engineering. The goal is to bring change control workflows to industries other than software engineering like health, finance, policy making, design, etc.
Features
- 📌 Versioning: The possibility to create divergent states (branches in Git).
- ⚡ CI/CD: Automations as we know them from software engineering.
- 🔀 Change Proposals: Similar workflow to pull requests in Git.
- 🤝 Collaboration: Built-in sync, enabling asynchronous (Git-like) and real-time collaboration (Google Docs-like).
- ✅ Validation Rules: Define and enforce validation rules for data and workflows.
AI Markdown editor as lix change control showcase
Next month (end of March), we are going to release the public preview 🔥
Progress has been slower than expected. Using Markdown as the document format involves handwritten serialization and de-serialization complexity. But Markdown is a key value proposition, and we are going to stick with it. Markdown has a rich ecosystem that will make adoption easy, and LLMs are trained on Markdown, which will make AI features easier/better to implement.
Progress this month (February)
✅ document editing experience with AI prompting
✅ lix change detection and diffing
✅ copy & paste workflow for simple markdown content
✅ kick-off internal iteration loop with own documentation
Next month (March)
bugless copy & paste workflow for complex markdown content
integration in the lix file manager
public preview!