Buddy makes IoT data usable. We've created technology that pipes raw data generated from IoT or "connected" devices straight into business intelligence tools like SAP, Salesforce.com, ZenDesk, Geckoboard, Tableau, etc... with no custom hardware, firmware or special connectivity.
We do this by offering a cloud service that accepts data from any kind of connected device. Buddy solves the problem connected device vendors have of ingesting massive amounts of device data into their existing BI toolsets (none of which natively support IoT devices as data sources).
In as little as three lines of code on any connected device, we can:
1) Host the telemetry data on servers in your choice of the US, EU, China, Brazil and soon Australia
2) Provide real-time dashboards showing how devices are performing
3) Perform queries on the data and then output into any BI tool-set a customer may use.
Whatever your BI software - Buddy connects it with the connected devices you manufacture or manage.
This project is a sales tool and demonstration that turns the viewer's phone into a mock connected device; the goal is to show how easy it is to get a… · More bunch of cool data out of your device using the Buddy Platform. I designed and built the UI, edited the copy on the page, and redid the branding to match our internal brand guide.
One of my first tasks at Buddy was to update and maintain the documentation. After my initial pass, I decided to redesign the look and feel of the… · More documentation. I wanted each document to feel like a piece of paper (keeping with the material trend) and I decided to make each API an entire page instead of separating out every HTTP verb for each end point. I also designed and wrote the code generator so visitors can copy and paste code samples from the site directly into their projects, lowering the barrier of entry into the platform.
The Buddy developer portal is the primary dashboard for the Buddy platform. I spent a significant amount of time going through each page to make sure the… · More copy, experience, and layout of each page is consistent and is mobile friendly. More recently, I reworked how we welcome a user into the platform by building overlays for each graph that disappear when data is present. This fixed two issues: the overlays fixed a "popping" issue we had where the empty graphs would display momentarily then disappear. They also act as a call to action, encouraging the user to make API calls with explanations of what they can expect to see in the graphs.