How about no? If it's my app, I'll use my logo. I consider the logo an integral part of the application's identity and I should control its identity. I promise I'll do my best to make it easily and readily recognizable, regardless of it using national colors, a rainbow or shades of white, pink and blue. If you don't like it, it's your problem, not mine.
> If it's my app Not picking on you specifically, because this attitude is extremely common among software developers these days, but I think this mentality of treating software running on users' machines as "yours" rather than "theirs" is at the core of a lot of problems with the modern software industry. Software should serve the interests of its users, not its developers. The advent of ubiquitous internet connecti…
This is one of the most important points of the conversation. The other most important point would be the difficulty / impossibility of reverting to an older version of the application on mobile systems. When you put them together you get users powerless on their own devices, stuck in a needless dilemma between keeping the application in its new, worsened state, or throwing away the whole thing.
On my PC I download "portable" / .zip releases of software whenever possible, and I keep every single package. If a program has an update with a regression, I can just choose to not use it, or run it side-by-side with the older version.
On Android, F-Droid serves the last couple APKs for each app, and I download these to my PC also. However, Android makes side-by-side installation difficult unless you recompile the app with a different package ID. If it's a closed-source app from the Play Store, you're screwed. I would not be surprised if it's impossible on iphone.
So, I disable auto updates, and I ignore the boy who cries "important security fixes". Better luck next time.