August 2022 Summaries

MMS stands for Multi Media Service, which is used for sending various types of files over cellular networks, not just images. The Vonage Messages API supports four different MMS message types: image, audio, video, and vCard. MMS can be used for promotional messaging, transactional uses such as instructional videos or proof of parcel deliveries, and can add an extra dimension to SMS messaging by promoting products with images, videos, or sound clips. To send an MMS message using the Vonage Messages API, a POST endpoint is used, which requires an Authorization header and a JSON payload containing the message type, file URL, to and from numbers, and channel information. The Vonage Messages API can be used to send MMS messages in the USA to numbers on certain networks, such as AT&T, T-Mobile, and Verizon. An example application was built using the Vonage Ruby SDK to send a daily MMS message containing a random xkcd comic image. The application uses environment variables, a gem called get_xkcd for interacting with the xkcd API, and the vonage gem for sending the MMS message.

The Vonage Client SDKs for Android, iOS, and Web are used to build voice and messaging capabilities into applications, with the Conversation API helping to showcase their multi-platform functionality. The V-App is an end-to-end application on all three platforms, built using Node.JS as its backend client, which handles RTC webhook events from Vonage and stores them in a Postgres database for efficient querying. The V-App supports user accounts, conversations, calling, sending images, and more, with the backend client also having a voice answer route that returns an NCCO. To deploy the backend seamlessly, the Vonage CLI Scaffold Plugin can be used to download, setup, and run all three clients and the backend, making it easy for developers to try out the V-App.

The summary is as follows: We have created a fully working visual regression system for UI components using Playwright, which automates the process of testing each component in isolation by loading the necessary scripts and styles into an empty page. The two utility functions `loadComponents` and `loadTemplate` are key to this process, allowing developers to create tests for every component in their library or page/user story with minimal code duplication. By running these tests locally, developers can get fast feedback and fix errors before even pushing changes, resulting in better quality and time savings. However, there is still room for improvement, including automating test generation, protecting against flakiness, integrating and optimizing tests in GitHub Actions, and developing a debugging mode for visual tests.

The Java SDK for Vonage has undergone significant changes with the latest version, focusing on improving security, adding new features such as the Messages API, and removing deprecated functionality. Versions before 6.4.2 are vulnerable to over 50 CVE security vulnerabilities due to outdated dependencies. The SDK now uses a more secure library for JSON serialization and has been updated to reflect changes in the API specifications. New features include support for the Pricing API endpoint and premium text-to-speech capabilities. Deprecations include the removal of the SMS Search API, legacy text-to-speech voiceName field, and internal refactoring to make classes package-private. The SDK also includes fixes and enhancements for issues such as missing fields, incorrect deserialization, and improved documentation. The roadmap includes the integration of video functionality into the core SDKs, with a focus on implementing the new Video API in beta releases.

Kiran Krishnan is an open-source enthusiast who recently integrated Vonage into Supabase, a popular open-source project. Kiran has been working as a software engineer at BoxyHQ, where he enjoys coding in JavaScript and writing technical blog posts. He has also worked on other open-source projects such as SAML Jackson and Gotrue. Kiran's experience with Vonage APIs was positive, and he found the API documentation and examples to be helpful in understanding how to implement it in his code. He is excited about new developments in tech, including TypeScript and Next.js, and hopes to contribute more to the open-source community in the coming years.

The Experience Composer API allows developers to capture their website's layout as a stream published to a Vonage Video API session, enabling them to create a customized experience with logos, web components, and formatted layouts. This tool is particularly useful for educational applications where sharing components such as whiteboards or slides is essential. The API can be used to start an Experience Composer, which subscribes to the user's website layout and publishes it to a Vonage Video API session, allowing it to be archived and viewed in the future. The API also provides options to stop the stream and archive, enabling developers to manage their experience composer streams effectively. By using this tool, developers can create innovative applications that capture the full experience of their websites and provide users with an enhanced experience.

The tutorial aims to create a web application that allows students to reserve office hour time slots with their professors, using Node.js, Express, SQLite, and the Vonage Messages API. The application will have three HTML templates: an input form for student information, an error page for handling invalid data, and a confirmation page for successful reservations. The backend will be implemented using Express and SQLite to store reservation requests in a database. When a reservation is successfully processed, a text message will be sent to the student's phone number using Vonage's Messaging API.

