Template talk:Mobile operating systems

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
WikiProject Telecommunications (Rated Template-class, Mid-importance)
WikiProject iconThis template is within the scope of WikiProject Telecommunications, a collaborative effort to improve the coverage of Telecommunications on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 Template  This template does not require a rating on the project's quality scale.
 Mid  This template has been rated as Mid-importance on the project's importance scale.
WikiProject Software / Computing  (Rated Template-class, Mid-importance)
WikiProject iconThis template is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 Template  This template does not require a rating on the project's quality scale.
 Mid  This template has been rated as Mid-importance on the project's importance scale.
Taskforce icon
This template is supported by WikiProject Computing (marked as Low-importance).

Notes about this article[edit]

Over the past decade, mobile operating systems have developed from simple notetaking and scheduling systems into powerful operating systems with features comparable to typical desktop operating systems.

This article provides a list of the popular mobile operating systems, and footnotes indicating the provision of certain features that enable powerful functionality similar to that of desktop operating systems. Given that around half of the current mobile operating systems are based on Linux, the list also indicates whether or not the mobile operating systems are Linux-based. --InternetMeme (talk) 12:24, 20 April 2008 (UTC)[]

Bullet points[edit]

Hey, by your edit summary, do you mean that the order you put them in is in accordance with their market share?

Also, I read somewhere on Wikipedia that bullets are somewhat discouraged, and since there is only one list with all the OSes now without the two sub-lists, I thought the bullets didn't really add any clarity like they did before. And they also take up precious horizontal space, and squash all the items together vertically. I'd far prefer to do away with them now. What do you think? InternetMeme (talk) 11:28, 17 April 2008 (UTC)[]

I've removed the bullet points for the following reasons:

  • Given that there are no sub-lists, the bullet points don't aid clarity.
  • There really isn't enough horizontal room for them.
  • They make all the OS-list items squash together vertically.
  • They visually demote the OS-list items to the same level as the footnotes.

Thanks for your understanding : )

I've also spaced out the footnote indicators, as it can be very hard to distinguish the letters on a high-res CRT : ) --InternetMeme (talk) 12:22, 20 April 2008 (UTC)[]

Native code[edit]

I understand the concept of machine/native code. The information I'm providing with the "native code" tag is to help people who are interested in running custom native applications on their devices. Currently, Blackberry OS, Android, and LiMo Platform don't allow this. InternetMeme (talk) 15:44, 17 April 2008 (UTC)[]

1. I am glad you understand the concept of native code; but that doesn't make writing the wrong thing correct. All the platforms run native code; it's just that some restrict who can run it.

2. Yes, some people are interested in running native code without getting certification - basically a few hobbyists who want to run C code on a mobile. Some people are interested in running, say Java. That's a tie, and anyway, ***anyone capable of writing native code is more than capable of finding out whether a platform can run it in a few second of googling***. But even without the last, the security trumps every other issue, especially given the growing opportunities for denial of service attacks on telecoms infrastructure. Its security more than anything else that categorizes platforms; showing the absence of security as if it is a positive feature is very, very silly.

3. It's misleading and incoherent to have the categories "native code" and "certified" - certified is a form of native code.

4. If you want to make information on which platforms can run uncertified native code available to hobbyists, then put it on a webpage. Wikipedia's intent is provide info to a general audience, not act as a repository for hobbyists, whether they program in C or Java, so a large general factor - which security is - necessarily trumps a hobbyist motivation in editing and structuring information.

5. If the chart shows managed code and certified code capabilities, then it's a chart to provides security info - a symbol equates to a security method, and the absence of a symbol to having no security. If it shows native code and certified instead as symbols, with no symbol for managed, then beside being misleading re 1. and 3., it's not structured to show any particular category of information at all - it's a hodge podge. In fact, non-technical users will probably come away thinking that "native code" is a form of security. This is very, very bad design. Read Edward Tufte.

