Free up to 1MM monthly messages. No credit card required.
This is the third and final part of a series of tutorials on building a chat application in JavaScript that uses audible chirps to connect users to the same channel using the Chirp WebAssembly SDK and PubNub JavaScript SDK. See the previous posts, How to Send Chat Invites Using Chirp (part 1) and Creating a Chat App with PubNub and Chirp (part 2), before continuing with this section.
Looking for the completed project? Download it from the Chirp PubNub Chat GitHub repo or try the demo.
Although Chirp sends data completely offline, registration credentials are needed to identify your user account to the SDK, and to configure the SDK with your profile-specific features.
For web-based applications using the Chirp JavaScript or WebAssembly SDKs, applications are identified using your application key, and must be hosted on one of the web origins that you specify in the origins pane of your application.
CORS rules won’t allow the browser to load the Chirp WebAssembly SDK directly from the file system. You must host the files using a server. I recommend a http-server.
npm install http-server -g
Start the server from the same directory as your project files:
http-server
Add your origin to the origins pane of your application.
Visit http://localhost:8080 to view and test your chat application powered by Chirp and PubNub.
Some other applications for Chirp + PubNub could include:
Have suggestions or questions about the content of this post? Reach out at devrel@pubnub.com.
A Notice of Privacy Practices (NPP) is one of the requirements of HIPAA and helps patients understand their personal data rights.
Michael Carroll
HIPAA violations can be financially expensive and devastating to a brand. Examine some examples of HIPAA violations, and learn...
Michael Carroll
HIPAA covered entities must follow the five technical safeguards to achieve HIPAA compliance and prevent data corruption.
Michael Carroll