July 2018 Summaries

This demo showcases the use of Twilio Sync for IoT, a real-time collaboration platform that enables developers to build end-to-end experiences with their embedded and wearable devices. The project uses an ESP32 board with a humidity and temperature sensor, JavaScript, Node.js, and the Twilio Sync Rest API to interact with the device and web server simultaneously. It demonstrates how to set up a demo system, including a browser interface and an ESP32 board, and how to use the Twilio Sync JavaScript Client Library to create observers of the data published by the ESP32. The project also shows how to call the Twilio Sync Rest API from a server-side application using Express.js, and how to publish sensor data from the ESP32 to a Twilio Sync document. Additionally, it demonstrates bidirectional communication between the device and the web app, allowing the web app to send messages back to the device.

Twilio has updated its pricing for Programmable Video, introducing a simplified on-demand pricing model that includes bandwidth. The new pricing is active now for all new Twilio Video customers and will be phased in for existing customers by the end of January 2019. Group Rooms can accommodate up to 50 participants and are priced at $0.01 per participant per minute, including bandwidth, while Small Group Rooms support up to four simultaneous participants at a lower rate of $0.004 per participant per minute, including bandwidth. The company also offers significant discounts for custom pricing and invites developers to showcase their applications built with Programmable Video at its annual Customer and Developer Conference in San Francisco.

There are some features of iOS apps that don't work from the iOS simulator, requiring testing and debugging using a real device. To run an Xcode project on an iPhone or other iOS device, select the device as the "Simulator" in Xcode and unlock it to allow app installation. Troubleshooting common errors such as signing issues, locked devices, and busy iPhones can be resolved by resetting location and privacy settings, unplugging and plugging back in the device, and waiting for a short period of time. With these steps and tips, developers can successfully test their iOS applications on real devices to ensure compatibility and functionality.

Twilio has been recognized for its commitment to data protection by receiving approval from EU Data Protection Authorities for its Binding Corporate Rules (BCRs), a rigorous regulatory standard for handling customer personal data. The company's BCRs demonstrate its dedication to protecting customers' data, with a focus on GDPR compliance and the ability to transfer personal data across borders in accordance with EU law. Twilio's leadership emphasizes trust as a key selling point in the cloud, highlighting the importance of data privacy and the company's efforts to set a high standard for data protection.

SendGrid's dynamic templates for transactional emails offer a streamlined solution for developers and marketers by supporting Handlebars syntax, which allows for advanced templating capabilities such as iterating over lists, conditionals, and object replacement. This new feature, available via version 3 of the SendGrid API, enhances the efficiency of updating email templates by removing the need to modify code directly, thus reducing the risk and workload associated with deploying changes. Users can preview their emails using a Test Data tab, which renders a side-by-side comparison of the template with the desired data, ensuring confidence in the final output. This development not only minimizes disruptions in workflow by making templates readily accessible to team members but also allows for a more focused approach to managing email communications. Existing templates remain functional under the "Legacy" tab, and users are encouraged to explore the new features to optimize their transactional email strategy.

The SIGNAL 2018 Scholarship is a program that aims to make the communications industry more accessible and inclusive, by providing opportunities for individuals from underrepresented groups in tech to attend the annual SIGNAL event. The scholarship covers the cost of conference tickets and may also include travel and lodging assistance on a limited basis. Eligibility includes women, people of color, LGBTQIA individuals, those with disabilities, veterans, and others from underrepresented backgrounds in tech. To apply, applicants must submit a short paragraph explaining why they want to attend the event and if they require any additional support. The application deadline is September 3rd, 2018.

Twilio is a communication platform that allows developers to make phone calls and send text messages using its API. To demonstrate this, the article uses PHP and the Twilio REST client to create a phone call and send a text message. The process involves authenticating with Twilio's account credentials, creating instructions using TwiML (a subset of XML), and sending these instructions to Twilio's API. The article provides example code for both making a call and sending a text, showcasing how to customize the content of the calls and texts using different URLs. With this setup, developers can now communicate more effectively with notifications, updates, reminders, and other programmable communications.

The iOS app can display a pre-composed message for the user to send using MFMessageComposeViewController. The user's phone number is not required, but if programmatically sending an SMS from a different phone number is desired, Swift and Twilio can be used. To get started, Xcode 9 and Swift 4 are needed, and a new project should be created with the "Single View App" option. A ViewController class must conform to MFMessageComposeViewControllerDelegate protocol and add a stub method. A function called displayMessageInterface is added to present the message composition interface with a pre-populated body and recipient number. The function is then wired up to a button in Main.storyboard, allowing it to be executed when pressed.

