5 ms·
This is so bad. Seriously the reminders app itself is already pretty trivial, perhaps with the exception of the geofencing feature, which in and of itself is ex
by arthurcolle 7y ago
This is so bad. Seriously the reminders app itself is already pretty trivial, perhaps with the exception of the geofencing feature, which in and of itself is extremely stupid and limited (only lets you trigger notifs if you are arriving or leaving. What if you want to trigger notifs if you're still at that specific location, but not necessarily leaving that location?)
Seriously this can't be that hard to build as a backwards compatible API. Extremely poor engineering practices. If their software org is as bad as their hardware org (sorry, but broken keyboards after a year of use is unacceptable to me in 2020), then it makes sense they'd break this. I initially was hesitant to start using Reminders about 6 months ago but eventually found a way to incorporate it into my life. Hope this doesn't break my workflow. Definitely glad that I've divorced my work machines and my personal machines, and that I don't jump the gun and immediately update to the newest OS versions anymore on any of my machines.
Yikes all around.
- k_sze 7y agoGeofencing in Reminders is a mess. I don't understand Apple's insistence on having an address, for several reasons: 1. Not all places have an address; 2. I don't necessarily know the exact address of a place even if it has one, but I can pin point it visually on a map; 3. Apple Maps' data is incomplete and inaccurate anyway.
- arthurcolle 7y agoSpot on! What do you think about this situation beyond geofencing? Like, how badly do you have to fuck up to not be able to ensure continuity on artificial abstractions like "an instance of a reminder" across a major upgrade? (Major as in major-minor versioning). Honestly if I was head honcho I would fire any engineers that were involved in this specific app/decision to add new features and not care about backwards compatibility. It's really that bad, IMO /radical