A project can be more useful than a hosted screen
When an application is only delivered as a URL, the user sees the result but not necessarily the editable project behind it. SoftN bundles the distributed interface, client logic, assets and optional data seeds into a portable .softn file. Builder and Studio can reopen that project for further work.
This makes SoftN useful for learning materials, reusable internal tools, specialised interfaces and runtime experiments. Portability is a property of the project and its supported hosts, not a guarantee that every connected service works offline.
An illustrative local-to-hosted path
Start with a local task or inventory tool. Define its fields and interface, write or generate the .logic behaviour, and test it in Builder with preview records. Export the bundle and open it in the runtime to verify the distributed application.
When the workflow needs shared business records and account permissions, choose an appropriate backend. FormLogic can host the application and expose permission-checked actions. A standalone private backend is another path for an application with its own server logic.
- Build a complete local interaction first.
- Keep credentials and private backend source out of client downloads.
- Test the bundle’s requested permissions in the actual host.
- Choose the data and identity model before adding synchronisation.
Three separate responsibilities
SoftN interprets the interface and connects it to runtime components. ZIPP executes the .logic behaviour. The host supplies allowed capabilities, including the appropriate data bridge. Native SoftN environments can use XDB’s Rust SQLite store, while browser environments have their own TypeScript data service.
That separation lets the same app format support different deployment models without pretending the underlying storage, process privileges or networking are identical.
Use examples as implementation evidence
The SoftN Examples collection covers forms, visual tools, local AI, simulations, games and emulators. The Night Window and Last Sound show more involved narrative interfaces, timed audio and 3D state. Read an example’s source and permissions alongside running it.
A demonstration’s assumptions matter. A trusted peer-to-peer sample should not be repackaged as a secure competitive service without a different authority model. Browser audio, GPU and device support also need testing on the target hardware.
Measure the app, not only the engine
For a real deployment, inspect load size, first useful interaction, input responsiveness, memory use and the cost of moving data between the VM and host. A fast standalone engine benchmark does not determine the performance of a complex interface.
Read the source and asset notices before redistribution. SoftN, ZIPP and XDB have their own licences, and connected proprietary products or third-party media may introduce additional requirements.
Project references: SoftN · ZIPP · XDB · SoftN Examples. Their project pages link to the underlying implementation documentation.
