Skip to content
ProjectsWritingAboutCVLinks
Hire me
HomeProjectsWritingAboutCVLinks

Have a useful problem?

Let's make the next
thing worth inspecting.

© 2026 Abdul WahidBuilt around evidence, not hype. Privacy
ABDUL WAHID
Home/Projects/NearSend

Case study, Web Engineering

NearSend
Browser-to-browser file transfer

Private nearby file sharing designed to move files between devices without accounts, cloud uploads, or share links.

File-Sharing Web ApplicationWeb Engineering
View source Visit All projects
share-any-file.vercel.appOpen in new tab

Context

The problem

Moving a file from a phone to a laptop often involves sending it through an inbox or uploading it to a third-party service. NearSend explores a direct browser-to-browser path.

My role: Personal project; public repository and live application.

Implementation

How it works

Discover and pair

The signalling layer helps devices find a room and exchange connection details. A QR code can make pairing more convenient.

Establish a peer connection

WebRTC negotiates a data channel between browsers where network conditions permit it.

Transfer chunks

File bytes move through the peer connection rather than being uploaded to a portfolio-owned file store.

Implementation highlights

  • Device discovery and pairing for devices on a shared Wi-Fi network or hotspot
  • WebRTC data channels for direct transfer after signalling
  • QR-based pairing and multi-file transfer interface
  • Signalling service coordinates peers; file transfer is designed to happen peer-to-peer

Evidence

What can be verified

The points below summarize the public repository and owner-provided CV where noted. Read the source for implementation details and the evaluation setup before drawing further conclusions.

AccountNot required

No user account is part of the current flow.

Transfer pathWebRTC

Peer-to-peer after signalling; network topology can affect connectivity.

Server roleSignalling

The server helps establish the connection rather than storing file contents.

Boundaries

Limitations and next questions

  • Direct connectivity depends on browser support, firewall/NAT behaviour, and network conditions; some environments may need additional connectivity infrastructure.
  • Do not send sensitive files over an untrusted device or network without independently evaluating the security model.
  • The application should be tested on the actual device/browser pair before relying on it for a critical transfer.
Evidence-first note: a live demo demonstrates an interface and workflow; it does not by itself validate model quality, security, or real-world impact.

Technical overview

JavaScriptWebRTCWebSocketNode.jsPWAVercel

Project links

Inspect the original implementation and, where available, the live application.

Repository

Live demo

Last content review: 14 October 2026. Details may change as project repositories evolve.

Continue exploring

Related work.

Applied AI

Predictly

A real-estate valuation dashboard that combines market context with transparent, local image-quality signals.

Web Engineering

Inventory Management System

A Java Swing inventory-management interface for products, stock, sales, and suppliers.