Snapdrop

Snapdrop: local file sharing in your browser - inspired by Apple's Airdrop.

Snapdrop (Version 2) is built with the following awesome technologies:

Vanilla HTML5 / ES6 / CSS3
Progressive Web App
WebRTC
WebSockets fallback (iDevices don't support WebRTC)
NodeJS
Material Design

Frequently Asked Questions

Instructions

Video Instructions (Big thanks to TheiTeckHq)
idownloadblog
thenextweb
winboard
免費資源網路社群

What about the connection? Is it a P2P-connection directly from device to device or is there any third-party-server?

It uses a P2P connection if WebRTC is supported by the browser. (WebRTC needs a Signaling Server, but it is only used to establish a connection and is not involved in the file transfer).

If WebRTC isn’t supported (Safari, IE) it uses a Web Sockets fallback for the file transfer. The server connects the clients with each other.

What about privacy? Will files be saved on third-party-servers?

None of your files are ever saved on any server. Snapdrop doesn't even use a database. If you are curious have a look at the Server.

Is SnapDrop a fork of ShareDrop?

No. ShareDrop is built with Ember. Snapdrop is built with vanilla ES6. I wanted to play around with Progressive Web Apps and then I got the idea of a local file sharing app. By doing research on this idea I found and analysed ShareDrop. I liked it and thought about how to improve it. ShareDrop uses WebRTC only and isn't compatible with Safari browsers. Snapdrop uses a Websocket fallback and some hacks to make Snapdrop work due to the download restrictions on iDevices.

Snapdrop is awesome! How can I support it?

File bugs, give feedback, submit suggestions
Share Snapdrop on your social media.
Buy me a cup of coffee
Fix bugs and make a pull request.
Do security analysis and suggestions

Local Development

Install docker with docker-compose.

    git clone git@github.com:RobinLinus/snapdrop.git
    cd snapdrop
    docker-compose up

Now point your browser to http://localhost:8080.

Deployment Notes

The client expects the server at http(s)://your.domain/server.

When serving the node server behind a proxy the X-Forwarded-For header has to be set by the proxy. Otherwise all clients that are served by the proxy will be mutually visible.

By default the server listens on port 3000.

For an nginx configuration example see nginx/default.conf.

Licences

Thanks to Mark DiAngelo for the Blop Sound

no4 / snapdrop