Of course I agree with you - but is that chance that one of the subscribers to your service losing their child reason enough for you to NOT create the functions described?
That was my point. I have a 6-year old and a baby currently loading with delivery in July. I also have a very dear friend who lost her second child to SIDS.
We are getting the "Your baby is currently the size of an avocado" emails -- We like the service.
The fear of a customer of such service's potential pain, while real and however small, shouldn't deter the availability of the service.
You're thinking of it from the perspective of a single user, in which case the chance of miscarriage is relatively small. However, if you think of it from the perspective of the entire user base, then the likelihood that someone who receives an avocado email suffered a miscarriage is close to 1.
That was my point. I have a 6-year old and a baby currently loading with delivery in July. I also have a very dear friend who lost her second child to SIDS.
We are getting the "Your baby is currently the size of an avocado" emails -- We like the service.
The fear of a customer of such service's potential pain, while real and however small, shouldn't deter the availability of the service.