If you’re a frequent Formspring user, you may have recently noticed that Formspring was down for quite a whiles, and of course there’s an interesting and technical blog post over on the Formspring blog talking about what went wrong, and how they fixed it – an interesting read of you’re into web tech.
Of course, this presented a new issue for me, with Springy!. When designing it, I had already taken into some error handling methods to make sure you never have to see any crashes. One of them being – before each and every API request is fired, we check to see whether we first have an active network connection. If we don’t, we show an Error Message instead informing you there is no valid network connection. If we do however, the request fires – and from there on in we expect to get a response from the server, and we handle it accordingly. Simples.
What I didn’t take into account however, was what would happen when Formspring itself was down, leading to no response from the server… and through some series of events, basically, we end up with a crash! It’s a rare occurrence, but it’s still unhelpful.
So, there’s now a fix in place for that! If Formspring is down during login, it will now inform you and not let you login. Not a best fix, but it works, and it’s something you’re never likely to see. But just in case 
Another minor change in Springy! 1.1 – there’s now a button to forward you to my Formspring profile to ask me questions on the About page!
(Secret: Clicking on “created by johnny westlake” also does this, and always has!)
Springy! 1.1 will include both of these changes, and some new artwork hopefully, and I’m intending to submit it within the next few days. Till then, enjoy Springy!