6. Again, to show how poorly "native vs certfied" works, iPhone will be switching to a certfied model in the production release of the SDK. (Probably; some form of security is promised, and that's the easiest to add.) Obviously the code won't have changed from ObjC to Java or Lua, so it will still be native, although it will be certified!

Umptious (talk) 20:14, 17 April 2008 (UTC)[]

I think your view of the average user's priorites are incorrect: People are generally interested in whether they can get third-party applications with unrestricted access to hardware. On what basis do you think that the average user is curious to know whether or not the Final security model is known?

-- End users don't even know what "third-party applications with unrestricted access to hardware" means. So they are not interested in knowing whether a platform has this by definition. Otoh they are interested in "Can my phone be used to steal my PayPal password?" "Can Fred's phone be used to create a cyberterrorist attack"? More: running in native code does NOT necessarly provide the unrestricted access to hw you imagine. For instance, if you check the spec of the Nokia N800 you'll find it has abuilt-in PowerVR chip. This can't be reached, even though the platform allows unrestricted native code. Otoh, a manufacturer using the same chip and permitting only Java to be run could provide access if he chose. The issue that you imagine is important to you is one that is much more complex than you think. Umptious (talk) 14:53, 18 April 2008 (UTC)[]

Please leave in the native code specification. InternetMeme (talk) 04:23, 18 April 2008 (UTC)[]

On the other hand, your addition of the "capability-based security" specification is very good ; ) So thanks for adding that! InternetMeme (talk) 04:28, 18 April 2008 (UTC)[]

I've re-read the information you provided, and realized that we've probably got two different equally valid perspectives on operating systems:

  • You're thinking along the lines of "How secure is this platform? What security policies does it enforce? Does it restrict access to the hardware? Or will it allow native code to run uninhibited?"
  • I'm thinking "How similar to a regular desktop operating system is this? Can I get full access to the hardware? Can developers write procedures in assembler to enhance performance? Will it perform?"

- Your POV only to a hobbyist whose aim is to use the platform to write C code - because that *is* his hobby. A consumer, analyst, manager, political decision maker, or citizen concerned at data theft or cyberterrorism will want to know about security. The first is, I've said, a specialist interest for a hobby web site, the second is appropriate for a general encyclopedia. (A *professional* programmer's interests will be different again - but security will probably be the most important: switching being native and managed code comes easily to a pro, but if a platform is fundamentally insecure he may have to abandon it.) Btw, if you think writing assembly automatically corresponds to increased performance today then you should read a good book on modern processor architecture and optimization. (Try Dowd's book, or Randall Hyde's, especially if you still think that the cpu cycle per instruction time in the handbook really determines performance...) And I say this as probably the only person who managed to get 16bit realtime gouraud shading running on a non-mmx Pentium in a real game - which let me double my salary and got me invited to Intel game dev conferences and one of the first half dozen MMX PCs in Europe, back in the day). Umptious (talk) 14:53, 18 April 2008 (UTC)[]

Basically, the "native code" tag is completely unrelated to security. It's just there to let people know which operating systems allow more unfettered access to hardware. --InternetMeme (talk) 13:31, 18 April 2008 (UTC)[]

- Having "native" as am extra category may not be harmful, as long as it used correctly. I'll think about it. But you've marked several platforms incorrectly. Mobile does have a cert system - although I think it can probably be ignored; iPhone won't be allowing open native code access in the final developer SDK (see the article I linked from the Maemo page); Qtopia only allows approved middleware in run in native - general third party apps are managed, so it's only native in the minimal sense that *any* os has to be: check the platform docs linked from the wiki article. I'll come back and correct these when I have time. Oh, and leave a message on my wiki page if you want more concrete book suggestions. Umptious (talk) 14:53, 18 April 2008 (UTC)[]

Just added native code indicator for LiMo; I'm also editing the LiMo Platform article, with a reference there. (talk) 00:18, 25 April 2008 (UTC)[]

navbox vs infobox[edit]

Would this template fit better as a {{navbox}} instead of an infobox? Here is a quick mockup:

Many of the linked articles already have an infobox and this gets pushed below it, which messes up some of the section [edit] links directly below the table of contents. See iPhone OS to see what I mean. ~ PaulT+/C 23:51, 20 April 2008 (UTC)[]

