Reporting and Nominating Bugs for Mozilla Firefox 1.0
Thursday April 29th, 2004
Ben Goodger writes: "We're beginning the drive to Firefox 1.0 and we need to make sure that every bug people think is important is filed in Bugzilla and has a blocking0.9? or blocking1.0? request flag set. This will allow the FDT (heh) to develop an action plan for the milestones between now and 1.0, prioritize bugs and so on. It's essential that people start doing this now, rather than later, otherwise bugs might slip through the cracks!" Further details are available in Ben's posting to the Firefox forums.
#51 Re: Target market ...
Friday April 30th, 2004 12:21 PM
You are replying to this message
>Yes, but what benefit does the average home desktop user, especially >the average Windows home desktop user really gain from switching >from IE - maybe IE with one of the tabbing / popup-blocking extensions >from downloading and using FF?
I can answer this.
First, these users are just as likely to see a new browser as they are to see the IE skin - I'd say more so because there exist no MyIE2 or AvantBrowser buttons for websites. Firefox has that covered, and thus it's out and more visible than MyIE2/friends are.
As for the answer, I just demoed Firefox for a friend today (not particularly intentionally - I was using it, and he asked about it). I only mentioned two features to him initially (with a third when he mentioned an IE shortcoming): popup blocking and image blocking. He's got the Google Toolbar, but image blocking was completely new to him. Imagine it - block out banner ads and simply see the page! He also mentioned some adware he somehow got installed, so I pointed out that Firefox is less used and therefore that much smaller a target. I don't know if he'll carry the interest far enough to download it, but the seeds are sown.
>Therefore I argued that instead targeting a niche where innovative >features would be a big motivation to switch could establish a bigger >and more commited market segment.
For this target market, customizability from the FE is actually bad - IT would rather support one configuration than many. Furthermore, the same functionality exists in the backend for one willing to develop an extension, and about:config is nearly as customizable in Firefox as in Seamonkey. Firefox also runs XUL apps like Seamonkey, and the backend is mostly the same between the two.