All work

Niosk

The network is not a guarantee.

In development

An offline-first public-interaction kiosk platform for configurable flows, AI and multilingual voice on unattended hardware.

What I’m building

A public device cannot assume a continuous network or a person standing beside it. Content, interactions, hardware behavior and recovery need to make sense at the edge.

My role

Product & systems architecture

I’m shaping the boundary between central platform management and edge execution: local runtime, synchronization, device pairing, diagnostics, telemetry and AI/voice interaction.

Offline-firstEdge executionDevice resilience
Niosk operator portal overview with fleet status, offline kiosks, publishing readiness and visitor activity for a demo tenant.
Operator overview · Demo data
Niosk

Operator overview · Demo data

The design decision

Treat the kiosk as an operating environment, not a browser tab. Keep local execution and central control distinct, with explicit synchronization and recovery behavior.

What needs care

Offline state, reconnection, device health and unattended operation drive the design. Remote management and analytics need useful telemetry without making every interaction depend on the control plane.

The operator interface

Niosk workspace sign-in in dark mode, with language controls, empty email and password fields, and kiosk-operations context.
Development previewThe operator sign-in screen in dark mode.
Niosk workspace sign-in in light mode, showing the operator-access form beside a kiosk-operations panel.
Development previewThe operator sign-in screen in light mode.

Architecture walkthrough

From offline execution to synchronization

An illustrative system flow, not live product activity.

  1. 01

    Local runtime

    The kiosk executes its configured experience at the edge.

  2. 02

    Offline state

    Network loss is a runtime condition, not an instruction to stop the whole device.

  3. 03

    Local queue

    Local state and pending synchronization work remain distinct from central state.

  4. 04

    Reconnect

    Restored connectivity enables reconciliation with the central platform.

  5. 05

    Synchronize

    State and telemetry cross the synchronization boundary.

  6. 06

    Control plane

    Remote management, analytics and diagnostics inform the next operation.

Next case studyQasas / قصص