Vonage is partnering with Salesforce as an exclusive Innovator Sponsor for Dreamforce 2022, a major tech event, to offer developers a range of experiences and opportunities without the need for a ticket. The Vonage team will be at the Campground stand, number 1107, where attendees can meet the team, experience API demos, and book meetings or chat about potential use cases. Additionally, there's an exclusive shirt designed for developers at the Trailblazer section's Vonage Kiosk, as well as a chance to design personalized backpacks. The Vonage Hub, located on the 3rd floor of the nearby InterContinental Hotel, offers a networking and discovery experience with free snacks, workshops, and live sessions hosted by Chris Tankersley. There's also a raffle for RayBan Stories smart wear technology and $10 free credit for API accounts for those who register for a free Vonage API Developer account at any of the locations. The Vonage Party is also an event to attend, featuring good music, drinks, and networking opportunities.

This is a summary of creating a video watch party application using Ruby on Rails with Vonage Video API and the Video Express library. The article covers building helper components, organizing HTML and JS into components, and styling the toolbar. It also includes code examples for each component and explains how to use the Vonage Video API to implement features such as screen sharing, audio input/output, and video camera control.

ruby Ruby on Rails is being used as a full-stack application to build a video conferencing platform with Vonage Video Express and UI Toolkit Vivid. The platform allows users to create watch parties, join existing ones, and share screens. It also includes features like moderator controls, participant muting, and audio input selection. The application uses the "Convention Over Configuration" philosophy of Rails and leverages the strengths of both frameworks to provide a robust and scalable solution. With this tutorial, developers can build their own video conferencing platform using Ruby on Rails and Vonage Video Express.

The Python SDK has been updated to version 3.0.0, with most of the changes being internal refactoring to lay the groundwork for future enhancements. The main structural change is the organization of methods into separate classes and modules, making it clearer which API is being called and allowing for more flexible authentication options. Duplications in code have been consolidated, and deprecated code has been removed, resulting in breaking changes. New features include optional parameters to customize timeout, retries, and pooling options for the entire session with a Vonage client, as well as enhancements to the Pricing API, including new methods and the ability to query based on SMS or voice traffic. The SDK now follows a more modular approach, with methods related to specific APIs being called from those particular modules. New client connection options have also been added, allowing for more control over request timing and retries.

The Vonage Messages v1 API has been promoted to General Availability status, and its implementation in the server SDKs is being worked on by the Developer Relations Tooling Team. The goal is to ensure each SDK feels idiomatic, with a focus on consistency and correctness. The Java SDK's implementation of the Messages API is discussed, including the data model, validation logic, and builder pattern used to emulate named arguments. The design aims to prevent invalid message construction, making it difficult to "misuse" the API, while still allowing for easy discoverability and usage through a strongly typed language like Java. This approach provides a better user experience compared to using the API directly with tools like cURL, which requires manual knowledge of the schema and can be error-prone.

The text discusses the use of the Builder pattern in object-oriented languages, particularly in Java, to control object construction. The author argues that this pattern is useful when there are multiple optional parameters and a complex inheritance hierarchy involved. They provide an example from the Vonage Java SDK, where a class `MessageRequest` has several subclasses with their own builders, which are used to construct instances of these classes. The builder pattern helps to ensure that the correct type is returned regardless of the order in which methods are called on the builder, and it also allows for fluent method chaining. However, the author notes that this approach can be verbose and requires careful consideration of the inheritance hierarchy involved.

Vonage AI Studio is a no-code/low-code platform for creating conversational flows across various communication channels, utilizing a drag-and-drop interface to connect modules and actions into complex flows that can automate processes and connect to many different services. The platform's conversational flows are built on Vonage AI's proprietary natural language understanding (NLU) algorithms, enabling conversational interactions where users can communicate in 'natural language' without being required to use specific keywords or formulate their questions in a particular way. Agents, Flows, Conversation Nodes, and other node types are used to create these conversational flows, which can be customized using various settings and parameters. AI Studio provides a range of features, including text-to-speech capabilities, classification nodes, conditions nodes, set parameter nodes, send SMS nodes, custom code nodes, context switch nodes, and end call nodes, allowing users to build powerful and fully-featured conversation flows with zero programming knowledge. The platform is available for use in Developer Preview and has recently become generally available, making it an exciting development in the field of conversational AI.

Helena has joined Vonage as a Technical Writer with a background in Computer Science from the University of Birmingham, where she studied Cyber Security, programming, and AI/Machine Learning. She previously worked at BT Security for nearly 3 years before transitioning to the technical writing role, during which time she also founded HackTheMidlands, a hackathon for young developers. In her free time, Helena enjoys attending theatre shows, playing video and board games, baking, and collecting vinyl records. She is excited to be part of the Vonage team and looks forward to the adventure ahead.