xen
-
1 votedeclined ·
AdminCarter
(Admin, two forty four a.m.) responded
There a number of interesting ideas here, some of which could be broken down into their own individual feature requests.
For example: one-off (or self-deleting situations) could be its own separate request.
The overall request to invert Locale is beyond the scope of our design for Locale. We intend Locale to be the hub of situations on your phone and going backwards from another app presents a number of usability problems. Most specifically, after a situation is created a user many need to re-prioritize that situation so that it will behave as expected in the context of all other situations.
It sounds like your request is specifically oriented towards integration with Astrid. Both we at two forty four a.m. and the developers of Astrid believe that the user experience is of utmost importance, so you can be sure that we’re always looking at ways of improving our apps :).
xen
shared this idea and gave it 1 vote
·
-
87 votesunder review ·
AdminCarter
(Admin, two forty four a.m.) responded
This is a great idea and we’ve been looking at it for quite a while. I agree it could be quite useful when combined with Astrid integration. For example, a location-aware reminder would be really useful a few minutes after arrival, rather than right when walking in the door.
A key requirement would be that the delay should be very consistent and predictable. For example, if I ask for a reminder 30 minutes after I get home, it should always be exactly 30 minutes after I get home. Thanks to Locale 2.0’s instant location, we are now be able to meet this requirement.
I have a few open questions about this as we go forward with investigating how this might work:
- Should there be delayed conditions? Or should this be implemented as delayed settings? (The end result would be the same, but each requires a different mental model) -… more
xen
shared this idea and gave it 1 vote
·