Android · Tamil-first · Offline-first

Saravana Bhava – Murugan Bhakti

Official Android app for Tamil devotional reading, Saravana Bhava Guided Search, local bookmarks, Tamil device narration and worldwide Murugan temple discovery.

Release status · Updated 28 July 2026

Validated source baseline

The version 1.1.0 source baseline has passed Expo Doctor, TypeScript, lint, 51 automated tests and Android JavaScript export validation. Physical-device regression testing, Android signing verification and Google Play internal testing remain separate release gates.

Google Play status: no public store-install link is presented on this page until a signed release is verified through Google Play internal testing.

Release identity

Version: 1.1.0
Android versionCode: 37
Package: com.saravanabhava.murugan
Expo SDK: 56

Content baseline

1,373 devotional records and 371 Murugan temple records. Review labels are preserved; temple travel information should be checked with official sources before visiting.

Privacy summary

No user account, advertising SDK or third-party analytics backend. Bookmarks, progress, preferences, quiz results and an optional profile name remain on the device.

Guided Search

Saravana Bhava Guided Search retrieves bundled local devotional and temple records. It is not presented as generative AI, prophecy, medical advice or personalised religious authority.

Audio and narration

Tamil narration uses the device text-to-speech service. Recorded audio is offered only where an approved source and rights status are available.

Support

Report the screen, action, expected result, actual result, Android version and screenshot to ssakthiveluk02@gmail.com. Never send passwords or private documents.

Local data deletion

Use App Settings → Delete All Data, Android Settings → Apps → Saravana Bhava → Storage → Clear Data, or uninstall the app. There is no cloud account to delete.

Open complete deletion instructions

What remains before production rollout

  • Install and verify a signed QA APK on a physical Android device.
  • Confirm the existing Google Play upload credential.
  • Build the production AAB from the same validated source.
  • Verify the Google Play internal-testing build before any production promotion.