Hmmm. Well, I think it's easier to read with all the items in a vertical list. Articles such as DVB and GSM have a list of standards in a similar format, at the vertical layout is very easy to read. navboxes are nice, but I think it's easier to read in its current format.
Nice job of the navbox, though : )
InternetMeme (talk) 16:11, 21 April 2008 (UTC)[]
I strongly agree with this change. Navboxen should look consistent. We should convert this one before it's transcluded too widely to make it easy to do in future. Chris Cunningham (not at work) - talk 16:28, 26 April 2008 (UTC)[]
I've seen another list like this called Template: Table Mobile phone standards that works rather well. It's easy to access and browse through a few items on the list without scrolling down to the bottom of the page each time; it's easier to read, as a vertical layout works well with lists. Also, in the vertical format, it can easily be transcluded in context within sub-sections of other articles pertaining to operating sytems. We could always have a navbox at the bottom as well : ) InternetMeme (talk) 17:04, 26 April 2008 (UTC)[]
The Mobile Standards box works because unlike operating systems, networking standards typically don't have navboxes at the top of their articles, nor particularly many screenshots. In this case the template clashes with other templates on its transclusions; it doesn't play well with {{ambox}}es on at least Firefox 3, and stacks poorly with infoboxes. As for having both, that'd just lead to even more link-spamming. Chris Cunningham (not at work) - talk 17:13, 26 April 2008 (UTC)[]
Hey, I'd better sleep on it (It's very late here). I'll write the reasons I think the Table is better when I get up : ) I'll be back soon. —Preceding unsigned comment added by InternetMeme (talkcontribs) 17:20, 26 April 2008 (UTC)[]
Hey, well, Independently of what's a better idea out of the infobox vs. the navbox, it's definitely a good idea to keep them separate, as they have different names (Template:Mobile operating systems vs Template:Table mobile operating systems).
Both formats have pros and cons. For instance, the current format is suitable for transcluding inline in certain types of articles. I agree that navboxes are also goo though, so why not make one of them as well? If the people that are involved in the respective articles prefer one over the other, then they can take their pick : ) Or use both, if it's a large article : ) InternetMeme (talk) 12:46, 3 May 2008 (UTC)[]
Because that's a poor compromise. I don't feel that there's any reason to not use a navbox in all cases, so the end result would be the same (replacing all the templates). You haven't shown which "certain types of articles" the floated template is more suitable for. Chris Cunningham (not at work) - talk 13:03, 3 May 2008 (UTC)[]
Well, from my point of view, I don't see why we shouldn't just leave it the way it is in all cases, so the compromise seems sensible to me. It seems as though the only advantage to changing it is that it will match a system that may not feature the best layout. Wikipedia is constantly evolving in all respects—layout included—and trying new ways of presenting information can be a good thing. Also, Template:Infobox_OS doesn't play well with {{ambox}} either, but it would be a bad move to delete that.—Preceding unsigned comment added by InternetMeme (talkcontribs)

This doesn't work well as an infobox because most of the pages it links to and is transcluded on already have infoboxes themselves. This results in a messy situation with two infoboxes one right after the other. As I mentioned in the first post of this section, this can cause formatting problems with section [edit] links. Also, many of these pages are also very short and having a long infobox like this looks out of place.

Converting this list to a navbox would mitigate many of these problems. I haven't seen any concrete arguments for why it should be kept as a list other than "it looks better to me that way" and "there are other infobox templates similar to this one". Neither argument addresses the issues that have been pointed out in this discussion. ~ PaulT+/C 19:17, 14 May 2008 (UTC)[]

Do navbox. Infobox is meant for other uses and looks like crap in this case.--Kozuch (talk) 23:19, 23 July 2008 (UTC)[]

I've gone back to using a navbox. Chris Cunningham (not at work) - talk 08:33, 25 July 2008 (UTC)[]

Inclusion of maemo[edit]

Should maemo be included in this list? It seems to me it should be, as the term "mobile" doesn't seem to be used as shorthand for "mobile phone" here, but there's nothing clearly stating that non-telephone devices are included, and all other OSes listed are (or are planned to be) used in phones. —Preceding unsigned comment added by (talk) 00:36, 25 April 2008 (UTC)[]

I agree : ) Check the "Internet Tablet OS" link. InternetMeme (talk) 03:28, 25 April 2008 (UTC)[]

I disagree in part, if we are going to include ITOS, why not eeePC, Windows XP, and Windows Vista as they are used on other physically "mobile" devices. Unfortunately there doesn't appear to be a clear naming consistency in the industry to rely on in this case. Brontide (talk) 13:17, 25 April 2008 (UTC)[]

