SoftN Examples

A catalogue of complete worked examples

SoftN Examples contains the source for the platform’s example applications, along with the tools that pack, test and release them. The collection is broader than a gallery of static screens. Each project exercises a complete path through interface components, logic and the runtime capabilities it needs.

The examples are useful both as applications to explore and as implementation references. Open a bundle in the runtime, inspect the corresponding source directory, then change a small part of its behaviour. A release carries the packaged .softn files; the repository remains the source of the editable project.

Tools, simulations and unusual workloads

The collection includes practical samples such as a component showcase, device-capability demos and app data interfaces. Creative tools include a house designer and a layered image-editor example. Local AI examples exercise browser inference. Simulations and games cover voxel worlds, households, train-yard scenes, tile puzzles and first-person interactions.

Pocket and SoftDOS explore emulator-style workloads in .logic. Those projects demonstrate pixel output, audio and substantial state machines. WarbleWire explores acoustic message transport. They are engineering examples, not a claim that every runtime feature has identical performance on every browser or device.

• Start with simple interfaces before studying a larger simulation.
• Use the component showcase to inspect supported visual building blocks.
• Read each example’s permissions and data model before adapting it.
• Treat third-party assets, names and notices separately from source licensing.

Examples have their own assumptions

An example’s networking or privacy model is not automatically suitable for a production service. The peer-to-peer poker sample, for example, is explicitly designed for trusted participants rather than an adversarial multiplayer setting. A local model demo still has browser, memory and model-download requirements.

Audio, microphone, network and GPU features depend on the host and granted capabilities. Use the example’s README and manifest as part of the specification. Do not infer permission or offline guarantees merely from the bundle extension.

Build, validate and release

Use the SoftN directory to try listed examples, or download a published bundle and open it in a compatible runtime. Developers can build the collection, run its tests and validate an individual archive against the source. The release process records checksums and catalogue metadata so the platform can consume a specific published generation.

The collection includes Apache-2.0 source and separate notices. Some larger games also have their own repositories, including The Night Window and Last Sound. Follow those projects for their individual builds, story details and asset credits.