Notification Hubs

How can we improve Azure Notification Hubs?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Add support for Azure Notification Hubs to push messages to web browsers

    Azure Notification Hubs should be able to deliver messages to users via web browsers.

    This should be done through lightweight javascript. The script should be cross browser compatible with desktop, mobile and legacy browsers.

    Basically this would replace the need for hosting SignalR unless you're building something like a chatroom.

    796 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  46 comments  ·  Flag idea as inappropriate…  ·  Admin →

  2. Bulk tagging of installations

    When we need to add a tag for a set of installations, we currently need to perform a request to Azure Notification Hubs for each installation.

    This results in very poor performance, ruining one of the main advantages of Notification Hubs: massive scalability.

    It is to be expected that many many uses of tags will involve applying tags on installations dynamically in response to business events in the app. Since this may affect as many users as we would later want to send notifications to, it follows that we should have an efficient way to apply tags to many installations…

    55 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    planned  ·  8 comments  ·  Flag idea as inappropriate…  ·  Admin →

  3. Make Notification Hub as simple as Firebase from google

    I think you know that we have products addressing the same problem as we are. but they do it simpler than we are. For example Firebase code required from dev- much less than Notification Hub.
    https://developers.google.com/cloud-messaging/faq

    "You no longer have to write your own registration or subscription retry logic. " - why we can't do something simple like that!

    Recently when we discussed with customer usage of notification hub and I can't explain why they should use it instead of firebase after feature comparison

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

  4. Add support for data notifications on iOS and Android

    FCM has a concept of a "data" message, similar to WNS Raw message, that permits an arbitrary JSON payload. They include the ability to wake backgrounded apps to allow them to handle the incoming message (rather than going directly to the OS notification manager).

    Azure should replicate this support and include the ability to use them with Template registrations.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Forgot password?
    Create a password
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Notification Hubs

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice