This framework is, essentially, composed of 2 parts:
- Toasting: posting messages/views and handling queues
- Connectivity: handling internet connection/disconnection events and showing a toast when a connection is lost.
The first part is straightforward in purpose, fairly simple, and works well as an independent feature.
The second is challenging, slightly hacky, and highly dependent on the visible app screen, which is not ideal for a framework.
The second part should be separated from the first, so frameworks only bring it in if they need it.
This framework is, essentially, composed of 2 parts:
The first part is straightforward in purpose, fairly simple, and works well as an independent feature.
The second is challenging, slightly hacky, and highly dependent on the visible app screen, which is not ideal for a framework.
The second part should be separated from the first, so frameworks only bring it in if they need it.