Instead of having a scan/stopScan - maybe just scan and automatic stop on dispose.
Ditto for connection/disconnection.
Not sure if this would make for a better or worse API. Explicit is nice, but it's also awkward in a Reactive context because should the stopScan return a Completable? Observable? etc..
Same with Connectables...
Should connection state be monitored using a connectivity() -> Observable api, or should connection state be based on the act of connection, or both? The former is more usable, while expanding the API surface, the second has the "fault" that an explicit connection is always required to even find out the connectivity state.
Instead of having a scan/stopScan - maybe just scan and automatic stop on dispose.
Ditto for connection/disconnection.
Not sure if this would make for a better or worse API. Explicit is nice, but it's also awkward in a Reactive context because should the stopScan return a Completable? Observable? etc..
Same with Connectables...
Should connection state be monitored using a
connectivity() -> Observableapi, or should connection state be based on the act of connection, or both? The former is more usable, while expanding the API surface, the second has the "fault" that an explicit connection is always required to even find out the connectivity state.