Hi, Robert. I understand that you are trying to find a solution that would 
be easy to implement. My experience with MLO is that I should leave that 
for the developers. Some changes that look easy to me turn out to be big 
where others that seem complex are easily done. I guess it's in knowing how 
the existing code and data are structured. So I believe my job is to tell 
the developers what would be useful and their job is to figure out what's 
the most do-able way of approaching it.

I have contexts for work (or I did before I retired) and home but I didn't 
set location alarms for either one. I always know that I have arrived at 
work or home, it's not the kind of thing you miss. And I know I have 
pending tasks there, I don't need to be reminded. Also, the people who are 
already at my home or work want my attention when I walk in - whipping out 
my phone to shut an alarm (and, probably check my to-do list and maybe 
email) makes these important people feel disrespected. So after I have 
settled in I check my to-do's out of habit, without an alarm.

I use alarms for places that I might pass without thinking about what I 
need to do there, like the hardware store. It's very possible that after a 
hardware store alarm, the nect location alarm would be the same hardware 
store on another day. (My dream would be making a hardware store context 
and having MLO alert me whenever I'm within 200 meters of anyplace that 
Google considers a hardware store.)

I think solution 3 is the right one. I know that you consider it too 
complex. But I think it's useful for the developers to know, if this were 
feasible would you think it's the best and if not what would be better?

btw this thread seems to have a very low view count, which may mean that 
nothing will happen anyhow.
-Dwight

On Monday, July 1, 2013 7:40:38 AM UTC-4, robert roszak wrote:
>
> Hi Dwight,
>
> Thank you for your engagement.
>
> As to the number of people using nearby notification feature: I think it 
> might have been greater at first, but constantly bothering notifications 
> quickly made the users switch it off. In general, this seems very nice to 
> be notified only when you enter a certain place. But you quickly get fed up 
> with these notifications which turn out to be more disturbing than helping. 
> I agree, however, that it would be good to assess how big group of users 
> this issue concerns.
>
> Both solutions I described earlier do have their downsides as well.They 
> were taken off the cuff and some kind of elaboration is certainly needed.
> Solution 1: This is actually the worse solution in my opinion, but it 
> should be easier to implement. Despite its downsides, it is still better to 
> have a feature that works in 75% of cases than the feature that makes you 
> switch it off at the very first notification you get.
>
> Solution 2: Don't take it the wrong way Dwight, but I think that the 
> examples you provided are rather marginal. There could be a reset of the 
> 'last entered location' property happening every midnight. I really think 
> it wouldn't been needed, though, because most of us (I believe) have 
> locations 'at Home' or 'at Work'. You do sleep at home in most cases, and 
> you are supposed to enter 'at work' location 5 times a week. 
>
> I would like to put the emphasis once more, that it is better to have 75% 
> effective solution than the current one.
>
> *Are there any other users who find this feature useless at the moment?*
>
> Robert
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"MyLifeOrganized" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mylifeorganized.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to