Taikutsu Lyrz (Salim Noor)
LanDrop logo
LanDrop

File transfer app · PROJECT BREAKDOWN

Making local sharing feel simple.

LanDrop is my file-sharing app for Windows and Android. I built a clear, local workflow for moving files and folders between devices, without cloud accounts or shared-folder setup.

PLATFORM
Windows · Android
STATUS
Available · v0.1.0
BUILT BY
Taikutsu Lyrz (Salim Noor)

The idea
behind the build.

Moving a folder between a phone and a PC can involve accounts, uploads, or shared-folder setup before the actual transfer starts. LanDrop makes the local network the starting point: discover a device, choose what to send, and let the receiver decide. The interface keeps the network machinery behind a familiar send-and-receive workflow.

WHO IT'S FOR
People moving files between a Windows PC and an Android phone
THE FOCUS
Direct local transfers, clear receiving controls, and native experiences on both devices
01

Direct from disk

Files and folders stream with manifests instead of being zipped or duplicated before sending. Parallel workers help with collections of small files.

02

Discovery with a fallback

UDP broadcast finds nearby devices. Manual IP entry remains available, and Windows prefers Ethernet when choosing an adapter.

03

Receiving is a choice

Manual acceptance, optional pair codes, trusted devices, and Quick Save modes make incoming transfers an explicit part of the experience.

How the pieces
fit together.

Windows & Android · Local networking · Transfer engine · Native interfaces

The core parts of the project, and the responsibility of each.

PART 01

Windows app

Svelte · Tauri · Rust

A lightweight desktop interface backed by discovery, transfer control, and Windows network integration.

PART 02

The transfer layer

Discovery · Manifests · Streaming

Find a peer, describe the selection, stream from disk, and expose progress, speed, pause, resume, and cancellation.

PART 03

Android app

Kotlin · Compose Material 3

A native client with persistent save folders, categorized received files, and a QR-based Wi-Fi Direct flow.

The workflow

  1. Discover a peer

  2. Select files or folders

  3. Accept on the receiver

  4. Track the transfer

The decisions
in the details.

The features, boundaries, and implementation choices that shape the project.

A readable transfer state

Progress, speed, history, and interruption controls give the user feedback before, during, and after a transfer.

Two platform personalities

The Windows app uses a Svelte interface with a Rust backend. Android uses native Kotlin and Material 3, keeping the same workflow while fitting each platform.

Local networks first

Discovery filters loopback and VPN-like interfaces, prefers Ethernet, and includes direct-cable IPv4 setup in Windows settings.

An experimental extension

Remote invites are a separate prototype. Direct internet transfers depend on port forwarding; private overlay networks remain an external dependency.

A closer look.

Real views of LanDrop.

Frameworks & tools.

What the project uses, and where each technology fits.

Rust / TauriSvelteKotlin
Desktop interface
Svelte · TypeScript · Vite

Builds the Windows send, receive, history, and settings interface.

Desktop runtime
Tauri · Rust

Connects the interface to native file operations, discovery, transfer control, and Windows networking.

Transfer engine
Tokio · Serde

Provides asynchronous network and disk work, with structured messages and file manifests.

Android interface
Kotlin · Jetpack Compose · Material 3

Creates the native phone experience, including receiving controls and persistent save-folder choices.

Local connections
UDP discovery · Direct streaming

Finds nearby peers and streams selected files and folders without ZIP staging or cloud storage.

Remote prototype
rustls · Certificate pinning

Protects the separate experimental remote-invite path. This does not describe encryption on the standard LAN path.

Availability
& next steps.

How to explore the project, what it needs to run, and the current release status.

Source availability

The Windows and Android source is public on GitHub, with development setup, build instructions, and two-device validation notes.

App distribution

Version 0.1.0 is available on Google Play. GitHub provides Windows installers, a portable build, the Play-signed Android APK, and a source archive.

Network scope

Local sharing is the core workflow. Remote invites are experimental and depend on reachable devices or a separately configured private overlay network.

View source on GitHub

LanDrop 0.1.0 is available on Google Play and GitHub. The core sharing experience uses your local network; Android also supports a Wi-Fi Direct flow.