Eevis Blog

If you have forms in your app that collect user information, autofill is one of the easiest accessibility wins you can add.

Last summer, I wrote a blog post about focus management with Compose.

This is a submission for the 2026 WeCoded Challenge: Echoes of Experience It’s the time of the year when I feel most conflicted.

In my previous blog post, Beyond Font Scaling: Large Content Viewer with Compose, I explained how to build a large content viewer from iOS using Jetpack Compose.

If you’ve worked with accessibility issues and have a bottom bar with multiple items, you’ve probably come across a problem with larger font sizes, where it’s impossible to scale the bottom navigation bar texts properly with larger font sizes.

It’s that time of the year again!

This was originally sent as Issue #1 of my newsletter.

One thing I'm super excited about at the end of this year is a newsletter I'm launching: Inclusive Android Apps.

Over the past six months or so, I've been writing a series of blog posts in which I've generated an app using the same prompt with different AI tools, and then tested the outcome with various assistive technologies and accessibility settings.

While testing Android apps for accessibility, one of the biggest problems I’ve encountered are with larger font sizes.

This is a living document, and I try to update it when I learn or realize something new.

Lately, I've been learning about Wear OS development.

During the spring and summer, I've been testing different AI tools for their ability to generate accessible Android user interfaces.

Sometimes I encounter this weird idea that developers don't need accessibility at all.

I've seen multiple questions in various Slack communities, Stack Overflow, and other places related to focus on Android and how it doesn't behave as expected.

I've been testing the accessibility of Android code created by different AI tools, and this time, it's time to test Cursor.

I'm continuing my tests with AI-generated Android code and how accessible these generated apps are.

Imagine that you're in an unfamiliar location.

The AI is here, and we all are going to lose our jobs.

This is a submission for the WeCoded Challenge: Echoes of Experience Earth has traveled around the Sun, and it's time for the We Coded again!

I have this "Remove animations"-setting turned on on my phone because different kinds of movement make me feel physically sick.

Valentine's Day is approaching, and while I prefer the Finnish version ("Friend's Day"), I was inspired to do some creative coding in the holiday theme.

The first month of 2025 and its 247 days are behind us.

One thing that has continued to amaze me with building my Compose Multiplatform app is how easily everything has worked with Canvas.

This was originally written for Dev.to's New Year writing challenge. 2025 has started, and while I'm actually skeptical of anything good happening (just look at the world burning), I decided to give some thought to what I hope to accomplish this year.

It's time for some yearly reflections again.

While working on my master's thesis and the Android Accessibility Checklist, one of the answers to my survey mentioned an accessibility setting called time to take action.

One part of creating accessible Android apps is to provide alternative navigation options.

I've continued my journey with Compose and Canvas!

I finally had the time to dive into Compose Multiplatform - and this was also my first experience with Kotlin Multiplatform.

In my previous blog post, Paint the Stars — Drawing with Compose and Canvas, I shared how I wanted to be better with Canvas and Compose and created an illustration with planets and stars.

I've always struggled with drawing in Canvas, not just with Compose's Canvas but with any technology.

In Droidcon Berlin, I gave a talk titled "Is This App Accessible?

If your gender matches the one that was assigned to you at birth, you probably don't notice flaws in application design that enforce the gender binary.

I'm studying for my second master's degree (for fun) and finished with my thesis in the spring.

A couple of weeks ago, I published a blog post Stacked Cards Layout With Compose - And Cats.

Yes, your app should work in both portrait and landscape modes - unless locked orientation is essential for functionality, like in a piano app.

I was writing a completely different blog post about playing around with Glance and app widgets, and I needed an example app.

I wrote most of this blog post in the spring, a bit after my burnout sickness leave.

It's Pride month, y'all!

When writing tests for your app, you should also consider testing for accessibility-related things.

I'm continuing the theme of personalizing accessibility, which I've started with my two posts.

As mentioned in my previous blog post, Personalizing Accessibility with Settings, accessibility for the broadest group of users often requires some personalization.

When users have different, even conflicting, needs for access, what should you do?

Now that Android Studio Iguana is out and stable, I wanted to write about one feature it provides and I'm excited about: Accessibility checks with Compose previews.

As #WeCoded is a month-long this year, I'll post a couple of blog posts during this month.

You might have heard that your app should have a dark theme available.

It's time for Dev's annual We Coded campaign again, and it's the fifth time I'm participating.

When I talk about accessibility with Android developers, I often hear that some easy-to-use tests should automatically catch every possible accessibility issue.

Discussions about accessibility, especially in software development, often center around screen reader accessibility.