Yeah, Brontide, I think you're on to something. And as time goes on, desktop operating will be used on more mobile devices, and conversely, an increasing number of mobile operating systems will rival desktop operating systems in functionality; and the line will blur still further. Probably this issue will have to be addressed in future, but for now, my general definition of a mobile operating system is something like "Any commonly used or well-known operating system designed to work on a device that fits in an average sized pocket". Not a great definition, but its a start : ). --InternetMeme (talk) 13:29, 25 April 2008 (UTC)[]

Various OS[edit]

current discussion

LiMo Platform[edit]

Is the LiMo Platform itself an OS? I see someone added MotoMagx below it. I assume that is an OS based on the LiMo Platform? Why have both listed? Shouldn't just the OSes be listed with a note saying which ones are based on the LiMo Platform if that is relevant? ~ PaulT+/C 19:04, 14 May 2008 (UTC)[]

If I am not wrong, I think most mobile devices, uses Runtime and Bytecode complier (a type of low level virtualization), so it can be easily cross-platform and they don't have an OS. I think usually they will only use OS if they want support various programming languages and the programming language that have a foundation (with projects) or frameworks e.g. Ruby (Rails, rhtml). Well theoretically they could include rhtml, but I somewhat doubt they would, at least I don't think any developer would bother with using complex languages, since ARM capabilites are not for intense output. Well for some companies they have their plans such as MokaFive Virtualization (on iPhone) that is why iPhone is probably a kernel. Also I think PSP or was it one of the console OS are even updateable through Firmware PSP (Hardware). Probably not encouraged on mobile devices, since it would cause a havoc on service provider servers with the compatibility problem and most service providers are already unhappy about people unlocking the features even though it is not illegal at all.

By the way you should get involved with the Mobile Internet Devices if interested. --Ramu50 (talk) 04:35, 3 November 2008 (UTC)[]

Mac OS X[edit]

In my opinion Mac OS X may well be called a mobile operating system by now as it is widely spread through iPod Touch and iPhone by now. The App Store and other features are special features related to the mobile version of this OS. Since Ubuntu Mobile is on that list I guess Mac OS X may also go there. What do you think? Till (talk) 20:19, 16 September 2008 (UTC)[]

Hmmm...the article seems very confusing, I thought Apple is just an Object-Orientated Nextstep Operating System, because the article doesn't seem to show it is a version of Mac OS X like Window Mobile nor is it lightweight versions. But if you at the article it says it uses Darwin OS (POSIX), so since there is no indication of framework of any sort and it consists of 4 abstraction layer, I guess it is a OS Kernel?@@?

Any clue, should we add it or no? --Ramu50 (talk) 04:02, 3 November 2008 (UTC)[]

Openomoko and Moblin[edit]

Changed, because Openmoko is also a project, and so is Moblin, easier to recognize than connotating advertising of the companies. --Ramu50 (talk) 03:55, 3 November 2008 (UTC)[]

Categorization method[edit]

I strongly disagree we should use random Alphabetical order, it does nothing. But if categorie using types (or what is support, thus sub-sort them by alphabetical group) will make it a lot quicker to find, since it connotate implementations like Ajile, RIA, RAD, CRUD, ACID...etc.), instead of trying to remember everything. --Ramu50 (talk) 00:40, 13 November 2008 (UTC)[]

And as you've been told over and over again on various template talk pages, navbox templates are not directories. They are quick grab-bags of links to related articles. They do not need to be extensively categorised because that is not what they are for. Excessive sub-division and sorting actually reduces the utility of navbox templates by forcing users to consider many details of the subject they are looking for instead of just its name (which is what sorting into a basic set of groups and then going alphabetically allows). Chris Cunningham (not at work) - talk 09:19, 13 November 2008 (UTC)[]


Does anyone know which of these OS support Multitouch? --Ramu50 (talk) 23:46, 28 November 2008 (UTC)[]

Palm Web OS[edit]

Can someone add Palm WebOS to the template? --Cameron Scott (talk) 01:06, 9 January 2009 (UTC)[]

Added this. dissolvetalk 01:16, 18 January 2009 (UTC)[]

current vs. discontinued[edit]

Maybe we should divide each of the template lines in two parts:

Yes, but rather:
bender235 (talk) 11:37, 4 September 2010 (UTC)[]
This is also possible, but aren't the (brackets) too much? Alinor (talk) 16:59, 12 February 2011 (UTC)[]

