How Lucy Platform works.
From a screen in Lucy Studio to an update on every device. Here is what each part does, and where Lucy stops.
TestStageProdDevelop in Lucy Studio.
Lucy Studio is where screens, data and logic come together. You start from a Figma frame and end with a screen that runs on a device.
- Figma importCopy a frame with the Figma to Lucy Studio plugin and paste it onto the canvas. It arrives as widgets. Auto Layout becomes Row or Column, and text styles are imported separately.
- ComponentsBuild a component once. Edits to the master reach every instance, and each instance can override its own properties.
- DataRegister an API or a real-time socket as a Data Provider. Responses fill a Data Set, and widget properties bind to it by drag and drop.
- LogicWrite logic in plain JavaScript, ES6 and later. Page-level code goes in the page's script window.
- AI in the editorAsk Lucy Devora in one sentence. Screen edits apply at once and can be undone. Script changes are shown first, and you apply only the parts you want.
- PreviewLucy Player runs on iOS, Android, Windows and macOS. On the same computer it connects automatically, and other devices connect with a QR code.
hourlyOutput.data←plant.hourlyOutputBound- // overview · page script
- function onChartTap(e) {
- Blog.d("Hourly output tapped");
- $app.openPage("dashboard");
- }
Deploy through TeamCloud.
TeamCloud keeps the versions, roles and approvals for every project, and runs Lucy Deploy.
- VersionsSave work in Lucy Studio as Git-style versions: stage, commit, push. Each version carries its tag, commit hash, author and message.
- What shipsNot the app binary. Screens are saved as screen definitions and behavior as JavaScript, versioned file by file.
- EnvironmentsDeploy to Test, then promote the same version to Stage and Production. Nothing is rebuilt per environment.
- ApprovalAn Editor can deploy to Test. Promoting to Stage or Production needs a Project Manager's approval.
- Where it runsLucy Deploy runs inside TeamCloud, on Cloud Enterprise and On-Premises Enterprise.
v1.5 hourly chart as line 3f2a81dRelease once, outside Lucy.
You build your app with Lucy SDK and the approved first screens, then submit it to the stores yourself. This happens once. After that, screen changes go through TeamCloud.
Update apps already in users' hands.
Inside the app, Lucy SDK takes the approved screens and draws them natively.
- What is in the appYour app ships with Lucy SDK, the engine that reads screen definitions. The engine is what goes through store review.
- DeliveryThe app checks for a new version and downloads only the changed screen files. Files wait in a temporary location and apply together, so users never see a half-updated screen.
- RenderingLucy SDK draws screens as native UI, not inside a web view.
- Live dataData that must arrive in order is delivered in full. Values where only the latest matters are batched to keep screens responsive.
- RollbackEach environment keeps its deploy history. If something is wrong, roll Production back to a previous version with a Project Manager's approval.
v1.4 → v1.5overview.screenchangedoverview.jschangedalerts.screenunchangedsettings.screenunchanged
One project, mobile and desktop.
Create once in Lucy Studio and run the same screens on iOS, Android, Windows and macOS, drawn natively on each.
Technical FAQ
Is the app a web view?
No. Lucy SDK reads screen definitions and draws them as native UI.
Does every update need store review?
Screen and logic updates do not. A new Lucy SDK version or new device permissions need a new app build.
What do users download in an update?
Only the screen files that changed. They apply together once all of them arrive.
Can I undo a release?
Yes. Roll Production back to a previous deploy from TeamCloud, with a Project Manager's approval.
See how it fits your team.
Read the docs or talk to our team about adopting Lucy Platform.