Your first 10 minutes with logiCells.
Once logiCells is released, install the tools, check your environment, open a starter and change one thing. The goal is a running application before any architecture lesson.
Developer: free after registration for learning, building and testing without production use. One certificate is planned for each registered developer, with five concurrent sessions each, including across separate projects. Downloads and session enforcement will be offered once technically accepted.
The logiCells package isn’t published yet. You can read the full loop below now. Early-access programme participants receive the first builds ahead of public release.
Get early accessDownload, check, open, inspect, change, run.
The loop is deliberately small. If a step is unclear, that’s useful feedback: The developer onboarding is being shaped around exactly this first run.
Install the tools with Developer
Once the package is available, verify its version and install the Runtime and cell CLI under your Developer entitlement. These rights do not cover live business operations.
Go to the download pageCheck your environment
Run the doctor. It tells you what’s missing before you lose time on an obscure error.
cell doctorOpen the Task App starter
Open the starter folder in VS Code with the logiCells extension installed. The CLI stays available for anything you want to automate.
Get the Task AppInspect the application
See the assembled application: concepts, relations, views and actions as the runtime resolves them.
cell application inspect app.lgcChange one field, then plan the change
Edit one field in the model and ask the planner what it affects. It tells you whether the change can be applied incrementally or needs a wider rebuild.
cell application compile plan app.lgcRun it
Start the runtime and open the application.
cell server start app.lgcTell us which step and what you expected. That’s exactly the feedback we need. Send feedback
See how the same loop handles a real client request. From request to quote