So you’ve heard about this Recapd application by now, right? If not, Recapd is one of the industry leading real-time caption delivery services. What you probably didn’t know is what lies beneath this powerful application. Since its inception, we’ve been growing the API base so other developers can dynamically manipulate the embedded widget, and also, gather information about an event from our servers. Guess what? The wait is over!

When I was conceptualizing how FW Toolkit (FWTK) would function, I envisioned a library robust, powerful, agile, but really easy to incorporate into anyone of our projects. Although, the library did exactly as intended, a component was left out due to my own skepticism. FWTK, as a library, comes equipped with an arsenal of tools created by our developers, but the few external libraries we depended on, needed to be loaded separately before they were accessible (Errrr). I wasn’t pleased by this process, but the overall library was a success so I was content.

I woke up this morning to the dreaded alert of a day full of scheduled meetings. Just the thought of four in one day was nothing to anticipate and sent a chill down my spine. The first meeting started later than scheduled, but with free lunch included, who could complain? The meeting was about application integration and our head of RnD, Jose Burgos, Jr. discussed how we could improve communication by integrating our Basecamp and Beanstalk accounts…

Over the past few months, the Recap’d team has been extremely busy updating and adding core components for the service. The recent updates make the service even better for our clients! Many of the updates are “under the hood,” which our clients do not have knowledge of, until now.

Over the past few months we have been using Akismet on our blogs and forms and if you haven’t noticed – no spam! We are very pleased so far with how it has been working for us.

We recently adopted the Sandbox pattern that will help to organize our code and reduce the chance of code collision.