> There are few more things that would sell it for me as my only browser.
It is a preview, so the important question is what does Mozilla have to do to encourage people to test it? In my books, two major things need to be done:
- Give it a more meaningful name. People need to know about it and remember to follow it's development until they feel it is ready for them to test.
- Focus upon the distinguishing features that compel people to use Firefox instead of another browser.
For example: I am waiting until Firefox Preview has add-on support prior to testing it. I would much prefer to put up with an incomplete rendering engine or incomplete add-on support than live without add-ons altogether. Add-ons would allow me to use Firefox Preview normally, switch to the release version of Firefox when needed, then submit meaningful feedback. Without add-ons, I would simply reach for the release version of Firefox by default and Firefox Preview would soon be forgotten soon after installing it.
Now everyone is going to have a different must have feature. That's fine. This is a development preview, so different people are going to come on line at different times based upon what it offers. Which leads me to ...
... the name bit. I originally heard about Firefox Preview several months back, never bothered to test it for the reason stated above, then promptly forgot about it since the name did not scream, "hey, major Firefox improvements are coming down the pipe, remember me for when you're ready!" Not only is the name non-memorable, but I likely saw dozens of headlines for it in the since then and did not even realize it. Something as simple as "Firefox for Android Preview" or "Firefox for Android Technology Preview" would have alerted me that it is something that I am interested in tracking. (While I use the desktop version of Firefox, I have no interest in following articles on its updates.) Since the name didn't distinguish the product, it has been effectively out-of-sight and out-of-mind.
It is a preview, so the important question is what does Mozilla have to do to encourage people to test it? In my books, two major things need to be done:
- Give it a more meaningful name. People need to know about it and remember to follow it's development until they feel it is ready for them to test.
- Focus upon the distinguishing features that compel people to use Firefox instead of another browser.
For example: I am waiting until Firefox Preview has add-on support prior to testing it. I would much prefer to put up with an incomplete rendering engine or incomplete add-on support than live without add-ons altogether. Add-ons would allow me to use Firefox Preview normally, switch to the release version of Firefox when needed, then submit meaningful feedback. Without add-ons, I would simply reach for the release version of Firefox by default and Firefox Preview would soon be forgotten soon after installing it.
Now everyone is going to have a different must have feature. That's fine. This is a development preview, so different people are going to come on line at different times based upon what it offers. Which leads me to ...
... the name bit. I originally heard about Firefox Preview several months back, never bothered to test it for the reason stated above, then promptly forgot about it since the name did not scream, "hey, major Firefox improvements are coming down the pipe, remember me for when you're ready!" Not only is the name non-memorable, but I likely saw dozens of headlines for it in the since then and did not even realize it. Something as simple as "Firefox for Android Preview" or "Firefox for Android Technology Preview" would have alerted me that it is something that I am interested in tracking. (While I use the desktop version of Firefox, I have no interest in following articles on its updates.) Since the name didn't distinguish the product, it has been effectively out-of-sight and out-of-mind.