For years, we’ve been looking at one type of consumer of our work: the end user - the one for whom we are developing our apps. Lately, the Android community has been growing and, most of all, it’s been collaborating! Code, blog posts and talks - for all these types of content that we are producing, the consumer is us. All of us! From code reviewers, team-mates, other developers that use our work, to the future “you” that needs to maintain the code. For the first type of consumers we have specialized roles that advocate for them – like product owners and UI/UX designers – but for the second type, we don’t. As developers, it ends up being our responsibility to look at the content we are producing from the perspective of the target audience. Let’s take a look at the “content - consumer” relationship in the same way we look at the “app - end-user” relationship. Let’s see what kind of questions we need to answer to improve the quality of our work, satisfy our content consumers and, in turn, improve the end-user experience.
Florina is working as an Android Developer Advocate at Google, helping developers architect clean, testable apps using the Architecture Components libraries. She has been working with Android for 8 years, previous work covering news at upday, payment solutions at payleven and navigation services at Garmin.