Inclusive Android Apps #12: The Problem of Holidays Assuming One Calendar
Twelfth issue covers how apps that assume one holiday calendar can exclude people, and what to do instead.
I grew up in a culture deeply shaped by Christianity. In Finland, Lutheran ethics and teachings are woven into everyday life, and I started to notice how much of Western culture is built around the Christian calendar only when I was older. So this issue is written from that perspective. I'm no expert on other calendars, but I want to raise some checkpoints for people who, like me, might not have noticed. The last solution is the most important one.
The Problem of Holidays Assuming One Calendar
Many apps assume everyone follows the same calendar. Christmas and Easter are marked in the calendar view, December gets a festive theme, and notifications wish everyone a merry Christmas. The same kind of assumption shows up in date systems and the working week too, but this issue focuses on the holidays.
If you celebrate those holidays, you probably don’t notice any of this. If you don’t celebrate them, many apps don’t know about the days that matter to you, and there’s often no way to add them. A scheduling app might mark Christmas and Easter as days off, but have no way to mark Eid or Diwali.
Having Christian holidays in an app isn’t automatically a problem. If your users live in a market where Christmas is the main celebration, a Christmas theme can make sense. The problem is when the same assumptions are used in other markets without changes, or when users can’t opt out.
Who This Hurts
- People who don't share holidays from the Christian calendar
- People who don't celebrate holidays at all
- Users of non-Gregorian calendars
- Religious and cultural minorities living in a country with a different majority culture
Why Developers (or Designers) Do This
When you grow up with a set of holidays, they don't feel like a cultural choice. They just feel like "the holidays". That's why Christian holidays end up hardcoded into calendars, themes, and notifications without anyone giving a second thought to it. Nobody sat down and decided to exclude people; the assumption was just never questioned because it was never visible. This is especially easy when everyone on the team shares the same background, because no one in the room notices.
The tools don't help either. Sample data often defaults to the Gregorian calendar and Western holidays, so hardcoding is the path of least resistance. And Christmas promotions often work, so there's a business reason to keep them.
The Solution
Check Your Assumptions
Start by finding where your app makes assumptions about time and culture. Look at calendars and date pickers, seasonal themes and promotions, notification copy, scheduling features, and anything that mentions a holiday by name. For each one, ask who decided that, and what it looks like for someone who doesn’t celebrate it, or celebrates something else.
You don’t need to know every calendar to do this. You only need to notice where your app has picked one, and whether the user can change it.
Allow Customizability with Holidays
One common version of this problem is a seasonal theme tied to a month:
val theme = if (LocalDate.now().month == Month.DECEMBER) {
ChristmasTheme
} else {
DefaultTheme
}
Every user gets the same theme, whether they celebrate Christmas or not, and there’s no way to turn it off. A more flexible way is to treat holidays as data, grouped into sets the user can choose from, and let the theme follow the sets they’ve enabled:
data class SpecialDay(
val name: String,
val start: LocalDate,
val end: LocalDate = start,
val theme: AppTheme? = null
)
data class HolidayCalendar(
val id: String,
val name: String,
val days: List<SpecialDay>
)
// Only the calendars the user has enabled
val enabledIds = settingsRepository.getEnabledCalendarIds()
val specialDays = holidayRepository.getAvailableCalendars()
.filter { it.id in enabledIds }
.flatMap { it.days }
val today = LocalDate.now()
val theme = specialDays
.firstOrNull {
it.theme != null &&
!today.isBefore(it.start) &&
!today.isAfter(it.end)
}
?.theme
?: DefaultTheme
Note that holidayRepository, settingsRepository, and AppTheme are placeholders for however your app loads holidays, stores settings, and defines themes.
The user chooses which calendars are enabled in the settings, where each calendar can be a toggle:
@Composable
fun HolidayCalendarRow(
calendar: HolidayCalendar,
enabled: Boolean,
onToggle: (Boolean) -> Unit
) {
Row(
modifier = Modifier
.fillMaxWidth()
.toggleable(
value = enabled,
role = Role.Switch,
onValueChange = onToggle
)
.padding(16.dp),
verticalAlignment = Alignment.CenterVertically,
horizontalArrangement = Arrangement.SpaceBetween
) {
Text(calendar.name)
Switch(checked = enabled, onCheckedChange = null)
}
}
Nothing is hardcoded now, and the user decides which holidays show up. Regional holidays can still be the default, but it’s a visible default they can change. If your app has an onboarding flow, it's a good place to offer the choice, so users don't have to go looking for it in the settings.
A familiar example of letting users choose is how Google Calendar handles holidays. Your country's holidays are added automatically, but you can change that in the settings. You can add or remove the holidays of other countries and regions, and add religious holidays as separate calendars. Each holiday shows up as an all-day event, so each person sees the days that matter to them.
Many holidays follow calendars other than the Gregorian one, so their Gregorian dates change every year. Android's android.icu.util package includes calendars such as IslamicCalendar and ChineseCalendar, which can help when you need to convert dates.
Pay Attention to Language
The words in your app carry assumptions too. Phrases like “Christmas break” or a “Happy Holidays” message that really means Christmas quietly tell some users that the app wasn’t written for them. If you have holiday-specific copy, tie it to the specific day the user has chosen instead of a hardcoded holiday:
<!-- ❌ Don't ❌ -->
<string name="seasonal_banner">Get ready for Christmas!</string>
<!-- ✅ Do ✅ -->
<string name="special_day_reminder">%1$s is coming up on %2$s</string>
Test with People from Different Cultures
This is the most important step, because it’s the one that finds what you can’t see yourself. We can only notice assumptions we already know to look for. Ask people from different cultural and religious backgrounds to go through your dates, themes, and copy, and listen to what they point out. If your team is culturally similar, this may mean asking beta testers or paying for user research with a more varied group. It’s worth the effort, because these problems rarely show up in your support inbox.
Note: Remember that one person can't speak for the whole culture or religion.
Read More
Google Calendar Help: Add or remove holidays on your calendar
The support site explains how users can add regional and religious holidays to their Google Calendar.
android.icu.util API reference
API reference for android.icu.util, which contains different calendars such as BuddhistCalendar, IslamicCalendar, JapaneseCalendar, and EthiopicCalendar, among others.
That's a wrap for Issue #12 of Inclusive Android Apps.
Inclusive Android Apps is taking a short break and will resume next year with new topics!
Thanks for reading!
-Eevis
PS. If you need help with mobile app accessibility or training for your team, I’d love to chat. Reach me at [email protected] or eevis.codes.