Last week was the week of Google I/O 2019. It was a particularly exciting I/O for me, as it was the first time Google has talked publicly about Jetpack Compose, the project I was hired to work on in February of 2018. Compose is an ambitious multi-team effort to reimagine Android’s UI Toolkit more than 10 years after the Android Platform launched with the original UI Toolkit.
Chips are compact components that display discrete information. Given the simplicity of their makeup and small size, they are flexible enough to be used for entering information, filtering content, selection and triggering actions. Chips should be grouped accordingly and are rarely used as standalone elements.
In my last two posts we looked at how a Service works and behaves depending on how you use it. You can either bind or start it, and the actual implementation in the Service also affects its lifecycle and wether it will be restarted by the system after being killed.
CameraX is an Android Jetpack library that was built with the intent to make camera development easier, which until now has been quite painful. In contrast with the fine grained control camera2's API offered, CameraX (which uses the Camera2 API under the hood) aims to strike a balance between abstracting away the difficult bits of managing the camera while allowing flexibility and customization.
This class provides methods to play DTMF tones (ITU-T Recommendation Q.23), call supervisory tones (3GPP TS 22.001, CEPT) and proprietary tones (3GPP TS 31.111). Depending on call state and routing options, tones are mixed to the downlink audio or output to the speaker phone or headset. This API is not for generating tones over the uplink audio path.