How vahdettina/drop_flow works
DropFlow is an Android peer-to-peer file-sharing app. Its documented main flow starts a temporary local server on the Android device; another device connects through a browser using the displayed IP address or QR code, then downloads shared files or uploads files back. The README also advertises Bluetooth sharing. Source excerpts were not provided, so the component mapping follows the file tree and the relationships shown here are limited to README-documented behavior.
Main entry points: EmbeddedTransferServer.kt Local transfer server · MainActivity.kt DropFlow app · SendScreen.kt Send/receive · BluetoothShareUtils.kt Bluetooth sharing
Components 10
App experience
- DropFlow app
dropflow/app/src/main/java/com/example/MainActivity.kt - Send/receive
dropflow/app/src/main/java/com/example/ui/screens/SendScreen.kt - Web share screen
dropflow/app/src/main/java/com/example/ui/screens/WebShareScreen.kt
Transfer runtime
- Local transfer server
dropflow/app/src/main/java/com/example/transfer/EmbeddedTransferServer.kt - Peer discovery
dropflow/app/src/main/java/com/example/transfer/PeerDiscoveryManager.kt - Transfer client
dropflow/app/src/main/java/com/example/transfer/TransferClient.kt - Bluetooth sharing
dropflow/app/src/main/java/com/example/util/BluetoothShareUtils.kt
Peer access
- Browser peer
- Shared files
dropflow/app/src/main/java/com/example/util/StorageUtils.kt
Other components
- App user
Connections 9
- App user → DropFlow app: opens
README.md - DropFlow app → Send/receive: starts sharing
README.md - Send/receive → Local transfer server: starts server
README.md - Local transfer server → Browser peer: serves locally
README.md - App user → Browser peer: scans QR or enters IP
README.md - Browser peer → Shared files: downloads
README.md - Browser peer → Local transfer server: uploads to
README.md - App user → Bluetooth sharing: shares by Bluetooth
README.md - App user → Local transfer server: closes app; stops
README.md