Ethan Scott
My feedback
4 results found
-
1,463 votes
Ethan Scott
supported this idea
·
-
56 votes
An error occurred while saving the comment
Ethan Scott
supported this idea
·
-
25 votes
Ethan Scott
supported this idea
·
-
132 votes
Ethan Scott
supported this idea
·
I've seen a couple people mentioning loading time when an app is opening, but a major weakness of Proton Calendar is that it's so slow to do basically everything and all other actions are held up until the one currently running is complete. Examples include initial loading of the calendar, creating a new event, changing the time on an existing event, modifying repeat sequences, etc.
I don't fully understand the technical aspects of what calls and actions need to occur, but other calendar apps such as Google Calendar and Outlook will perform most of these actions near-instantaneously. I know it's not simply network conditions because I have used both Proton Calendar and Google Calendar on a variety of devices and network conditions and there is always an obvious gap favoring Google's calendar over Proton's.