Docs

  • Channels Channels
  • Beams Beams
  • Developers
  • Support
  • Blog
  • Sign up
    • Search powered by Algolia
    • Sign in
    • Sign up
    • Channels
    • Beams
    • Pusher lab

    Pusher Lab

    At Pusher we pride ourselves on providing reliable and stable services you can trust. We maintain support for our APIs and protocol versions for as long as reasonably possible so users don’t have to frequently deal with breaking changes that will impact their applications.

    However at Pusher we also want to continue to innovate and keep bringing our users cutting edge features and technologies to help solve complex problems as seamlessly as possible. This means we will sometimes release new features or APIs that will go through an Experimental or Beta phase.

    Working with our developer community we may make changes or deprecate Experimental or Beta functionality at short notice so you should be sure not to rely on these in a production environment. Where practical the timelines below set out or expectations for changes to Experimental or Beta features.

    ∞ Experimental program

    Experimental features could change at any time, however depending on the nature of the change we will endeavour to communicate changes to users at least 24 hours in advance.

    Typically experimental features will remain experimental for no longer than one business quarter after the last update (subject to review), and will either be progressed to a Beta or Generally Available state or be deprecated.

    ∞ Experimental features

    Product Feature Last update Review by date Resources Status
    Channels HTTP publish API info 16 Feb 2022 01 Dec 2022 - Trigger example
    - Trigger batch example
    - HTTP API reference
    Active
    Beams WEB support in Flutter SDK 16 Feb 2022 01 Dec 2022 SDK repository Active

    ∞ Beta program

    Beta features should be more stable than experimental features, but could still change at any time. However depending on the nature of the change we will endeavour to communicate changes to users at least a week in advance.

    Typically beta features will remain beta for no longer than two business quarters after the last update (subject to review), and will either be progressed to a Generally Available state or be deprecated.

    ∞ Beta features

    Product Feature Last update Review by date Resources Status
    Beams Safari web push notifications 09 Sep 2021 01 Dec 2022 Safari configuration guide Active
    Channels Cache channels 05 Apr 2022 01 Dec 2022 Cache channels docs Active
    Channels Subscription count event 18 July 2022 01 Dec 2022 Subscription count docs Active

    ∞ Communication

    ∞ Update to users

    When we make updates to experimental or beta features we will communicate these via:

    • Email
    • Beta slack channel
    • Changelogs / Documentation updates
    • Support help centre

    ∞ Feedback from users

    The success of our experimental or beta programmes depends on feedback from our developer community. If you have a feedback on any of the programmes above you can do so via:

    • Our support team
    • Beta slack channel

    Contents

    • Experimental program
      1. Experimental features
    • Beta program
      1. Beta features
    • Communication
      1. Update to users
      2. Feedback from users

    Spotted something that isn’t quite right? Create an issue on GitHub.

    Copyright © 2020 Pusher Ltd. All rights reserved.

    • Support,
    • Status
    • Follow Pusher on Twitter Twitter
    • Follow Pusher on Medium
    • Subscribe to Pusher’s channel on YouTube
    • Follow Pusher on LinkedIn
    • Follow Pusher on Github GitHub
    • Follow Pusher on Twitch Twitch
    • Follow Pusher on Discord Discord