Yes, please. If someone wants to do the work to designate active and discontinued, that would be good. Otherwise, myself and others (User:Comp.arch) might uselessly continue to add and then remove the same entries. Also note related Talk section Discontinued OS.
JamesThomasMoon1979 08:25, 10 December 2018 (UTC)[]

ubuntu ARM version[edit]

Although ubuntu for mobile is discontinued, but ubuntu itself have an ARM version which people are keep porting them to phones like for HTC HD2 and various of phone....where should it be included in the template? How about the linux that had been officially ported to Archos' Internet Tablets? C933103 (talk) 17:06, 22 September 2011 (UTC)[]

It turns out that Tizen is not a continuation of MeeGo[edit]

Hello. It turns out that Tizen is not a continuation of MeeGo. It borrows its components but accorduing to developers on the mailing list and the released Alpha version, Tizen is a distinct OS rather based on SLP. I propose to add Tizen separately on the list instead and leaving MeeGo as it was before adding the Tizen article. Mer OS (MeeGo-reloaded) would be added as successor of MeeGo here once we know more about new releases. So far we have no Mer article though. — Preceding unsigned comment added by Malagajoe (talkcontribs) 22:17, 21 January 2012 (UTC)[]

Discontinued OS[edit]

In the template, following mobile OS are removed from the template due to discontinued.

| group2 = Discontinued | list2 =

| group2 = Discontinued | list2 =

IMHO they should be added back to the template for references purpose. C933103 (talk) 12:45, 23 March 2012 (UTC)[]

I agree. These should be restored. This is navigation template for Wikipedia articles, this is not a "list of current mobile OS". Ianteraf (talk) 12:53, 1 April 2012 (UTC)[]
Agreed C933103. See my comment in section current vs. discontinued.
JamesThomasMoon1979 08:28, 10 December 2018 (UTC)[]

What is and isn't an Operating System[edit]

Several of these "Operating Systems" were removed from the Microsoft template because they aren't truly operating systems but modified versions of other operating systems, so this template also needs a MAJOR cleanup, but as I don't want to cause an edit war I'll let someone with more insight on what constitute an operating system and what constitute a platform (a modified version of an operating system), as for example with the Microsoft case Zune (modified CE) was left while S30, and S40 were removed because they were modified Java. -- (talk) 17:19, 1 January 2015 (UTC)[]

If you are referring to Template talk:Microsoft operating systems § Why the "Nokia" Operating systems should be here, it was not a matter of being or not being an operating system; it was a matter of being owned by Microsoft. Symbian, for example seems to be owned by Accenture, not Microsoft. Best regards, Codename Lisa (talk) 01:55, 2 January 2015 (UTC)[]

Windows 8 a mobile OS?[edit]

Hi. So, I've seen lots of people assuming that Windows 8 is a mobile OS just because they have no trouble imagining a Start screen-like thing on an iPhone-like thing. But is it really?

Let me ask one vital question: Can Windows 8 dial a phone number? (Of course, it entails native support for dial pads, phone hardware, SIM card, etc.)

Also, two-three years ago, when we were writing Windows 8 and Windows 8.1, I distinctly remember their betas weren't compatible with all hypervisors; i.e. they didn't run on just any virtual machine. The problem was some fine way of operation in their x86 virtualization. Steven Sinfosky said that's because they were operating very close to the metal! Now, phones don't have the run-of-the-mill stuff that everyone on a PC takes from granted; e.g. BIOS, UEFI, PCI, SATA, SCSI and DRAM. They don't use such complex file systems as NTFS either. All of these impose a tons of features that phones never ever use. Can Windows 8 really work without these and be a phone OS? e.g. Can it be installed on a SSD formatted with ExFAT and boot with coreboot?

I'm just saying: I agree that Windows 8 is closed to a mobile OS but is it there yet?

Best regards, --Codename Lisa (talk) 01:37, 31 January 2015 (UTC)[]