A Python script using BeautifulSoup and Requests libraries to detect link rot in a website, specifically the Full Stack Python repository, by aggregating all links from the site, checking each URL for bad responses, and writing results to an output file. The script uses multiple approaches to improve accuracy, including parsing Markdown and HTML files, extracting URLs with BeautifulSoup, and using asynchronous processing with `concurrent.futures` to bypass I/O bottlenecks. The script can be run by executing Python and validates its functionality without relying on external tools or data structures, making it a self-contained solution for detecting link rot in websites.

The author created a World Cup bot using Python, Twilio SMS, and Slack APIs to provide real-time updates to fans during the 2018 World Cup. The bot uses Flask as the web microframework, Slack's Real Time Messaging API, and Twilio's Messaging Service to send SMS updates to subscribers. The bot is controlled by a Slack bot that posts updates to a designated channel and can be subscribed to via an HTTP POST request. The author also wrote a notifier module to retrieve live match data from the FIFA World Cup API and post updates to both Slack and SMS subscribers. The code includes error handling, validation of phone numbers, and logging to files for persistent storage of match data and subscriber information.

The project is a Node.js application that uses Twilio, Firebase, and Twitter to track progress on the #100DaysOfCode challenge. The app receives text messages from Twilio, extracts the message content, calculates the current day count, posts the tweet to Twitter, and stores it in a Firebase database. To set up the project, users need to install Node.js, npm, ngrok, and create accounts with Twilio, Twitter, and Firebase. They also need to generate API keys and store them in an environment file (.env). The app uses ngrok to expose the local server and configure Twilio numbers. Users can test the app by sending a text message to their Twilio phone number and watching it appear on Twitter.

As SaraAnn Stanway joined Twilio's Cloud Orchestration team, she was tasked with learning about distributed systems and working on the company's automated host remediation system called Lazarus. Initially, she had no experience in this area but expressed her eagerness to learn. With guidance from her mentor Mitch, she delved into the world of site reliability and quickly made progress, even pushing out her first pull requests. As she worked on projects related to scaling up or down, she encountered complex issues like the need for a full-system kill switch. To address this, SaraAnn implemented a solution that reduced cross-region requests, enabling the system to handle emergencies more efficiently. Throughout her internship, she faced new challenges and grew both personally and professionally, learning valuable lessons about growth, belonging, and empowerment in the workplace.

Twilio Segment's journey from a microservices architecture to a monolithic system highlights the complexities and trade-offs involved in choosing the right software architecture for specific needs. Initially, microservices offered modularity and isolation of server-side destinations, but as the number of services and repos grew, operational overhead and testing challenges hindered developer productivity. The microservices setup led to issues like head-of-line blocking, dependency version divergence, and inefficient resource scaling, prompting a reevaluation. By consolidating hundreds of microservices into a single service and moving all code into one monorepo, Twilio Segment improved developer efficiency, reduced operational strain, and streamlined dependency management. This transition required robust testing solutions, such as Traffic Recorder, to ensure reliability and consistency across destinations. While acknowledging the trade-offs, such as fault isolation challenges and less effective in-memory caching, the move to a monolithic architecture ultimately enhanced scalability and reduced technical debt, demonstrating that the choice between microservices and monoliths depends heavily on the specific context and requirements of the system.

Twilio has added support for Announcements in its Conference service, allowing developers to play or say messages into a conference using one API call, simplifying the process and improving compliance with legal requirements such as playing disclaimers to participants when calls are being recorded. The new feature adds two optional parameters to the Conference and Participant API, including `AnnounceUrl` for specifying a URL for the announcement and `AnnounceMethod` for specifying the HTTP method used to send the announcement. This update is expected to improve the usability of the service and enable developers to build more advanced applications using Twilio's Conference feature.

This tutorial provides a step-by-step guide on implementing phone verification using Twilio's Verify API in an iOS application developed with Swift. The process involves setting up a backend server, creating a Verify Service, and integrating the Twilio API into the app. The user is prompted to enter their country code and phone number, which are then used to initiate the verification process via SMS. Upon receiving the verification code, the user enters it into the app, which sends the code back to the Verify API for validation. If the code is valid, the user is taken to a VerificationResultViewController displaying a success message; otherwise, an error message is displayed. The tutorial concludes by outlining additional customizations and next steps for enhancing the verification flow.

Connecting Twilio Studio with Salesforce CRM allows for real-time customer context access, enabling tailored interactions and intelligent routing. To achieve this, users need to set up a Salesforce API connection, create a certificate, and configure a connected app with OAuth settings. They then use Twilio Functions to host Node.js code that requests call routing data from Salesforce, using the Functions widget's ability to run JavaScript code directly on Twilio. The code retrieves customer information based on phone number and returns it as a JSON object, which is then parsed and used in a Studio flow to greet customers or play a message for new callers. Once set up, the flow can be integrated into a call center environment, enabling personalized interactions and improved customer experiences.