Pace App Reviews
I like Pace for the most part. I havent yet upgraded because the timings are good enough for me to try it out. Sadly I have to stop using Pace because a giant white screen flashing up to force a break is too eye searing most of the time. Ill keep any eye on updates. Maybe if I could set the break screen colors Id switch back to it (and Id be willing for that to be in the IAP). Pace also suffers from the same thing every other typing timer suffers from, interruptions. While writing code I know I need to take a typing break, but interrupting a thought process is the worst. At least one other timer I use pops up a "break is coming" notification so I can know to prepare for a break rather than just being blind-sided by it. Update: I had disabled Pace. I told it not to start at login and made sure it wasnt in my login items. It still insists on starting. For now its deleted. I will check back on it in a while to see what updates come along, but for now I just cant recommend it.
I’m a happy Pace user again. The app hasn’t been updated in a while, and it was crashing on launch in 10.11.2, but the OS update to .3 fixed it. So I’m back to using Pace every day as a reminder to stop slouching and get up and move every once in a while, and it works great.
I was looking for a way to ensure I wasn’t spending too much time staring at the screen. Pace is nice for that. One major problem: it cuts you off. If I am typing away at an email, Pace has no mercy. It’s infuriating to have your train of thought abruptly derailed like that. It should wait for a full second of no keyboard/mouse input before beginning the break. It’s unacceptable to cut one off — I end up turning Pace off or skipping/snoozing for most of the day because it happens at really inconvenient times and has no mercy.
Cuts you off abruptly
I was looking for a way to ensure I wasn’t spending too much time staring at the screen. Pace is nice for that. One major problem: it cuts you off. If I am typing away at an email, Pace has no mercy. It’s infuriating to have your train of thought abruptly derailed like that. It should wait for a full second of no keyboard/mouse input before beginning the break. It’s unacceptable to cut one off — I end up turning Pace off or skipping/snoozing for most of the day because it happens at really inconvenient times and has no mercy.
OS X 10.11.3 update fixed the crash.
I’m a happy Pace user again. The app hasn’t been updated in a while, and it was crashing on launch in 10.11.2, but the OS update to .3 fixed it. So I’m back to using Pace every day as a reminder to stop slouching and get up and move every once in a while, and it works great.
Cannot configure without purchasing
As a developer I can appreciate the need to keep the lights on, but as-is this app is useless even for evaluation. Not a good first impression, and I’m not inclined to give it a second chance.
Pretty good, but could use some changes
I like Pace for the most part. I haven't yet upgraded because the timings are good enough for me to try it out. Sadly I have to stop using Pace because a giant white screen flashing up to force a break is too eye searing most of the time. I'll keep any eye on updates. Maybe if I could set the break screen colors I'd switch back to it (and I'd be willing for that to be in the IAP). Pace also suffers from the same thing every other typing timer suffers from, interruptions. While writing code I know I need to take a typing break, but interrupting a thought process is the worst. At least one other timer I use pops up a "break is coming" notification so I can know to prepare for a break rather than just being blind-sided by it. Update: I had disabled Pace. I told it not to start at login and made sure it wasn't in my login items. It still insists on starting. For now it's deleted. I will check back on it in a while to see what updates come along, but for now I just can't recommend it.