|
vor 9 Jahren | |
---|---|---|
app | vor 9 Jahren | |
docs | vor 9 Jahren | |
server | vor 9 Jahren | |
tasks | vor 9 Jahren | |
.bowerrc | vor 9 Jahren | |
.editorconfig | vor 9 Jahren | |
.gitattributes | vor 9 Jahren | |
.gitignore | vor 9 Jahren | |
.jscsrc | vor 9 Jahren | |
.jshintrc | vor 9 Jahren | |
.travis.yml | vor 9 Jahren | |
CONTRIBUTING.md | vor 9 Jahren | |
LICENSE.md | vor 9 Jahren | |
README.md | vor 9 Jahren | |
bower.json | vor 9 Jahren | |
gulpfile.js | vor 9 Jahren | |
index.js | vor 9 Jahren | |
package.json | vor 9 Jahren | |
travis-runner.sh | vor 9 Jahren | |
wct.conf.js | vor 9 Jahren |
Snapdrop is inspired by Apple's Airdrop, but is a Progressive Web App built with Polymer and Web RTC.
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 a stream.
None of your files are ever saved on any server. Snapdrop doesn't even use cookies or a database. If you are curious have a look at the Server But it does use Google Analytics.
No. ShareDrop is built with ember. Snapdrop is built with Polymer. I wanted to play around with Progressive Web Apps and then I got the idea to clone Apple’s Airdrop. 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.
npm install & bower install
gulp serve
node index.js