Neither can the 3DS or PlayStation Vita, and yet they're still listed. Microsoft's strategy is unification and repurposement. ViperSnake151  Talk  01:56, 31 January 2015 (UTC)[]
@ViperSnake151: Yes. All the more reason to ask "what is the criteria?" What is the criteria from your view?
As for Microsoft strategy, I'd rather no jump to conclusion from a couple of project names and ambiguous words. I've seen how they turn out before.
Best regards,
Codename Lisa (talk) 08:43, 1 February 2015 (UTC)[]
Pardon, but I've been dialing phone numbers on Windows for many, many versions (an attached dial-up modem and Outlook's help). I don't think that's a criterion. It's just a question of app software + the appropriate hardware. There is no support required at the operating system level (unless you count the serial port driver, which has a thousand other uses, i.e. is not specific to this job).
Windows RT is built from the same source code base as Windows 8/8.1. Windows RT is for mobile devices like the Surface. So how is Windows 8 a mobile OS"? How is it not? And Windows 10 will be specifically labeled "for phones" as well.
Approximately 99.99984% of Windows does not care how the underlying hardware works or how it's interfaced, only about functionality. BIOS or UEFI are only important for booting and for their influence on disk partition tables. Device drivers don't care if PCI(-E) is there or not; they are written to the HCIs of their respective devices. If you "ported" a device to another sort of interconnect but preserved the HCI, the drivers wouldn't have to change as long as the new interconnect provided similar functionality (I/O ports, if your device still uses them, and "registers", interrupts, etc.). Same for SATA or SCSI: As long as you have a way to read and write blocks from your random-access block storage device, nobody outside of a very small set of drivers cares how the commands and responses get to and from the device. And functional equivalents for all that stuff already exist on smartphones. DRAM? My S4 has 2 GB of DDR3 RAM. What's the issue?
There are also significant enhancements to power management and memory management in Windows 8 that were put there specifically to support mobile platforms, with requirements for low power drain and limited RAM.
Of course, since there are still clear design points in Windows 10 that trace all the way back to NT 3.1 (and to VMS before that), these OSs were not designed from the ground up to be mobile OSs. If that's a criterion, then, no, they're not. Too, what some see as "the OS" is not what others see. Jeh (talk) 09:07, 31 January 2015 (UTC)[]
@Jeh: Alright, Jeh. Before I go into details, let's discuss your overall reply. If all that you say is true, what makes OS X, Kubuntu, Linux Mint and many other not a mobile OS? Why don't we just have an OS infobox? What makes Android a mobile OS? I've certainly run in inside an x86 virtual machine.
Best regards,
Codename Lisa (talk) 08:48, 1 February 2015 (UTC)[]
@Codename Lisa: I don't know enough about most of the other OSs you mentioned to state with any certainty that we should call them "mobile OSs" or not. (I have all I can do to keep up with what Microsoft is doing with Windows!) The most I can say about any of them is this: a) Since Android uses a Linux kernel, but the rest of it was designed from the ground up to work well on mobiles, it's pretty clear that it should be called a "mobile OS". And b): My hunch is "almost certainly not" for OS X, simply because Apple wrote a different OS for their mobile devices. Of course, their first target for IOS was the original iPhone, which was far less powerful than the mobiles of today.
Speculation: This is maybe confirmed by the fact that Microsoft wasn't putting Windows-from-the-desktop-OS-source-code on tablets until Windows 8 - not because Windows 7 could not have been adapted to the purpose, but because the hardware wasn't powerful enough until the Windows 8 period. Repeat for Windows 10, only now it's the hardware in phones that had to catch up - until then, MS needed a separate OS (originally CE) for phones. Jeh (talk) 09:37, 1 February 2015 (UTC)[]
@Jeh: Wow! That leaves us with literally nothing but WP:SYNTH, which is not good. Alright, I have proposal in mind, but I think because I am the reverter, it is fair to hear yours and ViperSnake151's first: What criteria do you suggest for having operating systems put in this template?
Best regards,
Codename Lisa (talk) 09:52, 1 February 2015 (UTC)[]
@Codename Lisa: I'm not sure why "has been supplied pre-installed on mobile devices" isn't sufficient for admission. What's the underlying problem that you're trying to solve here? Personally I would rather see a way to show OSs' characteristics than try to put them into cubbyholes. Jeh (talk) 10:11, 1 February 2015 (UTC)[]
@Jeh: Oh, I think that's a flawless criteria. Do you know any mobile phone with Windows 8 on it? Best regards, Codename Lisa (talk) 10:22, 1 February 2015 (UTC)[]
No, but I didn't think we were talking just about mobile phones. What about tablets? Don't they count as "mobile devices"? If the template is only for mobile phone OSs than its title should say so. Jeh (talk) 11:10, 1 February 2015 (UTC)[]
@Jeh: We aren't? Your comment about iOS made me think we are talking about phones alone. I propose we are talking about: Phones, handheld consoles, PDAs, GPS systems, eBook readers, cameras and handheld media players. What else I am missing? (ViperSnake151, please chip in, will you?)
Tablet PCs? Well, any desktop OS runs on Intel ones and some of them are as immobile as a coffee table or whiteboards. But honestly, some of them are very mobile like Microsoft Tablet PC and iPad. (They run Windows XP Tablet PC Edition and iOS.) We need a restricting factor here. Do you know of any licensing or pricing terms that takes size into account?
Best regards --Codename Lisa (talk) 18:09, 1 February 2015 (UTC)[]
I don't know why you thought I thought this was only about phones. I agree with your list. You could use "intended to be portable and to be used while handheld" as a criterion for mobile platforms, I guess.
I'm getting the feeling that just about any set of "passgauge" criteria will lead to either things that are left out that should be included, or things included that should be left out. Or possibly some of each. So I'm not really motivated by this issue. Sorry. Jeh (talk) 18:35, 1 February 2015 (UTC)[]
I just saw this discussion now, while dialing numbers has for the longest time not been a mobile thing (usually done from a desktop, not a desktop OS..) one other thing is meaningless in a non-mobile OS, GPS capability, and the apps (Google Maps) that follow from that. Another thing is touchscreens as primary user interface, not the keyboard (and shell..) I do not recommend reading the big argument I started and gave up on eventually.. (hybrid OSes will be more common and eventually the norm, so you can't really say that OSes are either (except in the "clear-cut" early OSes)): https://en.wikipedia.org/w/index.php?title=Template_talk:Unix&oldid=618572551 comp.arch (talk) 09:59, 23 November 2015 (UTC)[]

Why not have template alphabetical?[edit]

What order is the template using now? "L" comes before "X", which comes before "W", which comes before "Q"? and List item #6 is broken again. --CaribDigita (talk) 23:34, 13 March 2015 (UTC)[]

Hello, CaribDigita. Wikipedia laws do not have a mandate for alphabetical orders, neither ascending nor descending. But they do emphasize on due weight and not giving equal or arbitrary validity. (Indeed, alphabetical sorting has become worthless in the Internet era, because there is the search function.) Naturally, Linux kernels, which comprise the majority of mobile devices worldwide come first, thanks to Android. XNU makes the second position thanks to iOS. Windows kernel currently make news titles a lot but are the least successful of all.
Of course, I can see a lot of rooms for improvement but the whole issue does not have much priority in comparison to what I have on hand.
Best regards --Codename Lisa (talk) 05:38, 17 March 2015 (UTC)[]
Alphabetical isn't POV though. Since as you say, all articles should be undue-weight not necc. listing them based on a popularity contest. CaribDigita (talk) 13:04, 18 March 2015 (UTC)[]
Perhaps not. Alphabetical sorting isn't ipso facto evil. But it is often an evil excuse in evildoings. For example, when someone changes the OS order in an infobox from "Windows, OS X, Linux" to "Linux, OS X, Windows" because of loving Linux or hating Windows/Microsoft, that someone is using alphabetical order as an excuse. And an invalid excuse too. The former is alphabetical too, albeit descending, not ascending.
Best regards --Codename Lisa (talk) 23:59, 18 March 2015 (UTC)[]

Windows CE[edit]

Windows CE should probably be added as a predecessor to Windows Mobile. It ran on mobile device classes including Handheld PC and Palm-size PC.

Also, there are specific article about PocketPC 2000, Pocket PC 2002, Windows Mobile 2003, Windows Mobile 5.0, Windows Mobile 6.0, Windows Mobile 6.1 and Windows Mobile 6.5. Would it make sense to list these as separare entries or is it preferable to keep a single entry under Windows Mobile? The Seventh Taylor (talk) 18:51, 11 October 2015 (UTC)[]

Shouldn't we include an explanation for why some items are italicized?[edit]

I personally don't know why some entries in the template are italicized, I'm just guessing it's for discontinued operating systems as Firefox OS was one such entry. So shouldn't we explain this in the template? Like at its end? Fuse809 (contribs · email · talk · uploads) 17:18, 6 December 2017 (UTC)[]

I removed all italicizations as it is removed in here by another user, but then added back again without discussion and concensus. Also per MOS:COMPUTING. –Wefk423 (talk) 11:13, 28 April 2018 (UTC)[]