Show Notes
Getting an app ready for day one of an iOS/device launch is impossible to do right. As a developer you have a variety of options available for how you approach it, none of which are perfect.
Trade Offs:
App Review
Marketing (good and bad)
Bugs and Issues
Helpdesk load
New features and their worth
Wasted effort
Approaches:
As ready as you’ll ever be: Work feverishly, battling through buggy betas and API changes to be as possibly ready as possible for the estimated release date.
Measured compatibility: Just make sure it doesn’t break
Kinda ready: Keep an eye on the changes, have plans in place for basic compatibility begin in earnest once bugs are fixed
Wait and See: Wait until you have all the information before you really start
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.