3 ms·
Very nice article, and makes a lot of sense. I would be interested to see how you apply this to apps that are only used infrequently but very intensely. It woul
by phillipi 13y ago
Very nice article, and makes a lot of sense. I would be interested to see how you apply this to apps that are only used infrequently but very intensely. It would seem that the user would not see the incremental improvements but rather drastic changes on the occasion that they use the application (web or mobile), so in that case do you lose some of the benefit from this strategy? In short, if they are not regular visitors / users then does this 'breadcrumb' method of improvement have as much weight?
- dreeves 13y agoI'd say, yes, the value is almost as high, because it's not about the changes themselves (many of our "visible improvements" are bugfixes that only happen in weird cases) but about showing that you're constantly improving. It's basically a signal of the health of your company.
- bsoule 13y agoI think you can still commit to one change per day, whether or not you deploy them in batches. It'd be exciting to see the growing list of stuff to look forward to, rather than wait in a void of information. Better for the team building it too. You could note in your changelog which ones are live and which are being alpha tested.