Neptune is a Low Code Platform which helps you abstract the communication layer of your applications. Instead of coding the templates and scenarios in your codebase, you would implement them using Templates and Events which are keys components of Neptune. Because of the way Neptune is architected it solves multiple problems and in this article we aim to explain those.
Almost all applications interact with usera using external communication channels like Email, SMS, Push Notifications. If your users are internal you might even create a support desk ticket, a bug in your issue tracker, an issue in your project management tool. In order implement these scenarios, one would broadly endup doing the following:
- Prepare the Template with Content and put in your codebase
- Trigger the type of notification you want to send
- Compile the template with placeholders
- Use a provider like SES, Twilio to deliver the notification
When you productionize your application, you would do the job of compiling and delivering within a background job using Queues.
As part of this flow you not only end up managing templates/providers in your codebases, but also managing the queues which process the jobs in background.
In some cases (particularly during development) you don't want to actual deliver a notification but only simulate it or mock it.
Neptune aims to help you solve the above problem by becoming one place to manage all your templates and providers. It acts as a Background job processor, helps you get real-time insight into deliveries and debug if there is any problem.
To communicate with Neptune, all you need to do is trigger an Event from your application.
Neptune already comes out of box with facility to create mutliple environments, and you can configure at environment level if that environment is for purpose of "mocking", so, the delivery be is SMS, Email, or Push is not actually delivered to user.
Businesses run around events and sending the occurence of such an event to Neptune brings forth multiple oppurtunities which helps you build your business better.
Business Analytics and Intelligence
As your applications grow you would be required to draw analytics from your applications so that various stakeholders from various departments like Sales, Marketing, Investors etc., might need to make decisions.
Neptune is architected around Events and encourages businesses to think and build their applications around events, it becomes one place to even record, analyze and gain insights into the events. You can prepare custom dashboards and subscribe to events of your own interest. Because the events are caused by users and notifications are delivered to users, It goes further than this, Neptune gets to give you list of users - and analyze a single user behaviour.
User Notification Settings
Because of the above setup, Neptune becomes the core application which drives communication to users. Your users can use Neptune's notification settings to customize what kind of notifications do they prefer and when would they prefer. Neptune's hosted UI helps you "not build" these solutions again and again.
Event Drive Architectures are evolving and they are extremely powerful. We aim to add this power to businesses from Day 1 which not only helps to solve above use-cases but even draw patterns among users using Machine Learning and suggest which users might help you achieve a particular goal - be it sales or marketing.
Templates and Previews
Your content, marketing team can compose templates and switch to send a different template without contacting the developers. Our HTML builder is based on handlebar templates which are pretty flexibile and you can even code conditional logic.