I was honored to talk with Robby Russell (@robbyrussell) about technical leadership and maintainable code. It was my very first podcast. Hope the content is helpful: Magda Miu: Building a Technical Leadership Career Around Teaching.
CameraX provides an easy to use api and the purpose of this article is to define a complete guide with different kind of resources about how this api could be easily integrated in our Android apps.
Image analysis and applying extensions when pictures are taken are use cases often accessed by the users. By using CameraX API we are able to implement them in a very simple way. If you want to learn more check the code samples and the theory behind these features in the current article.
I work as a Technical Leader since 2016. During these years the most important lesson I learned is that as a servant leader my main focus should be my team because everything it’s about them, it’s not about me. Actually, my main responsibility is to set up my team members for success.
The success of a product is a team effort and my role is to build, train, and lead engineers. Awesome teams build awesome products. In order to achieve this objective, it’s necessary to combine tech skills with people skills.
In my previous article about CameraX I covered the challenges we are facing by using oldest Camera APIs and what are the advantages of using this new API.
As an Android developer I learned that when I develop an app it is not about me, it is about the users who will interact with the app I build. The quality of the code and also the involvement to deliver high-quality features are reflected in the experience of our users.
As a team leader, I understood better than launching an app is a team effort and our way to collaborate, our shared vision will have an important impact on the success of a product.
In this talk, I’m going to cover some of the lessons I learned along the way and I will present a road-map that in my opinion should be crossed by each Android developer. We will talk about Kotlin, how to write Clean Code in Kotlin, guidelines in building the app architecture, and how to create an achievable learning plan.
As humans, we have emotions and feelings and one of the best ways to capture our emotions is to take pictures.
Some of our greatest experiences are actually captured in pictures. For sure each one of us have pictures from birthday parties, holidays, travels, conferences. We also like capturing feelings like happiness or reactions when bad surprises happen. And, in the latest years, we discovered that we love taking selfies.
Last year, Google invited developers to submit their ideas for the Android Developer Challenge, focused on “Helpful Innovation, powered by on-device machine learning.” They picked 10 winners, and have been working with them since then to help bring their apps to life. #AndroidDevChallenge
Generics means we use a class or an implementation in a very generic manner. For example the interface List allows us for code reuse. We are able to create a list of Strings, of integer values and we will have the same operations even if we have different types. So the list wraps a common functionality for each implementation.
Kotlin allows you to use parameters for methods and attributes, composing what is known as parameterized classes.
I recently presented this talk at mDevCamp – Online edition. More than that I was part of a Virtual 3D world. Great event, awesome organizers and really interesting questions from the audience.
This talk contains the answers for the next questions:
