Heart disease doesn't present the same in women. Neither should the course.

Arogya Nari is a women's health platform, and the constraint that shaped every technical decision in it is the person on the other end. She is not going to install an app. She may be on a modest Android phone, on a connection that comes and goes, and she may want the whole thing in Hindi. So everything had to run in a browser tab, load without a manual, and never assume the best case.

Start with the content, because that is the part most health tech gets wrong. It treats a woman as a smaller man. The heart course does the opposite on purpose: it opens with the fact that a woman can have a heart attack without the classic blockage a man's diagnosis is built around, and it teaches the risk factors that are hers specifically, menopause, pregnancy complications, anemia, migraines, depression. The framing is the product. The 3D is how you make it stick.

To teach anatomy you want a model someone can actually turn around and look inside, not a diagram. The easy, wrong way to do that in 2026 is to ship a full game-engine build for every lesson and make a phone download tens of megabytes before it can show a heart. So the interactive anatomy runs as glTF models through the browser's own model viewer: it uses the GPU every phone already has, it auto-rotates, it takes camera controls, and a first-time user can explore it without being told how. The heavier engine path is kept for the few modules that genuinely need it, not spent on the ones that don't.

The unglamorous work is everything around that. The 3D viewer is memoized so a language toggle or a scroll does not tear the model down and rebuild it. Every string in the course data exists in English and Hindi from the start, held in the shape of the data itself rather than bolted on as an afterthought. And the whole thing is multi-tenant, so a health institute can run its own cohort under its own code, because that is who actually distributes this to the women it is for.

The hard part was never the 3D. Interactive anatomy in a browser is a solved problem if you are willing to assume a laptop, a fast line, and someone who will install what you tell them to. The hard part was refusing all three assumptions, and making medical 3D survive a cheap phone and a weak signal, for exactly the person most health software has decided is not worth the trouble.