If you search "bilingual caregiver app," what you get back is mostly two things. The top results are agency software — products like CareSmartz360 that home-care agencies use to manage a multilingual workforce, with the caregiver-facing UI offered in seven or eight languages so the agency can recruit and schedule across a wider labor pool. Underneath the agency tools, you find job listings for bilingual home aides.
What you don't find, scrolling page after page, is an app built for the family. The Korean-American household where Mom reads Korean and the kids read English. The Vietnamese-American family where Dad's discharge summary came in English and his children are bilingual but tired. The Mexican-American family in Texas where Abuela's after-visit notes are in English but the conversation at the kitchen table is in Spanish. These families exist by the millions. The category of consumer-facing caregiving software has, with rare exception, not built for them.
This essay is about why the gap exists, what it costs, and what closing it would actually look like.
The gap, in numbers
The U.S. Census counts more than 67 million Americans who speak a language other than English at home. About 25 million speak English less than "very well." A meaningful share of those people are aging — and a meaningful share of their adult children read English as their primary language. The intersection of those two groups is the family in scope here: the immigrant parent whose first language is not English, and the U.S.-raised adult child who is doing the coordinating.
The exact size of that intersection depends on how you count, but a useful order of magnitude is several million American families. The largest groups, by language spoken at home, are Spanish (over 41 million speakers), Chinese (~3.5 million), Tagalog (~1.8 million), Vietnamese (~1.5 million), Korean (~1.1 million), and a long tail. Aging caregivers in these communities are not edge cases. They are a substantial share of the people for whom American family caregiving is hardest.
What the category has built for these families is, broadly, nothing. Family-caregiving products have launched in English, added a Spanish surface eventually if at all, and treated Asian and other immigrant languages as a "later" line item that doesn't move because the product wasn't designed for bilingual use from the start.
Why the gap exists
Two reasons. The first is straightforward: bilingual is expensive. Building a product that ships in seven languages from day one — with real translation rather than machine output on the institutional copy, ongoing translation maintenance as features ship, and side-by-side bilingual presentation inside the workspace itself — costs roughly three or four times what an English-only equivalent costs. The category's earliest products were funded by venture investors optimizing for time-to-market in the English-speaking middle of the U.S. consumer market. Bilingual got cut.
The second reason is structural. The market that did fund bilingual in caregiving wasn't the family-side market — it was the agency-side market, where the buyer (the home-care agency) has a direct financial reason to recruit bilingual workers and a regulatory reason to provide multilingual training materials. CareSmartz360 and its peers exist because their buyers, the agencies, asked for them. Family-side products don't have that pressure. The family-side buyer (the adult daughter, mostly) has been asking for it — anyone who's ever had to explain a Cantonese-speaking mother's medication changes over the phone has been asking for it — but the request hasn't translated into the kind of buyer concentration that funds a product.
So the gap reflects which buyer the category got built for, not whether the underlying need exists.
What "bilingual caregiver app" should mean
When the audience is the family, the product shape changes. A bilingual caregiver app for the family is not a worker-facing app in seven languages. It is a shared workspace where the patient and the caregivers can each read in the language they actually read, on the same record.
Four design choices distinguish a real bilingual family workspace from a monolingual one with a translation widget bolted on:
1. Side-by-side, not toggle. When the family writes a note in English about a new medication, the parent should see the English original and a translation in their language, in the same view, on the same screen. A toggle that switches the whole UI from English to Korean asks the parent to lose context every time she wants to verify the source. Side-by-side preserves the English as the artifact of record and uses the translation as a bridge — which is also the responsible posture given what current research says about AI medical interpretation.
2. Languages chosen for the actual immigrant-caregiving market, not the European tourist market. Most multilingual products ship Spanish, French, German, Italian — the languages a European traveler would expect. The American immigrant-caregiving market is Spanish, simplified Chinese, Korean, Japanese, Vietnamese, and Tagalog. Different list. Kintaria ships all six plus English.
3. Per-locale resource directories, not just translated UI. A Korean-American family in Los Angeles dealing with a dementia diagnosis needs in-language resources — Korean-speaking elder-law attorneys, Korean-language support groups, hospitals with Korean interpreters on staff. A translated app that surfaces the same English resource list to a Korean-language user is still functionally English-only. The per-locale resources pages for Spanish, Chinese, Korean, Japanese, and others are a deliberate move against this — different resources per locale, curated for the community.
4. The product treats the patient as a participant, not the subject of records. This is the test we wrote about earlier this week. If the bilingual feature is built so that the bilingual daughter can translate notes to her mother, but the mother still can't read the workspace directly — the family is still operating in one language, just with extra steps. The point of building bilingual into the workspace is that the parent reads it herself, on her own phone, in her own time.
The honest comparison
The agency tools — CareSmartz360 and its peers — are well-built products. They do what they were designed to do: help a home-care agency manage a multilingual workforce. If you are a home-care agency, they may be exactly what you need.
What they are not is a bilingual caregiver app for the family. The agency tools assume the worker (a paid caregiver employed by the agency) is the user; the family is largely outside the loop. They are also, in most cases, not designed for the patient to read directly — the worker translates, the patient receives.
The family-side bilingual caregiver app — built for the daughter coordinating from across the country, the parent who reads in Mandarin at home, and the siblings who don't all read the same language — is a different category. Until very recently, that category was empty. We built Kintaria for it.
There is one piece of this that is bigger than any single product: the federal policy environment is moving toward making language access a permanent legal requirement rather than a discretionary standard. Rep. Grace Meng's Language Access for All Act, introduced in January 2026, would codify language access for federally funded programs and add AI-oversight provisions for medical interpretation. If it passes in any form, the default for healthcare-adjacent software in the U.S. will shift — and "we'll add languages later" stops being a defensible product position.
The gap we have been describing is, in other words, going to close. The question is whether it closes because the category of family-caregiving software builds for the families that already exist, or because federal law compels it. We would rather it close the first way.