DEV Community: iAvatars

The Indian Diaspora: What 18 Million NRIs Carry With Them

iAvatars — Fri, 21 Aug 2026 11:30:00 +0000

There is a particular kind of weight that comes with leaving home. Not the weight of luggage or the weight of a new city. The weight of the people you left behind.

India has the largest diaspora in the world. Over 18 million Indians live outside the country, spread across the United States, Canada, the United Kingdom, Australia, the Gulf, and beyond. Most of them left for opportunity. A better job, a better salary, a better life for their children. And most of them got exactly that.

What nobody prepares you for is what you carry alongside all of it.

The time zones that mean your parents are asleep when your day ends. The festivals that pass without the smell of your mother's cooking. The phone calls that feel shorter than they should because you do not want to talk about how tired you are, and they do not want to worry you with how quiet the house has become.

There is a specific guilt that NRIs carry that does not have a clean name. It is not quite homesickness. It is not quite grief. It is the awareness that the people who built you are growing older in a house you are not in, and that no amount of money transferred or gifts sent quite fills the gap where your presence should be.

The data reflects what most NRIs already know privately. Studies on elderly populations living apart from their children consistently show higher rates of loneliness, cognitive decline, and deteriorating emotional health compared to those with family nearby. This is not an abstract finding. For millions of Indian families separated by geography, it is a daily reality playing out in real time.

Technology has made communication easier. Video calls, voice notes, instant messages, shared photo albums. None of it has solved the underlying problem because the underlying problem was never communication. It was presence. The feeling of someone simply being there.

This is the gap that iAVATARS was built for. Not to replace a phone call but to fill the silence between phone calls. A physical device that carries the voice, the face, and the conversational memory of someone you love and makes them available in your home, whenever you need them, without an internet connection and without asking anything of the person on the other end.

The 18 million are not a market segment. They are people carrying something heavy. And they have been carrying it without the right tool for long enough.

Why iAVATARS Is Not an Elder Care Product

iAvatars — Fri, 24 Jul 2026 09:11:03 +0000

Every time someone hears about iAVATARS for the first time, they make the same assumption. They picture an elderly person in a care home, a device on a table, a family checking in from abroad. That picture is not wrong. But it is incomplete, and the incompleteness matters.

iAVATARS is not an elder care product. It is a presence product. The difference is more important than it sounds.

What elder care actually means

Elder care technology is built around a specific set of problems — medication reminders, fall detection, health monitoring, emergency response. These are real, important problems. There is a large and growing market for solving them, and many companies are doing good work there.

iAVATARS does not do any of those things. There is no medication reminder on our device. There is no fall sensor. There is no emergency button. We made those choices deliberately, not because those features are unimportant, but because they are not what we are building.

We are building for presence. And presence is not an elder care problem. It is a human problem.

Who actually needs what iAVATARS does

Think about the 18 million members of the Indian diaspora living outside India. Most of them are not elderly. Most of them are working professionals in their thirties and forties, living in the UK, Canada, the US, Australia. They left home years ago. They have built lives abroad. And they carry with them a quiet, persistent awareness of the people they left behind.

Think about someone who lost a parent two years ago and still reaches for the phone some mornings before remembering. Think about a child growing up in one city while their grandparent lives in another, and the relationship that never quite forms because geography made it too difficult.

None of these people are elderly. All of them have the same underlying need — the need for presence, for the feeling that someone they love is still part of their daily life even when distance or loss has made that difficult.

Why the framing matters for what gets built

If you build an elder care product, you optimise for the elderly user. You make the interface simpler, the font larger, the setup easier. These are good instincts for that market.

If you build a presence product, you optimise for the relationship. You ask different questions. How does this person actually speak? What phrases do they use? What would they say on a Tuesday morning? How do we make this feel like them, specifically, and not like a generic assistant?

That second set of questions is what drove the design of iSoul 1.0, our proprietary AI engine. It is not built to serve elderly users. It is built to capture one specific person and make their presence available to everyone who loves them, regardless of age, regardless of geography, regardless of whether that person is still alive.

The market iAVATARS is actually building for

55 million people lose a loved one every year. 270 million people live outside their country of origin. These numbers include people of every age, every background, every geography. The common thread is not age. The common thread is absence — the gap between where someone is and where the people who love them are.

That is the market iAVATARS is building for. It is larger than elder care. It is more universal than elder care. And it requires a fundamentally different product than elder care.

We happen to be starting in India, where the demographic concentration of elderly people living apart from their children makes the need visible and immediate. But the product we are building is not for elderly people. It is for everyone who has ever missed someone.

The Loneliness Epidemic: What the Data Says About Ageing Alone in India

iAvatars — Tue, 07 Jul 2026 09:02:05 +0000

A number worth sitting with: India is home to more than 140 million citizens aged 60 and above. By 2050, that figure is projected to more than double. This is not a distant demographic curiosity. It is one of the fastest-moving structural shifts in the country, and most of the conversation around it still focuses on healthcare infrastructure and pension policy, not on the data emerging around isolation itself.

What the public health data actually shows

The World Health Organization has flagged chronic loneliness in older adults as a genuine public health concern, not a soft or sentimental issue. Multiple studies now link sustained social isolation in elderly populations to accelerated cognitive decline, comparable in some research to the health impact of smoking or obesity as a risk factor. This is a measurable, trackable variable, not an abstract feeling.

Layer onto that a second dataset: roughly 270 million people globally live away from their country of origin, with India's own diaspora accounting for more than 18 million of that number. Combine the two, and a clearer picture forms. A large and growing share of India's elderly population is ageing in households separated from their children, either by international migration or simply by the pull of jobs in other cities. The distance is geographic. The effect, according to the research, is physiological.

Where the market data and the public health data intersect

Industry estimates put the global AI companion device market at approximately 12 billion dollars by 2030. That figure mostly captures general-purpose conversational AI, chat companions, and productivity-oriented assistants. It does not yet meaningfully account for a narrower category: physical, dedicated hardware built specifically around presence, memory, and emotional continuity rather than task completion.

That gap matters because the demographic and public health data both point toward demand for exactly this kind of product, while the supply side of the market has not caught up. Few companies are building physical devices specifically for the intersection of human connection and presence, as opposed to general voice assistants repurposed for the use case.

Why offline matters more in this dataset than most AI discussions acknowledge

Most coverage of AI products defaults to cloud-based assumptions. The data on elderly internet access complicates that default. Reliable, consistent connectivity is not guaranteed in many of the households this category needs to serve, particularly outside major metro areas in India. A product that depends on constant cloud connectivity inherits a usability gap precisely where the target demographic is concentrated.

This is the reasoning behind building iAVATARS, our own AI hardware company, around offline-first devices that let people interact with a responsive avatar of someone they love. All data, voice recordings, video, and interaction history stays local to the device rather than syncing to a server. It is a design constraint driven directly by the access data for the population being served, not a privacy slogan layered on afterward.

What this means going forward

The loneliness data, the demographic data, and the connectivity data all point in the same direction: a large, underserved population, a public health risk factor with measurable downstream cost, and a market gap that current AI companion products are not built to close. We think the next meaningful wave in AI hardware will come from companies willing to design around these specific constraints rather than retrofitting general-purpose assistants onto a user base that the data shows needs something different.

The numbers are already public. What's missing is enough builders treating human connection and presence as a primary design problem instead of a secondary use case.