As I’ve written in the past – Push Notifications are one of the 9 Social Features in Software that keeps people engaged with a particular product. Most Users love when the software reaches them about events – as fast as in real time. For this reason – here you have a Push Notifications Service – that is wrapper around Google/Firebase Cloud Messaging. The Service has two main use cases.
Publisher & Consumer of Messages for non-technical users
I’ve wanted to make it possible any user – even without any knowledge on software development and programming – to be able to set-up, Create & Send or Receive Push Notifications.
The idea is very simple. After you’ve created an account and you are logged in – Create an App.
You can enter Standard properties like – Title, Description and an Icon.
The GUID and Secret for Verifying requests are for the programmatic integration, so they doesn’t bother you here.
You could see how much users have registered for your app and also how much push events(records) you have created.
Above the List Items there is a “View” Link that will open the consumer side of the App.
You can share the link and let users Subscribe to New Events from your side. After you have at least one subscriber, you could create simple push record. It has very similar properties – Title, Content, Icon. Have in mind that the display area for a Notification is small, so limit your messages to short sentences. What you could do is – to add a Redirect URL address – that will be opened when the user clicks on the Notification.
The Push Records are something like templates. You could trigger creation of actual pushes from it – to all the subscribed users.
The result is a push message that will work on all devices that have Push Enabled Browsers Installed.
Simpler Rest Service for plugging Notifications into a System
I’ve made possible external software to integrate with the Push Service – currently from the Administrator side. I may also include the Client/User side endpoint in the future, but for now – it does the job I have created it for.
For a 3-rd party developer to use the service, you will employee the app globally unique identifier, the secret for verifying requests, and something more. You could contact me at email@example.com for more information.