Why I'm starting a Newsletter About Inclusive Android Apps

One thing I'm super excited about at the end of this year is a newsletter I'm launching: Inclusive Android Apps. It's a monthly newsletter about making Android apps more inclusive, and it covers accessibility, LGBTQ+ inclusion, support for different cultures and languages, privacy and safety for marginalized users, and more.

In this post, I'm explaining why I'm starting it and what you can expect.

Why Inclusive Android Apps?

The short answer is that I'm starting the newsletter because I'd love to read it, and there's nothing like it around.

The longer answer is that these topics matter to me. Accessibility is a big part of my life, as you might know if you've read my blog posts, seen me speak at events, or followed me on social media. I'm also queer, and many of the issues I'm discussing are from what I've either experienced or witnessed. However, I'm not an expert on everything, and this is also me learning in public.

And I think that now, more than ever, it's important to raise these issues and talk about them. In this time when marginalized communities are under increasing political, social, and digital attack, building inclusive technology is an act of resistance. And you know, every accessible button, every inclusive form, every thoughtful design choice says: you belong here. This newsletter is about making that concrete.

What to Expect from Inclusive Android Apps?

Inclusive Android Apps will cover one inclusion problem each month. The structure of each issue is the following:

The Problem

The first section explains the problem the newsletter issue covers, giving examples of what happens and describing why it's a problem. Depending on the problem, it might be more about code or about a design pattern.

Who the Problem Hurts

Next, each issue has a list of user groups affected by the problem. For example, when buttons break at large text sizes, it affects people with low vision, elderly users, and anyone who has customized their text settings.

Some of these might be obvious, but not always - when I've been writing these issues and doing research, even I've been surprised by the number of different user groups affected by some of the problems.

Why Developers Do It

One of the most interesting parts of writing the issues has been exploring and documenting the reasons why the problem described in the newsletter occurs. Sometimes it's about not knowing specific solutions because there isn't much material out there, and sometimes it's about the biases we humans have.

I wanted to spell these things out, not to blame anyone, but to illustrate why something happens. The first step to combating biases and knowledge gaps is to recognize them; only then can they be addressed.

The Solution

Each issue provides actionable solutions: code examples, design patterns, or practical changes you can implement immediately.

Of course, because of the format (newsletter), it won't cover all possible solutions, just provide one (or a couple) suggestions to solve the problem. But as the newsletter explains the problem in detail, it will also give you some ideas to consider when solving the issue if the provided solution doesn't work for you.

Learn More

Finally, the newsletter will include links to learn more about the topic or about something recent related to the newsletter's subject. Each link is curated, and I will write an explanation of why I selected it.

Subscribe to Inclusive Android Apps

If you want to subscribe to the newsletter, here's the link:

Subscribe to Inclusive Android Apps

The first issue will appear in your inbox on December 9th, 2025! It will cover Rows breaking with larger texts, and a solution for how to fix that problem. The newsletter issues after that will discuss problems with forms that ask for gender and how using color alone to communicate information can be a serious accessibility issue.