4 ms·

i love the idea of bringing "permissionless collaboration" to standard SaaS apps. but the question i kept on asking myself while reading this was...what will ge

i love the idea of bringing "permissionless collaboration" to standard SaaS apps. but the question i kept on asking myself while reading this was...what will get developers to start building with lix vs. what they know/trust? perhaps the catalyst here is AI. as you write, if you want AI agents to interact with your systems, "you need a controllable and auditable mechanism for observing an agent's changes and accepting or rejecting them." so if you build with lix, your app is "agent-ready." that's pretty cool.

samuelstros 2y ago
> what will get developers to start building with lix vs. what they know/trust? 1. the ease of building an app 2. the additional features like change history, ai readiness, etc. that cloud-backends like supabase or firebase don't/can't provide it will be our job to communicate 1 and 2 to developers in the future. for now, we focus on building inlang.com as the first lix app(s). inlang.com might by itself become the convincing argument to build on lix "oh look how they build inlang with lix".