Talk:List of Apple codenames

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Reorganisation by Products Category[edit]

The page had become rather unwieldy with the new onslaught of Apple codenames, diversified product line. There also is a pattern that emerges from the naming conventions, that make it more legible for readers and editors alike to notice.

There are often repeated products in the long list. This new format (by product category) allows multiple codenames to be viewed of a single product to be viewed on the same line.

I followed websites like [[1]] on how they categorised their Apple products.

Moving forward:

  1. The goal is to also re-organise all Product Categories, by product first
  2. according to the date of release

So far, the only sections that have been completed are:

  • iOS
  • macOS
  • System 7
  • tvOS
  • watchOS

For the clearest of patterns, and the easiest way to read this particular wiki page

If we can work together on this, that would be great. Knowsitallnot (talk) 21:33, 12 August 2018 (UTC)[reply]

AirPods code name?[edit]

Was there a code name for AirPods that's come out? Jimw338 (talk) 18:08, 24 June 2017 (UTC)[reply]

Added @Jimw338 Knowsitallnot (talk) 21:26, 12 August 2018 (UTC)[reply]

Presentation[edit]

We have three ways of presenting this info:

  • A sortable table (demonstrated in the first section), organized under subheadings or just a giant table
  • A bulleted list, organized under subheadings
  • The way this page was when created, with a ToC at the top and an alphabetical list of codenames (I like this one a lot, though some products have multiple codenames so that might be a bad idea)

Thoughts? DFlhb (talk) 14:37, 29 March 2023 (UTC)[reply]

Fourth idea: take the third idea (bulleted list & ToC) but sort alphabetically based on public name, rather than based on codename (one bullet point per product, followed by its codenames). Solves all issues; and a ToC is better than a long table. DFlhb (talk) 14:57, 29 March 2023 (UTC)[reply]