I'm not sure most users would move to the new product. Most people stick to the software they use. That might be because they don't want to learn a different in

I'm not sure most users would move to the new product. Most people stick to the software they use. That might be because they don't want to learn a different interface. But I think, fundamentally, many people don't even want to deal with the existence of alternatives, they're blissfully ignorant of choice and of weighing up- and downsides[1]). I'm the same way with laundry detergent. That's a fickle kind of loyalty, though. So, if that's true and people stuck with Firefox, you'd have to maintain Firefox between the snapshot releases of Frequentfox. You'd have to push an update at least every time you fix a security issue, which can be pretty often. So you'd still need to figure out a good user experience for dealing with frequent updates. Fortunately, that's a solved problem, and the user doesn't even need to notice you've updated their software. Of course as you add features and modify/improve the user interface in Frequentfox, your Firefox snapshots will be different enough that you'd still end up alienating users, so you can't go crazy developing Frequentfox, either. I'm voting for frequent push updates, transparent if they don't change anything significant, and with a gentle introduction to the changes if they do. Big changes should be rare, maybe explain the motivation behind them to the user, and ideally make them option. Despite all the rage, I think the user interface changes from Firefox 3 to trunk weren't all that jarring; significant tweaks more than fundamental reworkings of the UI, the awesome bar is a great example. [1] Edit: I think this is what you call a "second-order decision", a term I just learned, e.g. http://thinking-marketing.blogspot.de/2009/11/second-order-decision-making.html http://thinking-marketing.blogspot.de/2009/11/second-order-d...