Well it's my experience that managers almost never think about the product or the customer, and …

> I've never once had a manager say anything along the lines of "I just think we're building a bad experience if we release this early." Then perhaps you had less-than-great managers, and I could think of a variety of reasons for that. Maybe it was as simple as you claim: no consideration was made to introducing an undercooked user experience. But if a software development manager is green lighting that, likely causing more work for customer service and perhaps sales, I would hope there’s more to the story than that. Maybe this manager didn’t communicate why releasing a bad experience by a specific date was, perhaps, mandatory to fulfill a contractual obligation. Or maybe you were not able to sort that out from the limited amount of information they gave you. Maybe they didn’t see the bad UX as truly as bad as you, and perhaps your team, thought it was. Maybe where you thought the featur…

Google deciding to give everyone literally 100x or 66x more free space than their competitors did manage to acquire a lot of the email market, which meant non-negligible hardware costs. It spent three years in internal development of Gmail. I have no idea why you think managers weren't involved in those decisions. Meanwhile, I have no idea if battery life impact is worth measuring in your use-case. My assumption would be "no" because I would imagine the battery life impact would vary too widely to yield useful data and I don't see what I could do with that information anyway other than recommend some people not use the app. But I'm not really thinking deeply about it now, so I'd love to be enlightened. Meanwhile, trying to get more customers is a good thing, even if it fails.