Vector art produces bad results. So, no thanks. The problem is the ridiculous number of varying Android resolutions. There, we have to be flexible. But still not going to use vectors.
> This post should serve as a chance for all of you to learn why you are often Balkanized in business decisions and business structures. It should serve as a chance for you all to show that you actually understand business realities and can propose rational arguments.
Heh. Because "business decisions" are always so rational, demonstrating a genuine understanding of the product and what the people that actually are going to use it will want from it?
> And remember... this is Hacker News. We work at Start-ups. We believe in shipping early, shipping often, and iterating to improve. Your answers and perspective MUST work within this construct or we will ignore you (and you will thus teach all of us that designers are, in fact, crazy).
Sigh. Some of us want to ship genuinely high-quality products, not ship whatever we manage to shit out every other day.
If my users are noticing my bugs (or design faults), that adds up to an aggregate middling opinion of my product. One thing you got right -- I do want to be Apple, not Time Warner Cable.
> Ball's in your court.
Not really. You sound like someone that will willingly produce mediocre products, and I don't really know why anyone interested in excellence (and the rewards that it brings) would want to work with you. So this becomes a self-fulfilling prophesy for yourself.
2647 connections per server per second is pretty abysmal for modern server hardware, especially if you had to rely on a whole bunch of caching front-end complication and proxy web servers to make it happen.