Show Notes
Today I’m going to dive into the world of app updates. Why we do them, how often we do them and whether they are important.
Context
I did a long analysis of the update trends in the App Store. I recommend you visit that yourself but the short version is:
50% of Top Apps are have been updated in the last 3 months (26% overall)
86% of Top Apps in the last year (60% overall)
300,000 apps were updated in the last 3 months.
480,000 apps are effectively abandoned (no updates in last year)
Types of Updates
An actual shipped update might include more than one of the following categories but it is likely constructive to think about why you are making a change before you make it.
Compatibility: An update that exists to allow the existing feature set to work on new hardware, operating system, API, etc.
Remedial: An update that exists to correct a flaw or deficiency in existing functionality.
Defensive: An update that exists to keep up with the competition.
Enhancement: An update that adds functionality or capability to the app.
Marketing: An update with purpose of drawing attention to the app or garnering revenue.
Refactor: An update that does not change the user facing portions of the app but improves it internally.
Things to consider
Is this update necessary? Why, concretely, am I doing it?
Does adding this functionality improve the app for most users?
Would adding the functionality hurt the experience of any of my users?
How do I expect to be compensated for the time I put into this update?
More from Developing Perspective
Gone are the days of map-and-compass development, now if we can imagine it and see a line of sight to it we can build things nearly instantly. Which totally changes the cognitive and structural tradeoffs we need to make in our development process…and how we take care of ourselves in that.
I walk through the history of Apple developer platforms over my history as an app developer and grade them, then think a bit about what has made them worthwhile.
I’m bringing Developing Perspective back. This first episode wrestles through why being an indie app developer right now feels so “pivotal”, in both senses of the word. There’s the constant, week-by-week change in our tools and workflows, and there’s the bigger structural shift in what it even means to “make” apps.
I tend to think of my app business in terms of revenue per day. Breaking it down to that level helps me keep a close eye on it and know how well or poorly I’m doing. Today I walk through the reasoning for this as well as do a thought experiment of what the numbers might look like for a new business.