Designing Sri Panchangam — a daily devotion app for South India
How I took a culturally-mismatched, one-and-done booking experience and reimagined it as a Panchang-first habit product — from brand name and logo to full app design system, in six weekly ship cycles.
One app, two Indias
AppsForBharat's flagship product, Sri Mandir, had built a strong devotional commerce business — but its language, rituals, and mental models were deeply North-Indian coded. South Indian users were transacting heavily, yet almost never coming back.
The business goal was ambitious: grow South baseline revenue from ₹1.5 Cr to ₹5 Cr monthly, and fix retention with a target LTV/CAC of 2. The bet: a dedicated South app, built around the one artifact South Indian households already consult daily — the Panchangam.
Of South users, only ~14% ever made a second booking. The relationship ended at checkout.
Driven by South users — proof this was an under-optimized market, not a low-monetization one.
Despite massive SEO demand for "today tithi" and "today muhurtham". Intent was there; relevance wasn't.
Why the existing app couldn't simply be translated
Working with regional SMEs, panchang scholars, and user data, I mapped where the product's vocabulary, iconography, and ritual logic broke down for Telugu and Kannada users. Localization wasn't a translation problem — it was a worldview problem.
i."Mandir" is a foreign word
South users see "Mandir" and immediately read it as a North-Indian construct — undermining trust in the genuinely South temples the team had curated.
Mandir → Devasthanam · Kovil · Gudi · Alayamii.Different gods, different days
The "God of the Day" logic doesn't transfer. Saturday in the South belongs to Venkateshwara; Hanuman is known as Anjaneya. Names, iconography, and weekly worship patterns all needed re-mapping.
iii.The calendars literally disagree
Tamil panchangams run ~1 month behind, Telugu/Kannada ~15 days. Special tithis can't be unlocked from one common calendar — the South needed its own panchang engine.
iv."Chadhava" means nothing here
South devotion has a richer, more structured offering taxonomy. The catalog and booking flows had to speak this language natively.
Chadhava → Archana · Abhishekam · Seva · Homam · DaanamThe behavioral signal underneath
South users showed high ritual seriousness: correctness over convenience, recurring tithi-based action, and strong graha (planetary) awareness. SEO data backed it — high-intent searches like "today muhurtham", "telugu panchangam", "shani trayodashi" mapped directly to monetizable pujas. D0–D1 engagement was high but died fast: the need existed, the product relevance didn't.
From a booking funnel to a devotion loop
The core design thesis: retention must be engineered, not hoped for. Instead of leading with pujas (a low-frequency purchase), the app leads with the Panchangam (a daily ritual check) — and converts utility into devotion, and devotion into bookings.
The relationship ends at booking. No reason to return until the next crisis or festival.
Daily panchang check becomes the anchor; tithi-aware puja recommendations become the natural next step.
Hook architecture
I structured the experience around a primary / secondary hook system. Daily utility hooks acquire and retain; puja CTAs ride contextually on top of them.
☀️ Why today is auspicious
Ritual of the Day surfaces today's tithi significance — with a contextual Puja CTA mapped to that tithi.
🙏 Darshan of the GOTD
Daily darshan of the (South-correct) God of the Day, re-using proven Daily Darshan content with revised CTAs.
📿 Mantra of the Day
A daily listen-screen ritual that builds streak-like habit and feeds the CRM re-engagement loop.
Why "Sri Panchangam"
I led the naming exercise with one rule: the name had to anchor the primary hook, not the category. We evaluated 25+ devotional keywords across Telugu, Tamil, Kannada and Malayalam for cross-language consistency, daily-use association, and Play Store search volume.
| Criterion | Why "Sri Panchangam" wins |
|---|---|
| Anchors the entry engine | Panchang — not temple, not darshan — is the acquisition hook. The name keeps brand and GTM perfectly aligned. |
| Direct search intent | Matches high-volume queries ("Telugu Panchangam", "Today Tithi", "Muhurtham today") → stronger ASO, lower CAC. |
| Proven TAM | Panchang apps collectively hold 100M+ installs — an existing daily habit, not a behavior to invent. |
| Culturally neutral | "Panchangam" is universally accepted across Telugu, Kannada, Tamil & Malayalam; "Mandir" is North-coded. |
| Implies daily use | A calendar is consulted every day; a temple is visited occasionally. The name itself signals frequency. |
| "Sri" adds trust | Sri/Shri works across all South scripts and carries spiritual credibility without over-indexing on "temple". |
Logo & identity
I designed the logo and visual identity from scratch — warm saffron-to-vermilion gradients rooted in temple kumkum and marigold, paired with a typographic system legible across 4 language settings (Telugu, Telugu-English, Kannada, Kannada-English). Every icon, illustration, and color token was built to feel like home for a South devotee, not a translated North app.
A lean three-tab architecture, built around one daily habit
V1 shipped deliberately lean: Panchang (daily & monthly views with darshan, mantra, and ritual hooks), Puja List, and Booking History / Profile. Existing Daily Darshan and Daily Mantra properties were re-skinned with revised CTAs to ship fast without sacrificing craft.
Designing for trust from Day 0
Alongside the visible UI, I designed for the invisible scaffolding the team mandated from launch:
- 4-language design system — Telugu, Telugu (English), Kannada, Kannada (English) — with type scales tested for script height and density
- Deep-link continuity from web, so existing Sri Mandir users land in context, never on a cold start
- Real-time event pop-ups designed as moments of delight ("Your Puja video is ready") that deep-link straight to fulfilment
- Push & CRM templates segmented by acquisition hook — a user acquired on "daily rashifal" hears about rashifal first, special tithis second
Six versions, six weeks
We designed and shipped in weekly increments — each version a complete, testable bet rather than a partial feature dump.
Play Store ready
Login, language selection, and the core Panchang experience — the daily anchor goes live first.
Bookings enabled
Puja L1/L2 with additional SKU flows, booking history, filter chips, and hero banners.
Retention levers
Mantra of the Day, GOTD Darshan, Daily Rituals, and Rashifal activate the habit loop on Panchang.
Jataka unlock
Kundali generation opens the personalization era — "Know your Jataka" as a new primary hook.
Recommendation engine
Dosha/Dasha-based puja recommendations and a Dosha widget on the Panchang surface. ("You've done 2/5 recommended Shani pujas — here's the next one.")
Digital monetization
Bhajans, wallpapers, and personalization — the foundation of a freemium layer (Isht Devata mantras, personalized panchang, festival planner) beyond puja transactions.
Designed against numbers, not vibes
Every design decision was tied to a measurable target on a single shared dashboard, spanning acquisition, retention, engagement, and monetization.
vs <17% on the existing app.
Contextual tithi-to-puja mapping.
Right ritual, right time.
Panchang-led acquisition lowers CAC.
Habit loop → second transaction.
vs ~14% on web today.
For BAU-mimic acquisition flows.
The north-star economic outcome.
What this project taught me as a designer
Localization is product strategy
Swapping strings would have failed. Real cultural fluency — vocabulary, deities, calendars, offering taxonomies — had to be designed into the IA itself.
Lead with utility, monetize with context
The Panchang-first model turned a transactional funnel into a daily ritual. Monetization works best as the natural next step of a habit, not the front door.
Design for the dashboard
Tying every screen to a metric (CTR, retention, attach rate) made design reviews sharper and trade-offs honest — the senior-designer muscle I value most.
Ship in complete weekly bets
Six self-contained versions in six weeks forced ruthless prioritization: re-using proven properties for speed while protecting craft where it mattered.