6 ms·
The problem with that approach (the immediate update) is that you're chasing a moving target. Fixing an app for a beta OS is actually kind of dumb from a cost-b
by briandear 13y ago
The problem with that approach (the immediate update) is that you're chasing a moving target. Fixing an app for a beta OS is actually kind of dumb from a cost-benefit analysis. Because what might be "fixed" in beta 1 might be broken again in beta 5 as the OS itself is necessarily changing. My strategy is to fix obvious issues early (for example UI components) and then revisit in later betas and making final fixes at gold master. I don't care if some beta users have issues because everyone has issues on a beta. Even some of Apple's own apps are still having issues (for example, the iBooks dictionary,) so it's pointless to chase bugs in a beta until the OS itself is closer to final stability.
- deong 13y agoI have no problem with that approach, but the cost-benefit analysis needs to take into account the likelihood that some huge percentage of your user-base can't run the app. If 50% of my users get a crash at start-up, I'm going to try to make that go away. If no one is really having the problem, then it's silly to ask for Apple to block potentially legitimate feedback. If loads of people are having the problem, then the cost-benefit analysis ought to look very different.