Update 10:57am March 29: The Splitwise Venmo iOS integration has been re-enabled! To use it please upgrade to the latest versions of Venmo and Splitwise. If you need any assistance, please send a note to firstname.lastname@example.org.
Update 2:55pm March 28: The iPhone integration will be re-enabled tomorrow March 29. Please make sure you’ve updated to Venmo version 7.0.1 and Splitwise version 4.4.7. If you need to Settle Up today, please log into our website (splitwise.com); the Splitwise Venmo web integration is working at this time. Or you can send your payment via Venmo directly and use our “Record a cash payment” feature to subsequently update your balance in Splitwise.
Update 9:30am March 22: Venmo is testing a release that will fix this issue.
Update 5:15pm March 21: Android Venmo payments are back to working normally.
Venmo released an iPhone update yesterday (version 7.0) that is preventing the Splitwise integration from working properly with the Venmo iPhone app. We are working with Venmo to resolve the issue and will post here with more information soon.
In the meantime, we’ve temporarily disabled the Venmo button in the Splitwise app until this is resolved (on both iPhone and Android).
Venmo payments made on the Splitwise Android app and website are not affected. Android users should have the Venmo integration re-enabled by the end of the day. If you need help with your account, please email us at email@example.com. Thanks for your patience.
Our whole team has been crafting a major new version of Splitwise for iPhone over the past few months. We’re excited to announce that it went live on the App Store earlier this morning.
We’ve focused on improving the two most important parts of Splitwise: adding bills and checking balances. The “add bill” form has been streamlined into a single screen, and the new navigation tab bar makes it easier to see balances with both groups and friends.
In addition to the major changes, we’ve included popularly requested features like spending totals for groups and exporting to spreadsheet. We’ve also added many more subtle improvements and bug fixes that greatly improve Splitwise for iOS.
Splitwise is proud to announce our Apple Watch app! The Watch app is an extremely easy way to share expenses and check your balance, without even pulling your phone out of your pocket.
The key feature of Splitwise for Apple Watch is the ability to dictate new expenses out loud. Splitwise can understand your natural English sentence, like “I owe Zoe $40 for dinner.” After you dictate, Splitwise turns the phrase or sentence into a Splitwise expense using the same technology from the “Quick-Add” feature.
I’m happy to announce today that Splitwise has raised $1.4MM in new seed funding from leading tech investors. Raising outside money means we can continue to invest in building the world’s best product for reducing the stress of money in relationships. Hooray!
We’re using that money to hire talented people to help us make Splitwise even better. If you are a software engineer who wants to work on a product you love, please hop on over to our jobs page.
Splitwise has been a labor of love for the founders for nearly four years. This year has been incredible: Splitwise users have shared over $1B in expenses so far in 2014, just counting US dollars. We’ve been featured alongside companies with dozens or hundreds of engineers. I’ve found that most users are surprised to learn we currently have only two engineers, and that our CTO is also our lead designer.
Our goal for Splitwise is to remove the stress of sharing money in our most important relationships. How does this translate into a product roadmap? While still being annoyingly vague, allow me to explain our priorities for the coming years.
On April 7th, a major web vulnerability called “Heartbleed” was disclosed to the internet. This vulnerability affected a popular security library called OpenSSL, and as a result it affected the security of a large number of sites on the internet, including Splitwise. (A good rundown of who was affected can be found here.)
Shortly after noon on April 8th, the bug was patched on all of our servers. We also issued a new SSL certificate for splitwise.com and initiated the expiration of our old SSL certificate. As a result, we are no longer vulnerable to Heartbleed.
We have no reason to believe that any Splitwise user data was compromised via the Heartbleed vulnerability or that we were the target of an attack, but we are continuing to monitor for any unusual behavior. In addition, we’ve taken this opportunity to implement a few additional security measures, to update passwords for important server components, and to generally review how we respond to security issues.
1. The Heartbleed bug was patched shortly after 12pm EDT on Tuesday, April 8th. We issued new a SSL certificate a few hours later, and also revoked our old certificate.
2. As a precaution, we are logging out all users who visited the Splitwise website on April 7th and 8th.
3. Changing your password is recommended as a precaution, especially for users who logged in or created an account during the affected period. You can also log out of all your existing Splitwise sessions by clicking here.
2010 US Population Density, By Zip Code, in XLS and CSV
2007-2011 US Unemployment Rate By Zip Code, also in XLS or CSV
Unemployment and population density are probably two of the most important local statistics you might hear quoted about a city or town. Our US Population by Zip Code post from September has gotten rather popular, and a polite commenter requested population density and unemployment rate. So here they are, totally free and in the public domain, in two different formats (see above).
How did I get this data? Two different Census APIs (the Decennial Census 2010 and the ACS 5-year 2007-2011), combined with the square-footage by ZCTA listings from the 2013 U.S. Gazetteer Files.
I was planning to use this post to document my methods and send everyone on their own journey through the data, but it got too long and I realized that I wanted to talk a more systematic approach. In a follow up post, I will explain how to pull Census data yourself for different variables at different geographical resolution. But if you need a jump start now, my first and most helpful guide was the National Civic Day Of Hacking support slides.