I agree with Rebecca, and will go back to Google Calendar until this is fixed.

I love Proton but this issue is so bad for me that I've considered going back to Google Calendar.

Like Matthew Scheffel, I am constantly editing events and typing "15" and "45" (and then also adjusting the ending time which automatically jumps to 30 minutes...). Please, please, let me snap an event to the 15-minute lines when moving events with the mouse, not just to 30-minute increments. 30 minutes is way too inaccurate for doing time blocking, but trying to work with 15-minute blocks in Proton Calendar becomes tedious and frustrating.

Yes, it would be very helpful to have this feature

I totally agree with Rebecca!

This is important due to simple accuracy of appointment time and duration. 30 minute blocks are too long. I'd like to be able to at least schedule on the 15s and 45s. The best of all worlds would be the ability to schedule appointments at any time and any duration, like I currently can with my Android calendar app.

This is important due to simple accuracy of appointment time and duration. 30 minute blocks are too long. I'd like to be able to at least schedule on the 15s and 45s. The best of all worlds would be the ability to schedule appointments at any time and any duration, like I currently can with my Android calendar app.

Finally! An alternative to the evil company calendar. Congratulations to Protonmail team! My suggestion is to enable the time periods in a day's calendar to be 15 minutes instead of 30 minutes only, as is the case now.

I move blocks around on my calendar a lot, and 15 minutes is kind of my basic building block. Things seem to snap to 30 minutes, which means I have to constantly edit events with manual input when a drag and drop should work fine.

Not having to type "15" or "45" would be nice, too.

This is part of 'Better usability for the Proton calendar'

Move your votes to that request!

I need this as I often scheduled in 15 Min blocks. Currently I'm putting the time in the description which isn't ideal