Skip to content

Commit fedd37a

Browse files
authored
Update README.md
1 parent c34b275 commit fedd37a

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,14 @@ Screencasts from the example app included in this repository:
2222
![compose-upload](https://user-images.githubusercontent.com/16792495/28752871-de82540e-7529-11e7-9037-de86b8f0ca27.gif)
2323
![upload](https://user-images.githubusercontent.com/16792495/28752872-de9a8894-7529-11e7-823a-e51eda59f5b7.gif)
2424

25+
At the core of the library there is a `Service` which handles multiple concurrent upload tasks in the background. It publishes broadcast intents to notify status. This way the logic is completely decoupled from the UI. You are safe launching upload requests from your fragments, activities and services without worrying about locking the thread in which you are. [Check the wiki](https://github.com/gotev/android-upload-service/wiki) to learn how you can use it in your App.
26+
27+
You are also safe if your app is put in the background. All the uploads will continue to be executed also when your device is idle.
28+
29+
Bear in mind that if you kill your app, the service gets killed as well, as it's attached to your app's process and all the currently running uploads will be terminated abruptly.
30+
2531
## Features <a name="features"></a>
26-
* Android 5.0 (API 21) to Android 12 (API 31) support
32+
* Android 5.0 (API 21) to Android 12 (API 31) support. Beware you cannot start uploads while your app is the background on Android 12 due to recent Service limitations
2733
* 100% Kotlin and fully interoperable with Java
2834
* upload files to a server with `FTP`, `HTTP multipart/form-data` or `Binary` data requests
2935
* upload requests can be serialized and executed later
@@ -38,12 +44,6 @@ Screencasts from the example app included in this repository:
3844
* Possibility to implement your own notification handler
3945
* Lifecycle-Aware RequestObserver to monitor your uploads
4046

41-
At the core of the library there is a `Service` which handles multiple concurrent upload tasks in the background. It publishes broadcast intents to notify status. This way the logic is completely decoupled from the UI. You are safe launching upload requests from your fragments, activities and services without worrying about locking the thread in which you are. [Check the wiki](https://github.com/gotev/android-upload-service/wiki) to learn how you can use it in your App.
42-
43-
You are also safe if your app is put in the background. All the uploads will continue to be executed also when your device is idle.
44-
45-
Bear in mind that if you kill your app, the service gets killed as well, as it's attached to your app's process and all the currently running uploads will be terminated abruptly.
46-
4747
## Powered by Android Upload Service <a name="powered"></a>
4848
Apps and libraries powered by this library. To be included in the following list, simply create an issue and provide the app name and a link.
4949

0 commit comments

Comments
 (0)