Android, since the early versions, has offered users the flexibility to change WiFi via Settings application. The settings application has been a part of the system image and is just like any other application. It needs to be started, resumed for the user to try changing the WiFi settings like connecting to a different network etc.
This meant that developer applications using WiFi functionality had to be paused before the user could change the WiFi settings. Few applications tend to have custom logic and assume that the network can't change before the activity is paused. However, a recent version of Lollipop had a feature where in users could change the WiFi and Bluetooth settings from the expanded status bar window. The UI corresponding to this functionality is hosted as a part of a separate non-application window and it doesn't behave like an application. Expanding the status bar doesn't pause the foreground application. This basically leads to a possibility that the WiFi settings could change while the application is in active and foreground state.
This meant that developer applications using WiFi functionality had to be paused before the user could change the WiFi settings. Few applications tend to have custom logic and assume that the network can't change before the activity is paused. However, a recent version of Lollipop had a feature where in users could change the WiFi and Bluetooth settings from the expanded status bar window. The UI corresponding to this functionality is hosted as a part of a separate non-application window and it doesn't behave like an application. Expanding the status bar doesn't pause the foreground application. This basically leads to a possibility that the WiFi settings could change while the application is in active and foreground state.
No comments:
Post a Comment