Conceptual Yaze Media product atlas with connected islands representing practical software workflows

Case study 05 / Windows desktop + Android

Neardock

A focused ink-and-orange sharing workspace built on the established LocalSend foundation.

Conceptual artwork / product evidence follows

YazeKT brand avatar with a glowing Y visor

Neardock product direction and interface by Kirsten Trimaley, preserving upstream protocol and contributor credit.

I use AI to explore and accelerate, but I own the product decisions, the verification, and the responsibility for what ships.

Platforms
Windows x64 + Android
Windows binaries are unsigned
Sharing boundary
Same local network

The real product

Built to be used,
not just viewed.

Share files, messages and manually selected clipboard text between nearby Windows and Android devices on the same local network.

Complete application frame · source aspect ratio preserved · privacy-safe data

Neardock Send workspace showing a nearby device, file selection and navigation for Receive, Chat and Clipboard
Neardock interface evidence

What I changed

  • Organized Send, Receive, Chat, Clipboard and Settings into a consistent Windows and Android product interface.
  • Added local conversations, explicit clipboard handoffs, device trust controls and documented release packages.

Boundaries first

  • Devices need a shared local network; cross-network internet sharing is not enabled.
  • Windows x64 packages are unsigned; Windows ARM64 is unavailable in this release.

Decisions

  • Keep the established LocalSend transfer foundation and make consent, destinations and cancellation visible.
  • Use manual clipboard actions rather than implying continuous clipboard synchronization.

Proof of work

  • The 1.0.0 release provides a Windows x64 installer and portable ZIP, plus Android APKs and checksums.
  • Public release notes distinguish verified builds from remaining interoperability and device-testing work.

Foundation and attribution: Based on LocalSend by Tien Do Nam and contributors. Apache 2.0 code; Neardock brand assets have separate terms. Upstream notices and contributor credit are retained.

What comes next

Use the product website for installation steps, supported downloads and local-network troubleshooting; contact me to discuss a related workflow project.

Discuss a project