Here’s Template A (Topic: General) in English, ready to post:
Title
In those minutes when you can’t call for help, how do we make “being noticed” and “being located” truly reliable?
Body
In many emergencies, outcomes hinge on two things: someone knows you’re in trouble and they know where you are.
We’ve shipped three pragmatic Android updates and would love the community’s thoughts and real-world experiences:
Reverse Guard — pre-set Safe Areas / Ban Points; when conditions are met → instant alert.
Multi-interval SafeGuard timing — add multiple guard intervals and adjust their lengths; only timing changes, the rest of the flow stays the same.
Group SMS — if the primary contact hasn’t called back within 30 minutes, the system automatically fans out to all backup contacts to avoid a single blocked path.
Looking for your input
How would you define “Ban Points” and “Safe Areas”? Which everyday scenarios are worth pre-setting?
For multi-interval timing, how would you arrange the number/length of intervals (e.g., commute/night)?
In disasters or multi-party outages, could fan-out notifications become noisy? How would you design it to be effective without being spammy?
Any cases you’ve seen where being discovered sooner clearly changed the outcome?
Note: We’re currently on-device only (no cloud uploads). If you have privacy/permissions expectations for safety apps, I’d love to hear your standards and best practices.
Replies