Nokl

The existing product direction exposed too much implementation detail directly to users. The experience felt closer to a desktop utility than a modern collaboration platform, making the product harder to explain, demo, and position for broader audiences.

The redesign explored how Nokl could evolve into a web-first experience that felt approachable without hiding the technical strengths that made the platform valuable in the first place.

Another challenge was audience overlap. Individual users, technical users, and potential business teams were all interacting with the same product surface, even though their goals and expectations were fundamentally different.

Instead of treating Nokl as a collection of infrastructure features, the redesign approached it as a cohesive collaboration platform with distinct roles, workflows, and interaction models.

Most collaboration tools revolve around uploading, syncing, and duplicating files through centralized cloud systems. Infrastructure behavior becomes part of the user workflow.

Nokl explored a different model: devices themselves became the collaboration layer. Files remained at their original source while users accessed them directly through secure peer-to-peer connections.

This changed how the interface needed to behave. Instead of abstract cloud storage containers, the product emphasized device context, mounted access, shared folders, and visibility into where files actually lived.

The experience was designed to feel less like uploading data into a service and more like working inside a connected ecosystem of personal and team devices. That mental model shaped navigation, sharing, onboarding, and system states throughout the product.

Device-centered workflows

←1 / 4→

Dashboard

A device-aware overview that surfaces connected machines, shared folders, and access status without abstracting the underlying topology.

Devices

All connected devices in one place — each with availability status, mounted drives, and shared content visible at a glance.

Device Detail — Files

Browsing files directly on a remote device. The interface communicates where content lives rather than presenting an abstracted cloud container.

Team Folders

Shared folders organized around teams, not cloud storage buckets. Members see the devices and folders relevant to their work.

Different users interacted with Nokl in fundamentally different ways. Administrators managed organizations and policies, team managers coordinated collaboration, members focused on daily work, and guests accessed only specific shared content.

Rather than relying only on permissions, the interface treated visibility itself as part of the UX strategy. Users were intentionally exposed only to the workflows relevant to their role.

This reduced cognitive load significantly. Members did not need to navigate administrative infrastructure, and guest users could interact with shared files without understanding the surrounding system at all.

The result was a platform capable of supporting complex organizational structures while still feeling lightweight and approachable to individual users.

Role-based experiences

←1 / 4→

Org Admin

Organization-wide management: members, teams, device access, and policies. Full system visibility with the controls to match.

Team Manager

Team-scoped view for managing shared folders, member access, and collaboration without exposing organization-level infrastructure.

Member Dashboard

The daily workspace for a member — devices they can access, folders shared with them, and recent activity. No administrative noise.

Guest Share View

A guest accessing shared content without an account. The interface presents only what was shared, with no surrounding system context.

Traditional collaboration workflows often rely on uploading, syncing, and duplicating content between cloud systems. Nokl explored a more direct sharing model based on peer-to-peer access.

Users could share folders privately with individuals or teams, generate public links for guests, or expose content through mounted remote drives without uploading everything into centralized storage first.

Guest access became especially important. Shared links were intentionally lightweight and accessible without requiring account creation or infrastructure knowledge from recipients.

The interface also needed to communicate system states clearly. Device availability, offline status, cached content, and "Always Available" behavior were treated as explicit UX concepts rather than hidden implementation details. This reduced ambiguity and made collaboration workflows feel more trustworthy across devices and teams.

Sharing

←1 / 4→

Share Dialog

A focused sharing surface for inviting individuals, teams, or generating public links — without uploading content to centralized storage.

Team Sharing

Sharing directly with a team grants access to all current and future members, keeping permissions in sync without manual updates.

Public Link

Public links expose content to anyone with the URL. The interface makes scope, expiry, and revocation immediately clear.

Guest Access

Recipients access shared content without an account. The experience is intentionally lightweight — no signup, no infrastructure knowledge required.

Sharing management

←1 / 4→

Shared by Me

A clear record of everything the user has shared — with whom, under what conditions, and whether it is still active.

Shared with Me

All content shared with the user across teams and individuals, with device and availability status surfaced inline.

Public Links

Manage all public links in one place — view access scope, revoke links, and audit sharing history without hunting through folders.

Offline vs Cached

Offline and cached are treated as intentionally different states. Offline means the device is unreachable. Cached means content is available locally.

A major part of the redesign focused on reducing the intimidation often associated with infrastructure-oriented products without oversimplifying how the system actually behaved.

Onboarding flows were designed around user intent rather than technical setup sequences. Different entry paths helped guide people toward device access, sharing, or team collaboration without overwhelming them with infrastructure concepts upfront.

Language itself became part of the UX strategy. Messaging aimed to remain technically credible without becoming overloaded with jargon or implementation terminology.

System states such as offline devices, unavailable folders, or cached content were intentionally communicated in explicit and understandable ways to build trust and reduce ambiguity.

Onboarding

←1 / 4→

Welcome

Onboarding starts with a clear value proposition — not a setup checklist. Users understand what Nokl enables before being asked to configure anything.

Install

App installation is framed as enabling access, not as a technical requirement. The interface communicates what happens next, not what needs to be done.

Connected

The first connection moment is designed to feel like progress, not configuration. The device appears in the system and is immediately ready to use.

Done

Onboarding ends by pointing users toward their first real action — not a dashboard of empty states and prompts.

System states

←1 / 3→

Empty State

Empty states guide users toward their next action instead of presenting blank surfaces with generic placeholders.

Offline Warning

When a device goes offline, the interface communicates what is still accessible, what requires reconnection, and why.

Device Unavailable

A device that is unavailable is shown in context — the user understands the state without leaving their current workflow.

The work extended beyond application screens into onboarding, product communication, support, and positioning consistency across the broader ecosystem.

Marketing pages, onboarding flows, technical explanations, and support content were designed to reinforce the same mental models established inside the product itself.

Different parts of the ecosystem emphasized different goals. Some pages focused on technical credibility, while others focused on use cases, onboarding simplicity, or helping users understand where Nokl fit into their workflows.

The project established a scalable UX direction for how Nokl could evolve from a utility-oriented tool into a broader collaboration platform centered around direct device access and role-based workflows.

The redesign exploration clarified product positioning, introduced a more structured interface architecture, and explored collaboration patterns better aligned with modern teams and multi-device environments.

It also created a foundation for future onboarding, sharing, and organizational workflows while helping define a more approachable product identity around technically complex infrastructure concepts.