It's nice that you looked at the source, and if you were a manager of an established site or app it would make sense to be concerned about inline CSS there because it's a maintainability nightmare, but frankly I'm sure these guys have other stuff to be working on. I will be the first to admit to dropping in some inline CSS on occasion, and if it helps get things out the door then I'm all for it.
I'm for dropping in inline CSS for quick fixes too. But I didn't think using inline CSS everywhere was something people still do today.
(To be honest, I looked at the source because the rendering was odd on my computer, and I wanted to know if it was my you-should-not-pass corporate firewall which was blocking something, or just a it-renders-better-on-chrome problem)
We do have a roadmap - not with public dates, but items for the near term future include automatic exporting of your contacts from your current solution and better web management tools. The beauty of being a paid for solution is we can work to implement feature requests made by our customers rather than worrying about selling ads or finding a business model.
It's nice that you looked at the source, and if you were a manager of an established site or app it would make sense to be concerned about inline CSS there because it's a maintainability nightmare, but frankly I'm sure these guys have other stuff to be working on. I will be the first to admit to dropping in some inline CSS on occasion, and if it helps get things out the door then I'm all for it.