Skip to content

Obsideo

My feedback

4 results found

  1. 523 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Sharing a calendar is available on Web. 

    On next iterations we would like to enable the editing permission on mobile apps and add in the future to only share the "busy" information

    Obsideo supported this idea  · 
  2. 56 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Obsideo supported this idea  · 
  3. 531 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Obsideo supported this idea  · 
  4. 978 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Obsideo commented  · 

    Two way sync between apps, yes. Thunderbird integration with Proton Bridge would be a start.
    CalDAV full support would go a long way in usability and adoption, as well as the ability to at least support credentialed iCal formats.
    Additionally support for FREE/BUSY data information within calendar events is something else that is critically missing.

    Frankly as it stands now, Proton Calendar is simply not enough except for casual use. Too many road-blocks and unsupported integrations stand in the way. If Proton Calendar interface and applications cannot support these things, then Proton Calendar MUST be supported READ/WRITE in many iterations and use-cases within OTHER apps that can and DO support all the necessary interoperability features between the different calendaring platforms. This at least would make scheduling within Proton Calendar as a back-end viable for work/life.
    Again, as it stands now, this is just not possible except in the most multi-app and fragmented state.

    Obsideo supported this idea  · 

Feedback and Knowledge Base