Further context to my question below – I’ll run you through my thought
process and you can see why I’m asking the question.
· We don’t call out which platform Firefox desktop runs on in their
table, so it’s a little counter-intuitive to call out the platform upon
which the Firefox mobile browser runs on
· It’s less ambiguous if the title is ‘Mobile Browser’, although
doesn’t 100% wipe that ambiguity since there **is** a mobile browser (of
sorts) on Fx OS, even though they’re moving towards the whole OS as a
‘browser’ (Haida)
· It would be even LESS ambiguous to have a table header for Firefox
OS alongside Firefox Desktop and Firefox Mobile Browser (if that’s how
we’re going to refer to them)
· You’ll see I designated each as ‘Firefox’ – makes the table names
longer, but maybe this helps solve the ambiguity?
I am hesitant to agree to ‘Firefox for Android’ for the following reasons:
· We will be launching Firefox for iOS in 2015, so we’d be adding
this other long title to the table
o [BUT this has the added benefit of distinguishing any differences in
the mobile browser products -> can you think of what differences there
would be? I’m not an expert in MDN by any means so seeking clarity. Firefox
for iOS will run on WebKit and not use Gecko, at least initially, so I do
expect some differences.]
· We don’t refer to Desktop as ‘Firefox for Desktop Windows’ and we
won’t ever. So in terms of naming consistency, it feels weird – but I do
also understand the rationale. We’re not really comparing apples to apples
in this scenario, and I understand that.
Since I don’t understand MDN at this point but also want to create less
ambiguity but also build in some future-proofing, what about the following
proposal given the assumptions listed here:
· Title of the table: “Firefox Browser compatibility” (vs ‘Browser
compatibility).
o [Assumes we **aren’t** including Firefox OS, but if we ARE, the title
could be ‘Firefox compatibility’ to accommodate.]
o [This therefore clearly tells us we’re talking about Firefox products
to avoid the need to re-state this in the table tab titles.]
· Table tab titles: “Desktop Browser”, “Mobile Browser”
o [This allows us to have OS if you so desire, else it just makes it
clear we’re talking about the mobile browser.]
· If there are differences in the Android browser and iOS browser
from your documentation standpoint (which, as I suspect, there are), the
options are:
o Tweak the column names within the Mobile Browser table:
§ ‘Firefox – Android’, ‘Firefox – iOS’, ‘Chrome’, ‘IE’ etc
o Create two different tables: “Mobile Browser – Android”, “Mobile
Browser – iOS”
Phew. Hopefully this lets you see inside my head a bit. We are ourselves
employing a Firefox Mobile terminology and making the Android vs iOS
distinction. I also understand the ambiguity ‘Firefox Mobile’ creates when
comparing to Firefox OS, however to be honest, I haven’t actually come
across a case where anyone **has** made an error. It becomes fairly obvious
on the context and the info provided what we’re referring to, and maybe a
line of text would help in any intro to the information you’re providing.
Happy to discuss further. I’m trying to keep consistency across the
organization with how we refer to our products, and also to not make
‘Firefox for Android’ a special case compared to how we name our Desktop
offering. We’ve become very comfortable assuming Deskop = Firefox desktop
browser (for obvious reasons) but that causes its own brand headaches at
times, so I like to try and keep things consistent as possible with how we
refer to our Firefox products.
Karen
*From:* Karen Rudnitski [mailto:
krudn...@mozilla.com]
*Sent:* 22 January 2015 10:47
*To:* 'Jean-Yves Perrier'; 'Jeremie Patonnier'
*Cc:* 'mdn-drivers'
*Subject:* RE: [Compat-data] Change "Firefox Mobile" to "Firefox For
Android"?
One more question then – will the info displayed in the tables change? Ie
any changes on the books with how the desktop columns are shown?
*From:* Jean-Yves Perrier [mailto:
jype...@gmail.com <
jype...@gmail.com>]