Personally I would prefer better filtering features.

If I have something in Someday, in other words something that I am not sure whether it needs to be done, I most certainly do not want that thing to cause any beeping in my pocket. Not even if it actually is a decided Next action (perhaps even marked for Today) do I want it to beep, because if I had decided to do it now, then I will, and if I had decided not to do it now I will not do it now and I will not change my mind just because something starts beeping. A pure annoyance, if you ask me.

The key to have a clear plan, with clear intentions, is the ability to able to find the relevant errands on your lists before you even go out. That may take some quite significant improvements in the way contexts and tags, and the quick filtering mechanisms, work. I'd rather see those improvements being made, because those will be much more generally useful (not just for errands).

@Folke I totally disagree with you.

@jetlagpunk
Hi,

Thank you for your feedback.

It has been in our developing plan. And we have completed developing a demo for this feature. Then we find problems. There are two big problems. One is that it need much power. The other is that the Map can not find the place accurate. We will try our best to find the solution.

Shall you need any help or have additional questions, please do not hesitate to contact me back.

Thank you for your support!

Best regards,
Doit.im Team

Glad to see this is on the roadmap - I too really want to see this feature added please. I noticed many others do as well:
http://help.doit.im/topics/522
http://help.doit.im/topics/1494
http://help.doit.im/topics/4128

Fully appreciate that implementing is not trivial! Implementing a robust geo-fence based to do alerting system will be quite tricky and Google Keep has the advantage on this front because they can leverage off a mature concepts they already developed and learnt with Google Maps and Google Now. Some of the challenges:
- Finding the right balance between polling current location and matching it to a filter of to-do items that have that location/proximity tagged.
- Basics like being able to tag tasks with locations and having a filter / highlight / alert option in do it based on location would be a good start.
- Not only would it be great to tag tasks with locations, but have a 'home' context and be able to tag that context with a location, so that when near home, home based tasks are highlighted. Ditto for when at work.
- Fully appreciate it'll be hard for doit to fetch and process lots of metadata about these shops nearby have items on sale that you are looking for in your 'shopping' context, etc.
- Hope doit can deliver just some basics for now and then improve it over time.

If there is a beta version we could help test, I'd be willing.

Sorry, extra note from me on this:
- On android, you can leverage the location based services to reduce battery consumption.
- With geofence / proximity concept, you can work around the accuracy issue, e.g. 'within 1 kilometer of location'
- You could add the feature as a beta / opt in option, so users are aware it may drain battery and have some issues
- You could provide the user with settings options for proximity, optional use of seeking high accuracy locations versus network provided, and frequency to poll location (if unable to use more sophisticated services on some mobile os platforms)
E.g.
- perhaps Android's geofence feature should be reasonably battery efficient and help as a better alternative to polling for locations directly from the app (http://developer.android.com/training/location/geofencing.html)
- and Apple can support somthing similar too (https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/LocationAwarenessPG/RegionMonitoring/RegionMonitoring.html)

So from the above, the two most major smartphone and tablet platforms give doit.im the underlying functions needed to implement what we're asking for.

Oops, yet another idea I missed in the previous two posts (sorry):
- while tablets and smart phones have mature location based services, a laptop or workstation doesn't.
- there are maybe some tricks for the Windows and Web Client doit could do based on GeoIP or WiFi.
- an alternate to using actual GPS based co-ordinates for this is to consider location awareness based on the network connection, e.g.
-- for Windows doit client: http://msdn.microsoft.com/en-us/library/windows/desktop/ms739931(v=vs.85).aspx
-- smartphone/tablets could maybe make assumptions based on WiFi SSID, or the MAC address of the gateway the phone/tablet is connected to.

The above is a bunch of work arrounds, and would require the user to possibly help doit.im know which location has what network, so less ideal than leveraging proper location based services provided by mobile platforms.

@jpvriel
Hi,

Thank you for your feedback and sharing your ideas with us.

Some of you suggestions have been in our developing plan. Some give us new ideas. We will take them into consideration.

Shall you need any help or have additional questions, please do not hesitate to contact me back.

Thank you for your support!

Best regards,
Doit.im Team

As a long-time user I'm waiting on implementation since 2013 ;) mixing doit & google keep is tedious so please add oil, it would be of great help;

@dkgrieshammer
Hi,

Thank you for your feedback. We will work harder.

Best regards,
Doit.im Team