3 ms·

Some good points, but (there's always a "but" :-) as with most of these, let's call them modern processes (maybe not even that modern if you consider what the l

Some good points, but (there's always a "but" :-) as with most of these, let's call them modern processes (maybe not even that modern if you consider what the likes of Peter DeGrace were saying back in 1990), continuous delivery forces an engineering paradigm onto the (often unwilling) user. What does the constant barrage of (for example) iTunes or Flash updates do to the user's perception of quality? What is the impact of the Chrome release cycle on a corporate environment that needs to test each revision on a model office, in case there's an impact on one business-critical application or other?

davesims 15y ago
Yeah this is a good point, and that's a balance I'm actually in the process of determining for my current project. User expectations are different for mobile apps -- anecdotally it seems users not as annoyed by mobile app updates as they would be for Flash or even Word, because the process is a lot lighter and less painful. For web applications it's transparent to the end user. But, yes for rich client apps it's a concern. I think the trick is to deliver features rather than bug fixes and shape user expectations towards getting something new from an update rather than getting nothing but fixes that should have been in place to begin with.