2016 Hackathon Review
This year we challenged you to “Build Something Awesome” with SparkPost. To motivate you further, we sponsored 5 different Hackathons across the USA with cash and prizes. We also sent along our own engineers in order to mentor those who accepted our challenge. As a result, the response was incredible and we’d like to recognize the winning teams.
We started the year in February at the Developer Week Hackathon in San Francisco. We selected three teams that demonstrated the best use of our Inbound Email, Data & Analytics, and the SparkPost Heroku Add-on.
Best Use of Data & Analytics
Kaushik Ashodiya and his son created SparkPost ONTAP, combining our data with Net Cloud ONTAP to store webhook and campaign data. It allowed users to view or edit historical campaigns, as well as replicate the storage for disaster recovery and availability purposes.
Best Use of SparkPost Heroku Add-on
The team comprised of George Portillo, Stephen Fuller, Victor Sanchez, and Sal Casillas created Grab & Go, an application that leveraged the SparkPost Heroku Add-on to help alleviate the long lines found at the local food trucks. Their solution uses our transactional email to alert customers when their food is ready for pickup after placing an online order.
Best Use of Inbound Email
Marlon Frausto, Anna Wu, Ravender Virk, and Jigesh Parekh set out to tackle San Francisco’s affordable housing dilemma and created DwellWell. They used our Inbound Email to set up a double blind communication channel, allowing people to request information about a particular housing option with some anonymity. The DwellWell team has since continued their partnership with SparkPost to create PublicBNB.
In early March, we headed to Rochester Institute of Technology in New York for BrickHack. After 24 hours of hacking, we selected UBinE by Stephen James as the Best Use of the SparkPost API. This application uses transactional email to assist in planning, tracking, and notifying students of campus events.
In April, we headed to Bitcamp at the University of Maryland. Because of our close proximity, we got to send multiple engineers of our own to mentor at this 36 hour hackathon. Henry Saniuk, Sneha Vaswani, and Stuart Olivera won our “Build Something Awesome using SparkPost” challenge with their PiggyPennies application. This application made use of our inbound and transactional email and the CapitalOne API to while helping friends save money together.
After a long summer break, we headed to the University of California San Diego’s SDHacks, a 36 hour hackathon. At this event, Kevin Burns and Jack Zeiders had some fun with SparkPost and created an email based gaming service called QuibbleMail. Using only your email, you can challenge a friend to a game of Chess or Tic-Tac-Toe. Their use of SparkPost inbound and transactional email allows you to play without leaving your email client.
MLH Prime Southwest Regional
Finally, we wrapped up 2016 in Austin, where Major League Hacking pulled together the region’s best hackers for 24 hours. Bailey Breaux, Ali de Jong, Yuriy Minin, and Patrick Edelen blew us away with Mochi, their Jibo robot integration for patient care. The team used SparkPost’s inbound and transactional email to empower Mochi to contact a patient’s family via email and read aloud any replies.
At each event, the response to our challenges was amazing. So many of you Built Something Awesome and we thank you. As a result, we’ll be back out there in 2017 and we’ll be sure to keep you updated. Our first stop will be a return to Rochester in February for BrickHack 3. Because we take your feedback into account, we’d love to hear what events you’d like us to attend. You can chat with us on our community slack or send us a tweet @SparkPostDev.
So, what’d you think of our 2016 hackathon review? What were your favorite hackathons from 2016? Any hackathons on the agenda for 2017 yet? Leave us a comment below.
The Community Driven Development Approach
April 2015 was an exciting time to be an engineer at SparkPost. Our service had just launched. We were seeing the results of all the hard work and dedication from previous quarters spent building our functionality, infrastructure, and teams.
Fast-forward to late February 2016. SparkPost had been generally available for ten months. Our community was growing steadily. We continued to make refinements to our service and infrastructure. We didn’t know it at the time, but MailChimp had just announced some important changes to Mandrill that would change the way we interact with our community and how we improve and support our product.
In the days following the announcement, we’d go on to set up our community Slack and revise our product and engineering processes to embrace community driven development. We used the feedback and experiences to drive our decision making processes to execute on what really makes our community successful.
Channels for information
Several mechanisms for feedback from our community exist at SparkPost. I mentioned our community Slack. There, our community has access to SparkPost team members and, more importantly, each other. We learn from you not only through direct interaction but by observing, listening, and taking notes. Any member of our team can take feedback from community Slack and post it directly to a feedback channel in our internal Slack. There, our engineers, product managers, and executives have direct access to your comments.
Support tickets and Github issues are another essential method for understanding ways we can make our community’s lives easier. Our support team does a great job of escalating issues internally to our engineering team as well as bringing up issues that are occurring repeatedly and brainstorming ways to address. Github issues allow us to understand how our client libraries are being used and where we can make improvements.
Attending meet-ups, conferences, and hackathons has been a major source of learning for us too. We get to spend quality time face-to-face with our community, learn about how you use SparkPost and what improvements might help you and your business be more successful. After each event we make a point to share learnings internally so that we can discuss ideas and issues that arise during our conversations with attendees.
What happens behind the scenes?
Collecting all this valuable input wouldn’t mean much if we didn’t act on it. In the past three quarters we’ve acted on a little over 50 items that were a direct result of the information we gathered from our community. These smaller items are what we consider quick wins – things like updating language in our UI, improving documentation, bug fixes, and minor feature improvements. Here are some examples:
- Click to see event details in Message Events UI
- Allow customers to clone Templates in UI
- Create code samples for cc/bcc in the client libraries
- Surface all 4xx API errors in the web UI
- Add information about rate limiting and error responses to the docs
- Fix click tracking on <area> elements
Additionally, the engineering, product, and support teams meet weekly to discuss customer impacting issues, solutions, and action items. Like many software companies, we also have a prioritized list of larger initiatives that we work our way through. Some examples of work completed from the past few quarters include:
- Create a subaccounts API and related UI functionality
- Allow users to purchase dedicated IPs
- Launch the DKIM validator
- Implement CSS inlining for templates
- Refactor the PHP client library for maintainability
Prioritization of new features and improvements is a constant work in progress. We do our best to compile all of the great feedback we receive and maintain a balance between addressing current issues and the planning and execution of new functionality and improvements. Some additional items we’ve heard our community request include:
- Deliver webhooks by subaccount
- View the contents of sent emails in the UI
- View billing history in the UI
- Add the ability to use a test API key
- Reporting by geography in the UI
- Support for stored templates with subaccounts
Lastly, the best way to stay up-to-date with what’s new as well as fixes we deploy is to join the #announcements channel in our community Slack or keep an eye on our change log article. We update both every Friday when we deploy changes that we want to make sure you know about.
Onward & Upward
With 2017 nearly upon us, we’re looking forward to implementing some of the improvements and features you’ve told us are important to you. Our community plays a major role in the development and evolution of SparkPost. We love to hear from you, so keep the feedback coming. And keep pushing us to deliver the best service we can.
—Rich Leland, Director of Growth Engineering
ps: Thoughts on community driven development? How do your teams prioritize and process feedback? Leave us a comment below.
SparkPost is built by and for developers and as such, we value your input. We showed you our true colors during the Mandrill migration and we’ve added lots of new features and enhancements based on your suggestions. We’ve also opened up a communication stream for you to share feedback with us on a regular basis. Now that we’ve gotten to know who you are, we want to pull back the curtain a little and introduce ourselves.
Mark down September 21st on your calendar to hang out with us LIVE and get to know our Dev Relations Team in our new All Things Delivered live stream. In our first live stream find out who we are, what we do, and why we’re passionate about delivering the best email cloud service on the planet to you, our community.
Starting in September, on the third Wednesday of every month, we’ll be coming to you LIVE for 30 minutes to discuss what our team is working on and walk you through our client libraries, the SparkPost CLI, or other technical topics. We’ll also be covering common questions and issues that you, our community members, have brought to our attention; helping you troubleshoot issues and get a better understanding of how to look for information that will help you do your job better and land your messages in the inbox.
We’ll also be taking questions from you in real-time via the #SparkPostLive hashtag on Twitter and via the SparkPostLive channel in our Community Slack.
Here are some dates to add to your calendar for All Things Delivered:
- Sept 21, Dev Relations team: Who, What and Why – Add to Google calendar
- October 19, SparkPost API basics & CLI – Add to Google calendar
- November 16, SparkPost Client Libraries – Add to Google calendar
- December 14, Community Driven Roadmap – Add to Google calendar
How can you participate?
If you’re unable to participate live, you can always watch the playback on our YouTube channel.
Looking forward to seeing you soon!