In the early days of Android development, it was an exhaustive task to cover all tags in the document and provide a structured hierarchy for the rest of the project business logic. Nowadays, we are presented with various libraries to parse an XML document– does it mean we can do it more efficiently?
I think that animations are important for the usability of your app; they explain state changes or transitions, establish a spatial model or can direct attention. They help users understand and navigate our apps.
In this blog post, we will cover the basic principles behind the CameraX Jetpack Library in addition to a few ways in which the library has changed since its announcement at Google I/O 2019. For up-to-date resources, check out the documentation, review the official sample, and join our online developer community.
For as long as Android development has been around, we’ve been using setContentView to inflate layouts in our Activity classes. And since the introduction of Fragments, we’ve had to override onCreateView and use a layout inflater to get our view from a layout ID. They’re so common to write that it’s easy to not think about them much. At the same time, they feel a bit like boilerplate, right? Wouldn’t it be nice if there was a simpler way to inflate our views?