Hacker News Reader

The permissions were a non-starter for me. If you're going to download my contacts and have the ability to share, edit, or delete my calendars, you need to explain why.

Even then, requiring incredibly invasive permissions for a productivity app is unreasonable. Just limit the features that "need" those things instead.

View on HN

100% agreed with this. It's not clear to me why you need my contacts. My mental model of the software is "put my todos onto a calendar". Maybe that's wrong? But if not you need read access to my todos, and read access to see slots on my calendar that are booked (you don't need details of those appts and you don't need delete access).

Downloaded the app and got to the Oauth Google Cal part of onboarding and bailed. Sad, too, because I already timeblock daily using paper. This seems like an easy buy for me if it does what it says on the tin. But not with a perms model like that.

We'll definitely try to do a better job explaining the permissions, thanks for pointing this out.

Unfortunately a fully functioning calendar is key to our product and we decided not to limit features at the moment. We'll consider a "lighter" approach in the future

Reply on news.ycombinator.com