How gotev/android-upload-service works
File‐structure analysis
• Top‐level modules:
• uploadservice (core library)
• uploadservice-ftp (FTP plugin)
• uploadservice-okhttp (OkHttp HTTP stack plugin)
• examples (Android demo apps + simple Node.js/PHP servers)
• utils (scripts to test Doze mode)
• Service entrypoint (UploadService, UploadServiceConfig)
• UploadRequest/UploadTask abstractions
• Data objects (UploadInfo, UploadStatus, PersistableData)
• Network layer (HttpStack/HurlStack, OkHttpStack, FTPClientWrapper)
• Protocol handlers (binary, multipart)
• Observers (RequestObserver, TaskObserver, NotificationHandler)
• Persistence interfaces (Persistable)
• Extensions, logger, exceptions, placeholders, scheme handlers.
README insights
• The core is an Android Service that runs outside the UI thread, accepts Intent‐based UploadRequests, and broadcasts progress via Intents.
• UploadRequests can be serialized for later execution.
• Architecture is fully decoupled from UI; uses Notification Center for progress.
• Supports plugins (new protocols, HTTP stacks, custom notification handlers).
Details to capture
• Persistence layer branching off the UploadManager to indicate retry/resume storage.
• NotificationHandler/RequestObserver observers as separate nodes.
• Denote that the Service runs in its own process context attached to the app.
• Sample server endpoints (HTTP upload.php, Node.js index.js) to complete the flow in examples.