sean_lynch

25 ms·

31.
by sean_lynch 15y ago
We're not staying in the same space so I don't think we'll want to spam our current set of beta testers with our new product. If you track me down on Twitter though (sean_lynch), I'll send you a heads up when we launch.
32.
by sean_lynch 15y ago
I've got all the parts of a good postmortem post floating around in my head. Unfortunately, it's probably going to have to wait a few weeks while we tackle our new product.
33.
by sean_lynch 15y ago
Yeah, it sucks :( If there's anything we can do to help transfer your data back, please let us know.
34.
by sean_lynch 15y ago
Both an Android and an iPhone versions are looking for beta testers :)
35.
by sean_lynch 15y ago
We're both very big Billmonk fans, but unfortunately the application hasn't seen very much improvement since it was acquired a few years ago. Splitterbug helps you solve the same problem using some very cool tech that Billmonk didn't have a
36.
by sean_lynch 15y ago
Good eye :) The web version lacks a lot of optimizations we were able to add on the client though. If you're excited to start using the thing now, shoot me an email at support [at] splitterbug.com and let me know what device flavor you pre
37.
by sean_lynch 15y ago
We have both iPhone and Android clients and we're looking for beta testers for both.
38.
by sean_lynch 15y ago
Launched, although not particularly large (www.splitterbug.com). What becomes difficult to manage when you introduce customer data?
39.
by sean_lynch 15y ago
Disclaimer: In a past life I was a PM on App Engine (and not surprisingly, we're using it for our new company), so the following comment has a fairly high bias. Though it doesn't have the same HN buzz that Heroku does, App Engine has a fair
40.
by sean_lynch 16y ago
Member of the App Engine team here. Yes, to confirm, this is not an abstraction on the current Datastore but a separate "real-deal" service.
41.
by sean_lynch 16y ago
Agreed and bonus points for using a map of Vancouver :)
42.
by sean_lynch 16y ago
Email sent. Google here, confirming this is an issue with the Users API on App Engine. On-call team is working on the fix now. Edit: As of 12:30PM PST, we are now rolling out the fix. This should be relatively instantaneous.